In that case, the actor exchanges messages with the user interface life line and the user interface exchanges messages with entities like Storage or DeliveredProduct.ĭisclaimer: Because it is homework, I expect you have some text book recommending some particular way of modeling. Often, sequence diagrams have life lines that represent the user interface, or particular parts of the user interface (often called boundary classes). In your example, I would expect the actor to send a message containing the shipping code to Storage, then Storage requests delivery information from DeliveredProduct and then Storage returns that information to the actor. If you use UML 1 however, you should use objects and underline them. I say 'parts' instead of 'objects' because in UML 2, the life lines in sequence diagrams correspond to parts, not to individual instances and are therefore not underlined. Yes, it is common practice to let an actor send messages directly to parts of the system, not to the system as a whole. I prefer to avoid to insert some partecipant like "system" or "application" in the sequence. Now I'm making a sequence for "get information about shipping" use case and I have made this:Ĭan i use "DeliveredProduct" as abstraction of the part of the system that "handle" the information about shipping processing? I don't insert some User class because the system doesn't mantain any information about user (they access directly with some shipping code), it's right?. Storage class: Wich is associate with DeliveredProduct and mantain information about wich product are in a specific Storage.DeliveredProduct class: that describe the delivered product, having a "state" and "shipping code" attribute and some method like (getPosition, computeShippingCode etc.).So I made a use case diagram, a class diagram in wich there are only: Allow user to receive information about shipping of specific product starting from a shipping code( if is on way the position, if is arrived the storage in wich is stored).The functional requisites for the system are: Its main purposes are encapsulation and dependency minimation as well as simplifying division of labor and structuring your system at design time.Can an actor "talk" directly with an object of the system in a sequence? exampleįor an homework I need to model a "tracking service" for some shipping company. You can roughly compare it to the concept of namespaces in C++. Since you have a C++ background, the concept of packages is probably not known to you. Sequence diagrams are typically associated with use case realizations in the Logical View of the system under development It depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario. Plotting diagrams of packages and dependencies helps you keep an application's dependencies under control.Ī sequence diagram shows object interactions arranged in time sequence. These diagrams correspond well to common programming structures. People find package diagrams extremely useful on larger-scale systems to get a picture of the dependencies between major elements of a System. The dependencies between these packages can be adorned with labels / stereotypes to indicate the communication mechanism between the layers. Package diagrams can use packages that represent the different layers of a software system to illustrate the layered architecture of a software system. Package diagrams can use packages containing use cases to illustrate the functionality of a software system. Well, some googling would have brought up the answers in a few seconds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |