![]() SDs support modularity mechanisms and combination operators, such as parallel, alternative, optional, or repeated action or event occurrences (par, alt, opt, loop) in the definition of the interactions. Moreover, the succession of control creation (which represents in principle a use case according to the EBC model) looks more like a detailed description of the system's internals rather than a high level overview of the requirements (that could be discussed with a user) or the more detailed analysis of requirements.In UML, sequence diagrams (SD) describe a type of interaction that focuses on the partial order of message interchanges between objects. I'm asking because this diagram seems very detailed for a use-case scenario. Unrelated remarksĪre you sure that you are still modeling the requirements and that you did not accidentelly start to model the detailed design? This gives you full freedom, including starting to gather requirements, and complete teh diagram afterwards to be sure that the needed paramters are known where they are needed. UML 2.5.1, section 8.3.3.1 page 71: (.) However, the actual interpretation of the symbol depends on the context of use of the Expression and this specification does not provide any standard symbol definitions. What does the UML specs say?īeyond these natural and straightforward possibiliies, there are many more possible origins, because the UML specifications leave the semantics unspecified: But you could also think of some property that the enclosing context keeps once the user logs in. You could imagine that :PostPage knows it since it was specially created for the user interaction. ![]() But not here, since no such message is received.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |