![]() 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. the result of a response message previously received by the sending lifeline.But not here, since the only message was votePost(vote) a parameter of a message previously received by the sending lifeline.an object visible by the sending lifeline, such as property of the enclosing context or a globally known object.But not here, since your lifelines are anonymous (no symbol before the :) an object corresponding to another lifeline.The parameter symbols such as user in the message arguments can for example be: ![]() If deemed useful, this is a portion of a class diagram showing the relevant entities : Is it a correct approach, or should a third control object (called AuthenticationControl) be involved in order to get the current user? Where does the user argument come from?Ĭurrently I did it so that the boundary object PostPage calls votePost(user,post,vote), assuming that it has knowledge of the user entity associated to the actor participating in the use case. In the sequence diagram with the analysis objects for this use cases, there is a message votePost(user, post, vote).
0 Comments
Leave a Reply. |