1 / 14

Week 10: Object Modeling (1)Use Case Model

MSIS 670: Object-Oriented Software Engineering. Week 10: Object Modeling (1)Use Case Model. Figure 1: UML Models using Use-Case Driven Approach (Rosenburg, 1999). Performing Object Oriented Analysis (OOA).

sopoline-mendoza
Télécharger la présentation

Week 10: Object Modeling (1)Use Case Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MSIS 670: Object-Oriented Software Engineering Week 10: Object Modeling (1)Use Case Model

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

  3. 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. 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. 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. 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. • Ause case: a behaviorally related sequence of steps (a scenario), both automated and manual for the purpose of completing a single business task.

  7. Use Case Model Composition

  8. Developing Use Case Diagrams • Identify actors • Determine how these actors will get value from the system • Provide a simple and accessible view of the users and their use of the system

  9. A B C D E F

  10. Relationships Between Use Cases • Communicates b. Uses c. Extends

  11. 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

  12. Use-case diagram for a university registration system

  13. Class Exercise 1: Use Case Diagram • (see handout)

More Related