{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

tutorial3

tutorial3 - Tutorial 3 UML CSC2120& ERG3820 Prepared...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Tutorial 3 -- UML CSC2120 & ERG3820 Prepared by (Cai Yi)CY Outline • General picture of UML – What is UML – UML first pass (General picture of UML) – UML second pass (detail about user case diagram) • Conclusion What is UML • UML (Unified Modeling Language) – An emerging standard for modeling object-oriented software. – Easiest answer:“The UML is the standard language for specifying, visualizing, constructing, and documenting all the artifacts of a software system.” – Resulted from the convergence of notations from three leading object- oriented methods: • OMT (James Rumbaugh) • OOSE (Ivar Jacobson) • Booch (Grady Booch) • Reference: “The Unified Modeling Language User Guide”, Addison Wesley, 1999. • Supported by several CASE tools – Rational ROSE – Together/J – ... Concept of an Object • Object: a thing you can interact with • State of an object: all data which it currently encapsulates • Behavior: the way an object acts and reacts, in terms of its state changes and message passing • Identity: An object is normally referred to by a name • Attributes: instance variables or data members of an object • Class: describes a set of objects with an equivalent role or roles in a system UML First Pass: Use Case Diagrams • Use case diagrams – Describe the functional behavior of the system as seen by the user. – Model the users and their interactions with the system at a very high level of abstraction – Serve as a structuring tool for more concrete descriptions of a system’s functionality like, for example, sequence diagrams. UML First Pass: Use Case Diagrams WatchUser WatchRepairPerson ReadTime SetTime ChangeBattery Actor Use case Package SimpleWatch Use case diagrams represent the functionality of the system from user’s point of view How to find the actors? • The first thing I would do when starting my analysis process is to ask,“who is going to interact with this system?” • Once you’ve identified how your actors will be interacting with the system, just do document your use cases. UML First Pass: Class Diagrams • Class diagrams – Describe the static structure of the system – Show the classes of the program code, their attributes and operations , and the relationships and dependencies between them – May be seen as a special kind of E/R Diagrams – Used for data modeling in the early development phases and later refined and enriched with additional attributes and operations •...
View Full Document

{[ snackBarMessage ]}

Page1 / 33

tutorial3 - Tutorial 3 UML CSC2120& ERG3820 Prepared...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon bookmark
Ask a homework question - tutors are online