Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.

Slides:



Advertisements
Similar presentations
Ver 1,12/09/2012Kode :CIA-230 Anal-Perc.SistemFASILKOM PERTEMUAN-4 Chapter 4. Use Case Analysis.
Advertisements

© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
© Copyright 2011 John Wiley & Sons, Inc.
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
Objectives Detailed Object-Oriented Requirements Definitions
CS3773 Software Engineering Lecture 03 UML Use Cases.
Unified Modeling Language Sequence Diagrams Chapter 2 (JIA)
Use-case Modeling.
Systems Analysis and Design in a Changing World, Fourth Edition
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Use Case Modeling.
UFCEPM-15-M Object-oriented Design and Programming Jin Sa.
Use Case Diagram.
Unified Modeling Language
Object-Oriented Analysis and Design
Chapter 7: The Object-Oriented Approach to Requirements
USE Case Model.
Software Engineering 2003 Jyrki Nummenmaa 1 USE CASES In this lecture: Use cases - What are use cases? - Why to use use cases? - How to write.
Chapter 5 – System Modeling
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
Understanding User Requirements. Documenting Use Cases 2 At this stage of the exploration, the participants should be thinking of essential use cases.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Eng. Mohammed Timraz Electronics & Communication Engineer University of Palestine Faculty of Engineering and Urban planning Software Engineering Department.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Chapter 9 요구사항 모델링: 시나리오 기반 방법론 Requirements Modeling: Scenario-Based Methods 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim.
UML – Unified Modeling Language Use-Case Diagrams.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
UML-1 3. Capturing Requirements and Use Case Model.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
UML-1 8. Capturing Requirements and Use Case Model.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
Drawing System Sequence Diagrams
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of.
Systems Analysis and Design in a Changing World, Fourth Edition
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
UML (Unified Modeling Language)
Chapter 5 System Modeling (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
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.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
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.
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.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
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 Cases Discuss the what and how of use cases: Basics Examples Benefits Parts Stages Guidelines.
Chapter 5 – System Modeling
Use Case Analysis Chapter 6.
CompSci 280 S Introduction to Software Development
Welcome to M301 P2 Software Systems & their Development
Use Cases Discuss the what and how of use cases: Basics Benefits
Chapter 5 – System Modeling
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Systems Analysis and Design 5th Edition Chapter 4. Use Case Analysis
Chapter 9 Requirements Modeling: Scenario-Based Methods
Software Design Lecture : 15.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Use Case Modeling Part of the unified modeling language (U M L)
Week 8 Lecture 1: Identifying Actors and Activities
Software Engineering Lecture #6
Presentation transcript:

Use Case What is it?

Basic Definition Of who can do what within a system? TemplateDiagramModelDescription

Purpose of use case Describe system from user’s point of view ◦Describe interaction between user and system Indicate system response to request/trigger originating outside the system (by user) ◦Provide sequence of steps involved in interaction ◦Depicts functional requirements of the system for a task (how task/goal achieved)

Focus on the user end Users ◦End user ◦Other systems ◦Hardware devices

Why Use Case? Use User focus Case Complete series of events Complete series of events for one particular use of a system Use case simplified from usage scenarios/usage case

Who creates use case? End users Systems Analysts Use case

Who uses use case? Systems engineersSoftware engineers

Requirements of use case Use case should: ◦Describe what the system shall do for the actor to achieve a particular goal. ◦Include no implementation-specific language. ◦Be at the appropriate level of detail. ◦Not include detail regarding user interfaces and screens. This is done in user-interface design. From

Applications of use case Systems design Programming Object-oriented design UML (unified modeling language) Wherever functional requirements need to be captured Business use Software use

Use case diagram (in UML) Diagram used in UML (unified modeling language) in software engineering e_diagram e_diagram

Use case template Sample template – see se_case for what would go in each of fields in the right hand column of this template se_case Fill in descriptions Use case name Version Goal Summary Actors Preconditions Triggers Basic course of events Alternative paths Post conditions Business rules Notes Author and date