Stimulate 2005 Instructor: Luz M. Quiroga University of Hawaii Information and Computer Science / Library and information Science POST.

Slides:



Advertisements
Similar presentations
Suppose the employees of the university are not billed for
Advertisements

Use Case Diagrams.
Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself A set.
Karolina Muszyńska Based on:
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.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
2008/03/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Object-Oriented Analysis and Design
January Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box.
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing systems process: Use Case Diagram.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Use Case Modeling.
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Unified Modeling Language
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
State diagrams Interaction diagrams –Sequence diagrams –Collaboration diagrams Object orientation Part 4: Dynamic Modeling.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Chapter 5 Models and UML Notation for The Object-Oriented Approach.
Kyung Hee University System Functional Model OOSD 담당조교 석사과정 이정환.
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George.
Chapter 16 Applying UML and Patterns Craig Larman
1 Structuring Systems Requirements Use Case Description and Diagrams.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 8 (Chapter 7) MODELING SYSTEM REQUIREMENTS WITH USE.
Use Case Model Use case diagram.
1 Modeling System Requirements with Use Cases. 2 Why Do We Need Use Cases? Primary challenge in a system design process –ability to elicit correct and.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Use Case Model Use case diagram. Relevant Requirements Artifacts Use-Case Model Supplementary Specification Use-Case Specifications... Glossary Actors.
Modern Systems Analysis and Design Fifth Edition
UML Diagrams: Use Case Diagrams Prof. Hany Ammar, CSEE Dept., WVU.
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.
New Perspective Based on how the system is used. What Is a Use Case? A case of how the system is used. –A behaviourally related sequence of interactions.
4-1 © Prentice Hall, 2007 Topic 4: Structuring Systems Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
UML (Unified Modeling Language)
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.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
Ondřej Přibyl Faculty of Transportation Sciences, CTU DESIGN OF ITS SYSTEMS Project support 1 3 PROJECT SUPPORT Use cases.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
UML CSE 470 : Software Engineering. Unified Modeling Language UML is a modeling language to express and design documents, software –Particularly useful.
Sept Ron McFadyen1 Include Relationship UC1:Process Sale … Main Success Scenario … 7. Customer pays and System handles payment. … Extensions.
UML CSE 470 : Software Engineering. Unified Modeling Language UML is a modeling language to express and design documents, software –Particularly useful.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing system processes: Use Case Diagram Updated.
Use Cases -Use Case Diagram
WHAT IS A Context Diagram?
Chapter 7 Appendix A Object-Oriented Analysis and Design: Use Cases
Object-Oriented Modeling
Lec-5 : Use Case Diagrams
Analyzing system processes: Use Case Diagram 2/2
M.M. Pickard, PhD A Primer on Use Cases (Reference: UML Superstructure Specification, v2.1.1)
Use Case Model Use case diagram.
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
WHAT IS A Use Case Diagram?
Use Cases & Use Case Diagrams
Chapter 20 Object-Oriented Analysis and Design
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Appendix A Object-Oriented Analysis and Design
Use Case Model Use case diagram – Part 2.
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

Stimulate 2005 Instructor: Luz M. Quiroga University of Hawaii Information and Computer Science / Library and information Science POST 314b; System Analysis and Design (SA&D) Object Oriented modeling Part 2: Use case modeling

Object Orientation Application to system analysis (Osborne, Sinha)

Use Case Modeling Applied to analyze functional requirements of the system Performed during the analysis phase to help developers understand functional requirements of the system without regard for implementation details Use Case –A complete sequence of related actions initiated by an actor Actor –An external entity that interacts with the system

Use Case Modeling Use cases are always initiated by an actor Use cases represent complete functionality of the system Use cases may participate in relationships with other use-cases Use cases may also use other use cases

Use-case Modeling (Fig. A1 - Source: Sinha) A use case consist of actors (stick figure) and use case (oval) It represent the typical interactions user - systems Several relationships used to explain how a use case is related to use cases and uses: association / extend / include

Use-case Modeling (Fig. A1- Source: Sinha) Association: communication between actor and use case Example: Student using class registration Depicted as a line ; typically represents two way communication between the use case and the actor, then no arrowheads needed (if only one way then use solid arrowhead)

Use-case Modeling (Fig. A1- Source: Sinha) A use case may participate with other uses cases: extend relationship (hollow triangle toward the extended case; > label) Class registration is always performed; the extension: e.g. registration for special classes is performed only under special circumstances

Use-case Modeling (Fig. A1- Source: Sinha) Another kind of relationship is “include”, labeled > It implies that one cases uses another while executing (aggregation; part – whole; functional decomposition) When a manager reorder supplies, the sales and inventory data are tracked.

Use case exercise: Valacich app. A (author of the chapter: Sinha) Exercise 2. p. 422; reference to figure A1 of previous slides Suppose that the employees of the university are not billed by tuition. Their spouse do not get a full tuition waiver, but pay for only 25 % of the total tuition. Extend the use-case diagram of fig. A-1 to capture these situations Draw the diagram with MS- Visio