Use Cases Week 8 CMIS570. Refresher – Class Diagrams Appointment scheduling example Car Rental example E-Commerce example.

Slides:



Advertisements
Similar presentations
Week 2 The Object-Oriented Approach to Requirements
Advertisements

Chapters 7 & 9 System Scope
Agenda What is a Use Case? Benefits of the Use Cases Use Cases vs. Requirements document Developing the Use Case model System Actor Use Case Use Case.
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users.
Drawing System Sequence Diagrams
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Data.
Documenting Requirements using Use Case Diagrams
© 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.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
NJIT Drawing System Sequence Diagrams Chapter 10 Applying UML and Patterns Craig Larman Presented by Anuradha Dharani.
Functional Modeling Chapter 6.
© 2005 course technology1 1 1 University Of Palestine UML for The IT Business Analyst A practical guide to Object Oriented Requirement Gathering Hoard.
USE Case Model.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
CMIS 470 Structured Systems Design
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Intro to UML - OO Class Diagrams Week 5 CMIS570. Plan for Tonight Object terms Unified Modeling Language history Class Diagrams Intro to Oracle Oracle.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
CMIS 470 Structured Systems Design Object-Oriented Analysis and Design – Sequence Diagrams; BPP details Week 5.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Object-Oriented Sequence Diagrams
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Use Cases 1. Last week  Introduction to software engineering  How is it different from traditional engineering?  Introduction to specification  Operational.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
IS3320 Developing and Using Management Information Systems Lecture 9: Use Cases and Scenarios Rob Gleasure
1 Structuring Systems Requirements Use Case Description and Diagrams.
1 Chapter 4 Analyzing End-to-End Business Processes.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Drawing System Sequence Diagrams
Use Case Model Use case diagram.
10 October, 2007Information System Design IT60105, Autumn 200 Information System Design IT60105 Lecture 17 Collaboration Diagrams.
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.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
Analysis Modeling CpSc 372: Introduction to Software Engineering
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Unit-3 Identifying use cases Object Analysis Classification
Understanding Requirements
Use Case Diagrams Lecture Oo14 Use Cases. References n Booch, et al, The Unified modeling Language User’s Guide, AWL, 1999, Chapt 16 & 17 n Fowler & Scott,
Spring 2007 Week 10: Object Modeling (1)Use Case Model IFS410: Advanced Analysis and Design.
UML - Development Process 1 Software Development Process Using UML.
CS223: Software Engineering
Larman chapter 61 Use cases Larman chapter 6. 2 Fig. 6.1.
Use Case Model Use case description.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
Use Case Diagrams. Introduction In the previous Lecture, you saw a brief review of the nine UML diagrams. Now that you have the clear, you'll start to.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
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.
ACO 101: Use cases What do the users do?. When building a system You begin with the Use Case Analysis – When looking at the system as a whole, Use Case.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Use Case Analysis Chapter 6.
UML Use Case Diagrams.
Object Oriented Analysis and Design
Use Case Model Use case diagram – Part 2.
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Week 8 Lecture 1: Identifying Actors and Activities
Presentation transcript:

Use Cases Week 8 CMIS570

Refresher – Class Diagrams Appointment scheduling example Car Rental example E-Commerce example

UML diagrams 9 diagrams Used throughout SDLC Use consistent syntax and notation. Key building block is the use-case.

Use-Case Requires you to break system into use cases, small logical pieces of the system and deal with each separately. In contrast, DFDs and ERDs encompass the entire system in one diagram.

Use-Case Diagrams Graphical specification of the system’s behavior from the perspective of the user(s). Describes what the system does without describing how the system does it. They are used to identify and communicate the high-level business requirements for the system.

Use-Case contains: Actor Event/Use Case Association System boundary

Example! Patient Admission system

Example Car Rental System

Another example E-commerce system

Steps in creating a Use-Case 1. Identify use-cases (find major functions) 2. Draw the system boundary 3. Place use-cases on the diagram (6-8 use-cases per diagram) 4. Identify the actors 5. Add associations

In addition… Text documents to document use-cases since use-case diagram does not describe how those use cases are carried out by the actors. When describing the use-case, you should focus on its external behavior – how it interacts with the actors, rather than how the use case is performed inside the system.

Steps in Documentation 1. Create a use case template that has areas labeled Basic Course and Alternative Courses. 2. Ask “What happens?” 3. Ask “And then what happens?” 4. Ask, “What else can happen?

Documentation examples Patient Admission Rent a car Search by Author

TIPS Think usage scenario rather than functional requirements. Describe usage rather than attributes and methods. Don’t write use-case too tersely. Don’t ignore system responses. Don’t forget alternative courses of action

Includes statement When one use-case needs to use another use-case Two types Internal – only other use-cases reference Both external actors and internal use-cases reference

Examples Order Entry Class registration