1 / 24

Chapter 7: The Object-Oriented Approach to Requirements

Chapter 7: The Object-Oriented Approach to Requirements. Systems Analysis and Design in a Changing. The Unified Modeling Language and the Object Management Group. Object-oriented modeling notation is Unified Modeling Language (UML)

Mia_John
Télécharger la présentation

Chapter 7: The Object-Oriented Approach to Requirements

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. Chapter 7: The Object-Oriented Approach to Requirements Systems Analysis and Design in a Changing

  2. The Unified Modeling Language and the Object Management Group • Object-oriented modeling notation is Unified Modeling Language (UML) • UML was presented to Object Management Group (OMG) as standard modeling technique • Purpose of Object Management Group • Promote theory and practice of object technology for development of distributed systems • Provide common architectural framework for OO Systems Analysis and Design in a Changing World, 3rd Edition

  3. Object-Oriented Requirements • Systems development process starts with identification of events and things • Events are business processes that new system must address • Things are problem domain objects involved in business process Systems Analysis and Design in a Changing World, 3rd Edition

  4. Object-Oriented Approach Models • Class diagram – definition of system components • Use case diagrams and use case descriptions – show user roles and how they use the system • Systems sequence diagrams (SSDs) – define inputs and outputs and sequence of interactions between user and system for a use case • Statechart diagrams – describe states of each object • Activity diagrams – describe user activities Systems Analysis and Design in a Changing World, 3rd Edition

  5. Requirements Diagrams: Traditional and OO Models Systems Analysis and Design in a Changing World, 3rd Edition

  6. The System Activities – A Use Case / Scenario View • Use case analysis used to identify and define all business processes that system must support • Use Case - single function performed by system for those who use that function • Actors • Role played by user • Outside automation boundary and organization Systems Analysis and Design in a Changing World, 3rd Edition

  7. Simple Use Case with an Actor Systems Analysis and Design in a Changing World, 3rd Edition

  8. Use Case Diagram with System Boundary Systems Analysis and Design in a Changing World, 3rd Edition

  9. Use Case of Customer Support System Systems Analysis and Design in a Changing World, 3rd Edition

  10. All Use Cases Including Customer Systems Analysis and Design in a Changing World, 3rd Edition

  11. Example of Order-Entry Subsystem with <<Includes>> Use Cases(Figure 7-6) <<includes>> Common Subroutines Systems Analysis and Design in a Changing World, 3rd Edition

  12. Developing a Use Case Diagram • Starting points for use case development • Use event table • Identify all actors of the system • Identify functions actors perform with system • Develop flow of activities to identify various scenarios • Common internal use cases can be identified and separated into different use cases Systems Analysis and Design in a Changing World, 3rd Edition

  13. Brief Description of Create New OrderUse Case Systems Analysis and Design in a Changing World, 3rd Edition

  14. Intermediate Description of the Telephone Order Scenario for Create New Order Systems Analysis and Design in a Changing World, 3rd Edition

  15. Intermediate Description of the Web Order Scenario for Create New Order Systems Analysis and Design in a Changing World, 3rd Edition

  16. Fully Developed Description of Telephone Order Scenario for Create New Order Systems Analysis and Design in a Changing World, 3rd Edition

  17. Fully Developed Description of Web Order Scenario for Create New Order Systems Analysis and Design in a Changing World, 3rd Edition

  18. Activity Diagram: Telephone Order Scenario Systems Analysis and Design in a Changing World, 3rd Edition

  19. Activity Diagram: Web Order Scenario Systems Analysis and Design in a Changing World, 3rd Edition

  20. Problem Domain Modeling – The Domain Model Class Diagram • Class diagram is focal point of object-oriented development • Provides definition of system components • Contains important class structural information for implementation with object-oriented programming • Provides conceptual data model to describe classes for database definition • Consists of problem domain classes and implementation classes Systems Analysis and Design in a Changing World, 3rd Edition

  21. RMO Domain Model Class Diagram Systems Analysis and Design in a Changing World, 3rd Edition

  22. Relationships Between OO Requirements Models Systems Analysis and Design in a Changing World, 3rd Edition

  23. Use Case Diagram for Inventory System Systems Analysis and Design in a Changing World, 3rd Edition

  24. Relationships Between OO Requirements Models (Figure 7-28) Systems Analysis and Design in a Changing World, 3rd Edition

More Related