Different Methods Of Collaboration

Good Essays
Activities: An activity represents the performance of some behavior in the workflow. Transitions: Transitions are used to show the passing of the flow of control from activity to activity. They are typically triggered by the completion of the behavior in the originating activity. Decision points: When modeling the workflow of a system it is often necessary to show where the flow of control branches based on a decision point. The transitions from a decision point contain a guard condition, which is used to determine which path from the decision point is taken. Decisions along with their guard conditions allow you to show alternate paths through a work flow. 10. Identification of analysis classes 1) use-case driven approach One of the…show more content…
In this case, we know from the use case diagram that the traveler is the actor for this use case. The use case description tells us that traveler search for the flight by giving arrival and departure city. The objective of the use case search flight is allowing the user to search for flights First begin by picking out from the description all the important things or concepts in the application domain. Our first list might include traveler, airline database, and user database. But we are only interested in those about which the system must store some information or knowledge in order to achieve its objectives. The traveler will be modeled as an actor. For the purposes of this particular use case, it is unlikely the system will need to encapsulate any further knowledge about the actor. The collaboration diagram for the above use case. Collaboration is between individual object instances, not between classes. This is shown in the diagram by the convention of writing a colon before the class name, which indicates that this is an anonymous instance of the class, rather than the class itself. Messages between classes are shown by arrows, and their sequence is indicated by the number alongside. In this example, these are not yet labeled, although some those that can be most easily related to the use case description will probably soon be given names that correspond to responsibilities of the class to which the message is
Get Access