Use Case Model Use case diagram. Relevant Requirements Artifacts Use-Case Model Supplementary Specification Use-Case Specifications... Glossary Actors.

Slides:



Advertisements
Similar presentations
Writing Good Use Cases - Instructor Notes
Advertisements

OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Object-Oriented Analysis and Design Evolutionary Requirements.
Use Case & Use Case Diagram
9/10/2004Use Case Workshop 1 CSC480 Software Engineering Workshop 1 Requirements Modeling.
Information System Engineering
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
Use-case Modeling.
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Uml and Use Cases CS 414, Software Engineering I Mark Ardis Rose-Hulman Institute January 9, 2003.
Copyright ©2004 Cezary Z Janikow 1 Use Cases n Within Requirements discipline/workflow n Verbal descriptions of important functional (behavioral, transactional,
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
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,
Unified Modeling Language 7/12/2015B.Ramamurthy1 The Unified Modeling Language™ (UML) was developed jointly by Grady Booch, Ivar Jacobson, and Jim Rumbaugh.
Use Case Analysis – continued
1 Business Models Modeling. 2 Why Model the Business Business modeling is a technique to help answer critical questions, such as: What do the workers.
USE Case Model.
RUP Requirements RUP Artifacts and Deliverables
Why Analysis Process Refer to earlier chapters Models what the system will do makes it easier for understanding no environment considered (hence, system.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
Object-Oriented Analysis - Instructor Notes
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Chapter 5 Analysis Model. Analysis model (AM) The first step in describing how the system will implement the requirements specification The first step.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Use Case Modeling. What is use case modeling? Core concepts Diagram tour When to model use cases Modeling tips Example: Online HR System.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
1 Source: IBM Academic Program IBM Software Group ® Mastering Requirements Management with Use Cases Module 3: Introduction to Use-Case Modeling.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Use Cases 1. Last week  Introduction to software engineering  How is it different from traditional engineering?  Introduction to specification  Operational.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
1 Objectives  Define key concepts of use-case modeling.  List the benefits of use-case modeling.  Find actors and use cases.  Describe their relationships.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
A Use Case Primer 1. The Benefits of Use Cases  Compared to traditional methods, use cases are easy to write and to read.  Use cases force the developers.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
1 Structuring Systems Requirements Use Case Description and Diagrams.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
Use Cases Use Cases are employed to describe the functionality or behavior of a system. Each use case describes a different capability that the system.
Writing Good Use Cases Outlining Use Cases. Process of writing use cases Find actors Find use cases Outline a use case Detail a use case  Outline the.
CSC 131 Fall 2006 Lecture # 5 UML Use Cases. UML The UML is a graphical language for  specifying  visualizing  constructing  documenting the artifacts.
Use Case Model Use case diagram.
Use Case Diagram The purpose is to communicate the system’s functionality and behaviour to the customer or end user. Mainly used for capturing user requirements.
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.
Rational Unified Process Fundamentals Module 3: Disciplines I.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Essentials of Visual Modeling w/ UML Instructor Notes
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 3: Outlining Use Cases.
UML - Development Process 1 Software Development Process Using UML.
Use Case Model Use case description.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
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.
Using Use Case Diagrams
Lec-5 : Use Case Diagrams
Chapter 5 유스케이스 개요 Introduction to Use Cases
Recall The Team Skills Analyzing the Problem (with 5 steps)
Use Case Model Use case diagram.
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Object Oriented Analysis and Design
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Use Case Model Use case diagram – Part 2.
Using Use Case Diagrams
Presentation transcript:

Use Case Model Use case diagram

Relevant Requirements Artifacts Use-Case Model Supplementary Specification Use-Case Specifications... Glossary Actors Use Cases ٥

What Is System Behavior? System behavior is how a system acts and reacts.  It is the outwardly visible and testable activity of a system. System behavior is captured in use cases.  Use cases describe the system, its environment, and the relationship between the system and its environment. ٨

What Are the Benefits of a Use-Case Model?What Are the Benefits of a Use-Case Model? OOAD o Communication o Identification o Verification End User ١٢١٢ Use Case Communication Identification Verification Domain Expert UsersUsers

Key points ▪The development team, with stakeholders involvement, writes the use cases. ▪Compared to traditional requirement methods, use cases are relatively easy to write and easier to read. ▪Free of technical or implementation details.

Use Case Diagrams  A use case diagram depicts the interactions between the system and the external actors. 6

Developing use case diagram 7 Actor is a stick figure usually an actual person using the system Connection line shows which actor participate in the use cases The use case System boundary System name

Major Concepts in Use-Case ModelingMajor Concepts in Use-Case Modeling ▪An actor represents anything that interacts with the system. ▪An actor might be: ▪ a person ▪ a company or organization, ▪a computer program, or a computer system ▪ A use case is a sequence of actions a system performs that yields an observable result of value to a particular actor. ▪Name each use case using Noun-Verb OOAD Actor UseCase ٩

Types of actor ▪Primary actor initiates the use case. ▪ Secondary actor is used to complete the use case.

10 A Step-by-Step Guide to Building the Use- Case Model ▪Step 1: Identify and Describe the Actors ▪Who uses the system? ▪Who gets information from this system? ▪Who provides information to the system? ▪Where in the company is the system used? ▪Who supports and maintains the system? ▪What other systems use this system?

11 A Step-by-Step Guide to Building the Use- Case Model ▪Step 2: Identify the Use Cases and Write a Brief Description ▪What will the actor use the system for? ▪Will the actor create, store, change, remove, or read data in the system? ▪Will the actor need to inform the system about external events or changes? ▪Will the actor need to be informed about certain occurrences in the system?

12 A Step-by-Step Guide to Building the Use- Case Model ▪Step 3: Identify the Actor and Use-Case Relationships ▪Only one actor can initiate a use case ▪Many use cases may involve the participation of multiple actors. ▪Each use case is analyzed to see what actors interact with it

13 Use case diagram

Case Study: Course Registration Problem Statement OOAD Review the problem statement provided in the Course Registration Requirements Document. Course Registration Requirements Document ٦

How Would You Read This Diagram?How Would You Read This Diagram? View Report Card Maintain Professor Information Course Catalog Register for Courses Student Login Select Courses to Teach Professor Submit Grades Registrar Billing System OOA D ١٣١٣ Maintain Student Information Close Registration

Use-Case Flow of EventsUse-Case Flow of Events ▪Has one normal, basic flow ▪Several alternative flows  Regular variants  Odd cases  Exceptional flows for handling error situations ١٥١٥