Chapter 18 Object-Oriented Systems Analysis and Design Using UML

Slides:



Advertisements
Similar presentations
Systems Analysis and Design, 7e Kendall & Kendall
Advertisements

Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
Object-Oriented Analysis and Design
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Objectives Detailed Object-Oriented Requirements Definitions
CS3773 Software Engineering Lecture 03 UML Use Cases.
Object-Oriented Analysis and Design
Chapter 15: System Modeling with UML
Systems Analysis and Design in a Changing World, Fourth Edition
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
© 2005 Prentice Hall3-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Chapter 21 Object-Oriented Analysis
Object-Oriented Systems Analysis and Design Using UML
Use Case Modeling.
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Detailed Object-Oriented Requirements Definitions
Unified Modeling Language
The chapter will address the following questions:
Chapter 7: The Object-Oriented Approach to Requirements
USE Case Model.
Object-Oriented Systems Analysis and Design Using UML
Objectives Detailed Object-Oriented Requirements Definitions
4 2009/10 Object Oriented Technology 1 Topic 4: The Object-Oriented Approach to Requirements Adopted from: Ch.7 The Object-Oriented Approach to Requirements.
Systems Analysis and Design in a Changing World, Fifth Edition
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
For accurate communication, since a project can have several participants, each from different background. Represent a given aspect of the system We will.
Systems Analysis and Design in a Changing World, 3rd Edition
Chapter 5 Models and UML Notation for The Object-Oriented Approach.
IT 21103/41103 System Analysis & Design. Chapter 05 Object Modeling.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Use Case Modeling Chapter 7 Part of Requirements Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
1 Structuring Systems Requirements Use Case Description and Diagrams.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
Slide 12A.1 © The McGraw-Hill Companies, 2005 Object-Oriented and Classical Software Engineering Sixth Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach.
Object-Oriented Systems Analysis and Design Using UML
Chapter 7 The Object-Oriented Approach to Requirements.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Systems Analysis and Design in a Changing World, Fourth Edition
4-1 © Prentice Hall, 2007 Topic 4: Structuring Systems Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Object-Oriented Systems Analysis and Design Using UML Systems Analysis and Design,
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Use Cases and Use Case Diagrams Reporter: 陳雅萍. Outline Use cases, actors Organizing use cases Modeling the behavior of an element Use case diagrams Common.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
Use Cases UML. Use Cases What are Use Cases?  A statement of the functionality users expect and need, organized by functional units  Different from.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases
Object-Oriented Systems Analysis and Design Using UML
Unified Modeling Language
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Chapter 9 Use Cases.
Unified Modeling Language
Use Case Modeling Part of the unified modeling language (U M L)
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

Chapter 18 Object-Oriented Systems Analysis and Design Using UML Kendall & Kendall Sixth Edition

Object-Oriented Overview Object-oriented (o-o) techniques work well in situations where complicated systems are undergoing continuous maintenance, adaptation, and design. The Unified Modeling Language (UML) is an industry standard for modeling object-oriented systems. Reusability is the main goal. Kendall & Kendall © 2005 Pearson Prentice Hall

© 2005 Pearson Prentice Hall Class Symbol Kendall & Kendall © 2005 Pearson Prentice Hall

Commonly Used UML Diagrams The most commonly used UML diagrams are: Use case diagram, describing how the system is used. The starting point for UML modeling. Use case (not a diagram). Activity diagram. Each use case may create one activity diagram. Kendall & Kendall © 2005 Pearson Prentice Hall

Commonly Used UML Diagrams The most commonly used UML diagrams (continued): Sequence diagram, showing the sequence of activities and class relationships. Each use case may create one or more sequence diagrams. A collaboration diagram is an alternative to a sequence diagram. Kendall & Kendall © 2005 Pearson Prentice Hall

Commonly Used UML Diagrams The most commonly used UML diagrams (continued): Class diagram, showing classes and relationships. Sequence diagrams and CRC cards are used to determine classes. Statechart diagram. Each class may create a statechart diagram, useful for determining class methods. Kendall & Kendall © 2005 Pearson Prentice Hall

© 2005 Pearson Prentice Hall Use Case Diagram A use (yoos) case describes what the system does, not how it does the work. The use case model reflects the view of the system of the user outside of the system. Symbols are: Actor, a stick figure. Use case, an oval. Connecting lines. Kendall & Kendall © 2005 Pearson Prentice Hall

© 2005 Pearson Prentice Hall Actors Represent role played by one or more users Exist outside of the system May be a person, another system, a device, such as a keyboard or Web connection Can initiate an instance of a use case May interact with one or more use cases and a use case may involve one or more actors Kendall & Kendall © 2005 Pearson Prentice Hall

© 2005 Pearson Prentice Hall Use Case Consists of three things: An actor (user) that initiates an event. An event that triggers a use case. The use case that performs the actions triggered by the event. Kendall & Kendall © 2005 Pearson Prentice Hall

© 2005 Pearson Prentice Hall Use Case (Continued) Better to create fewer use cases 20 use cases for a large system 50 use cases would be the maximum for a large system Can nest use cases, if needed Kendall & Kendall © 2005 Pearson Prentice Hall

Use Case Relationships Communicates Connect an actor to a use case Includes Use case contains a behavior that is common to more than one use case. The common use case is included in other use cases. Dotted arrow points toward common use case. Kendall & Kendall © 2005 Pearson Prentice Hall

Use Case Relationships (Continued) Extends A different use case handles variations or exceptions from the basic use case. Arrow goes from extended to basic use case. Generalizes One thing is more general than another thing. Arrow points to the general thing. Kendall & Kendall © 2005 Pearson Prentice Hall

Use Case Relationships Kendall & Kendall © 2005 Pearson Prentice Hall

Steps for Creating a Use Case Model The steps required to create a use case model are: Review the business specifications and identify the actors within the problem domain. Identify the high-level events and develop the primary use cases that describe the events and how actors initiate them. Kendall & Kendall © 2005 Pearson Prentice Hall

Steps for Creating a Use Case Model The steps required to create a use case model are (continued): Review each primary use case to determine possible variations of flow through the use case. Develop the use case documents for all primary use cases and all important use case scenarios. Kendall & Kendall © 2005 Pearson Prentice Hall

© 2005 Pearson Prentice Hall Example Kendall & Kendall © 2005 Pearson Prentice Hall