Art for Chapter 5, Analysis
Figure 5-1. Ambiguity: what do you see?
Figure 5-2. Products of requirements elicitation and analysis (UML activity diagram).
Figure 5-3. The analysis model is composed of the functional model, the object model, and the dynamic model. In UML, the functional model is represented with use case diagrams, the object model with class diagrams, and the dynamic model with statechart and sequence diagrams.
Figure 5-4. Analysis classes for the 2Bwatch example.
Figure 5-5. An example of multiplicity of associations (UML class diagram). A 2Bwatch has two Buttons and one LCDDisplay.
Figure 5-6. Examples of multiplicity (UML class diagram). The association between Person and SocialSecurityNumber is one-to-one. The association between Person and Car is one-to-many. The association between Person and Company is many-to-many.
Figure 5-7. Example of a hierarchical file system. A Directory can contain any number of FileSystemElements (a FileSystemElement is either a File or a Directory). A given FileSystemElement, however, is part of exactly one Directory.
Figure 5-8. Example of a nonhierarchical file system. A Directory can contain any number of FileSystemElements (a FileSystemElement is either a File or a Directory). A given FileSystemElement can be part of many Directory (ies).
Figure 5-9. Example of how a qualified association reduces multiplicity (UML class diagram). Adding a qualifier clarifies the class diagram and increases the conveyed information. In this case, the model including the qualification denotes that the name of a file is unique within a directory.
Figure 5-10. An example of a generalization hierarchy (UML class diagram). The root of the hierarchy represents the most general concept, whereas the leaves nodes represent the most specialized concepts.
Figure 5-12. Sequence diagram for the ReportEmergency use case (initiation from the FieldOfficerStation side).
Figure 5-13. Sequence diagram for the ReportEmergency use case (DispatcherStation).
Figure 5-14. Sequence diagram for the ReportEmergency use case (acknowledgment on the FieldOfficerStation).
Figure 5-16. An example of association between the EmergencyReport and the FieldOfficer classes.
Figure 5-17. Eliminating redundant association. The receipt of an EmergencyReport triggers the creation of an Incident by a Dispatcher. Given that the EmergencyReport has an association with the FieldOfficer that wrote it, it is not necessary to keep an association between FieldOfficer and Incident.
Figure 5-18. Attributes of the EmergencyReport class.
Figure 5-19. UML statechart for Incident.
Figure 5-20. An example of inheritance relationship (UML class diagram).
Figure 5-21. Analysis activities (UML activities diagram).
Figure 5-23. An example of a revision process (UML activity diagram).
Figure 5-24. A naive model of the Gregorian calendar (UML class diagram).
Home Page: http://www.cc.gatech.edu/classes/AY2001/cs3300_fall/
Download presentation source