 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users.

Slides:



Advertisements
Similar presentations
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Advertisements

CPSC 333: Foundations of Software EngineeringJ. Denzinger 2.2. Use Cases: Scenario based requirements modeling Recommended: Booch, Rumbaugh, Jacobson:
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.
Use Case Model Shinta P.. UML Actor An actor is behaviored classifier which specifies a role played by an external entity that interacts with the subject.
Chapters 7 & 9 System Scope
Use Case Diagram © copyright 2001 SNU OOPSLA Lab..
CT1404 Lecture 2 Requirement Engineering and Use Cases 1.
Use-case Modeling.
1 CS 426 Senior Projects Chapter 4: Use Case Modeling [Arlow and Neustadt, 2002] February 8, 2007.
Use Case modelling How to go from a diagram to a further definition.
Documenting Requirements using Use Case Diagrams
Object Oriented Analysis Process
Chapter 21 Object-Oriented Analysis
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Functional Modeling Chapter 6.
Use Case Modeling.
Unified Modeling Language
USE Case Model.
Chapter 5: Modeling Systems Requirements: Events and Things
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Classification of UML Diagrams
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
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?
Use Cases Week 8 CMIS570. Refresher – Class Diagrams Appointment scheduling example Car Rental example E-Commerce example.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
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.
UML-1 3. Capturing Requirements and Use Case Model.
UML-1 8. Capturing Requirements and Use Case Model.
® 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.
1 Use Case Diagrams Use Case Actor Use case description Use case realization (Scenario) Use case relationships –Extends –Uses.
Modeling System Requirements: Events and Things. Objectives Explain the many reasons for creating information system models Describe three types of models.
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.
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.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 7: Requirements Engineering Software Engineering: A Practitioner’s Approach, 6/e.
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.
Chapter 7 The Object-Oriented Approach to 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.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Scenario A scenario is a sequence of steps describing an interaction between a user and a system. Use case is a set of scenarios tied together by a common.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
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.
Unit-3 Identifying use cases Object Analysis Classification
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.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Slide 1 Project team 1. gathers requirements from the users (Ch. 4) 2. models the overall business process using __________ 3. identifies _________ using.
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.
Developing Business Processes Developing an activity diagram of the business processes can provide us with an overall view of the system.
Storyboarding and Game Design SBG, MBG620 Full Sail University
Use Case Model.
Use case Diagram.
Unified Modeling Language
Requirements Elicitation and Elaboration
Object-Oriented Analysis Principles using UML
Object Oriented Analysis and Design
Presentation transcript:

 Need to Gather requirements and other related information  Use case Modeling ◦ What the system will do for the users

 A client makes a call that is taken by the operator, who determines the nature of the problem. Some calls can be answered immediately, other calls require research and a return call.

 The process consists of the following steps:  1. Identify the actors: ◦ Who is using the system? ◦ Or, in the case of a new system, who will be using the system?  How would such information be gathered?  2. Identify the requirements (use cases) which the system must support.

 The use-case model describes the uses of the system and shows the courses of events that can be performed.  Use case defines what happens in the system when a use case is performed. ◦ Model ◦ Description  The use-case model tries to systematically identify uses of the system and therefore the system's responsibilities.

 Use cases are scenarios for understanding system requirements.  A use case is an interaction between users and a system.  The use-case model captures the goal of the user and the responsibility of the system to its users.

 The description of a use case defines what happens in the system when the use case is performed.  In essence, the use-case model defines the outside (actors) and inside (use case) of the system's behavior.  A good starting point for: ◦ Designing the GUI (prototype) ◦ Testing the system

 The term actor represents the role a user plays with respect to the system.  When dealing with actors, it is important to think about roles rather than people or job titles.

 Candidates for actors can be found through the answers to the following questions: ◦ Who is using the system? Or, ◦ Who is affected by the system? Or, ◦ Which groups need help from the system to perform a task?

◦ Who affects the system? ◦ Which user groups are needed by the system to perform its functions? These functions can be both main functions and secondary functions, such as administration. ◦ Which external hardware or other systems (if any) use the system to perform tasks?

◦ What problems does this application solve (that is, for whom)? ◦ And, finally, how do users use the system (use case)? What are they doing with the system?

 These relationships are shown in a use-case diagram: ◦ Communication. ◦ Uses. ◦ Extends.

 The use association occurs when you are describing your use cases and notice that some of them have common subflows.  The use association allows you to extract the common subflow and make it a use case of its own.

 The extends association is used when you have one use case that is similar to another use case but does a bit more or  Is more specialized; in essence, it is like a subclass.