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.

Slides:



Advertisements
Similar presentations
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Advertisements

Chapters 7 & 9 System Scope
Chapter 7 Structuring System Process Requirements
Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Unified Modeling Language
CS3773 Software Engineering Lecture 03 UML Use Cases.
Object-Oriented Analysis and Design
 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users.
Use-case Modeling.
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2002] February 8, 2007.
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
Systems Analysis and Design in a Changing World, Fourth Edition
© 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.
1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,
1 SWE Introduction to Software Engineering Lecture 15 – System Modeling Using UML.
SwE 313 Introduction to Rational Unified Process (RUP)
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2005] February 5, 2009.
Use Case Modeling.
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
UML. Overview of UML Diagrams Structural : element of spec. irrespective of time Class Component Deployment Object Composite structure Package Behavioral.
Chapter 7 Structuring System Process Requirements
Chapter 7: The Object-Oriented Approach to Requirements
Use Case Diagrams Week 1 – Lab 1.
USE Case Model.
2005/05/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Use Case What is it?. Basic Definition Of who can do what within a system? TemplateDiagramModelDescription.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Chapter 7 Structuring System Process Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
The Requirement. What is Inception? What is the vision and business case for this project? –not to define all the requirements Feasible? Buy and/or build?
Requirements Documentation CSCI 5801: Software Engineering.
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.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 Structuring Systems Requirements Use Case Description and Diagrams.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Systems Analysis and Design in a Changing World, 6th Edition
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
UML Examples PRESETED BY: MEHRAN NAJAFI SHIMA AGHTAR.
Systems Analysis and Design in a Changing World, Fourth Edition
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
4-1 © Prentice Hall, 2007 Topic 4: Structuring Systems Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
 What to do if you want to build a new house? › Buy a bunch of wood and nails and start immediately. › Or, put some blueprints to follow, and plan of.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
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.
By Mashael AlDayel Introduction to UML. What is UML? UML (Unified Modeling Language) is a graphical language that is suit-able to express software or.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
CompSci 280 S Introduction to Software Development
Systems Analysis and Design in a Changing World, Fourth Edition
WHAT IS A Context Diagram?
Business System Development
M.M. Pickard, PhD A Primer on Use Cases (Reference: UML Superstructure Specification, v2.1.1)
BTS430 Systems Analysis and Design using UML
Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer
Software Design Lecture : 15.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
CS 420/620 HCI Use Case Modeling Project Preparation
CS 425 Software Engineering
CS 425/625 Software Engineering
Presentation transcript:

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 user).  In other words, a use case describes "who" can do "what" with the system in question.

 A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use- case analysis.  Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases).

 Actor  Use-Case

 An actor specifies a role that some external entity adopts when interacting with the system directly.  It may represent a role played by: * a user * another system * a piece of hardware  Actors may be both at input and output ends of a use case

 Describes all the services required or performed by the actor.

 Use Case Names  Written in a oval  Simple Name Register Students