1. Spring 2007 Week 10: Object Modeling (1)Use Case Model IFS410: Advanced Analysis and Design

2. 3/27/2007 Figure 1: UML Models using Use-Case Driven Approach (Rosenburg, 1999)

3. 3/27/2007 Performing Object Oriented Analysis (OOA) –OOA requires that we identify the objects, their data attributes, associated behavior, and relationships which support the required business system functionality. –We perform object modeling to document the identified objects, the data and behavior they encapsulate, plus their relationships with other objects.

4. 3/27/2007 Performing OOA (cont.) Two general activities when performing object oriented analysis: –Gathering requirements through use case analysis –Finding and identifying the business objects. –Organizing the objects and identifying their relationships in class diagrams

5. 3/27/2007 Gathering Requirements A system’s requirements consist of a document (or a collection of documents) that describes the functionality that system provides. –Use case models show discrete groups of system users as they interact with the system.

6. 3/27/2007 Dynamic Modeling: Use Case Model Use case modeling breaks down the entire scope of system functionality into many smaller statements of system functionality called use cases or business events. –A use case: a behaviorally related sequence of steps (a scenario), both automated and manual for the purpose of completing a single business task.

7. 3/27/2007 Use Case Model Composition

8. 3/27/2007 Developing Use Case Diagrams 1.Identify actors 2.Determine how these actors will get value from the system 3.Provide a simple and accessible view of the users and their use of the system

9. 3/27/2007

10. A B C D E F

11. Relationships Between Use Cases a.Communicates b.Uses c.Extends

12. 3/27/2007 Use of Includes and Extends Relationships Includes (uses): the base (abstract) use case depends on the included use case because it absorbs its behavior Extends: the base (abstract) use case does not include the subordinate use case, instead, the extension use case depends on the base use case

13. 3/27/2007 Use-case diagram for a university registration system

14. 3/27/2007 Class Exercise 1: Use Case Diagram (see handout)