Lecture 2: Business Use Cases and Actors - How to identify them

Slides:



Advertisements
Similar presentations
USE CASE MODELLING A use case is a scenario that describes the use of a system by an actor to accomplish a specific goal. An actor is a user playing a.
Advertisements

Karolina Muszyńska Based on:
SYS366 The Last Stage in Analysis: System Use Case Descriptions created through the Use Case Authoring Process.
System definition and boundaries Subsystems, environment, connections, dependencies Payroll Rules, contracts Working time Reductions, tax Accounting and.
Introduction To System Analysis and Design
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
Lecture 2: Businesses and Business Processes  archaic : purposeful activity : BUSYNESSBUSYNESS  usually commercial or mercantile activity engaged in.
1 Chapter 5: The F1ive Steps in Problem Analysis The five steps in problem analysis. Team Skill 1.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
Documenting Requirements using Use Case Diagrams
Use Case Modeling. Kendall & Kendall© 2005 Pearson Prentice Hall18-2 Commonly Used UML Diagrams The most commonly used UML diagrams are: – Use case diagram,
Lecture 4 Business Use Cases: How to document them 1 SYS366.
SYS366 Week 6 - Lecture 1 Business Use Cases: How to Identify them & How to Document them.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Computer System Analysis
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
The Next Stage in Analysis: Systems Use Case Diagrams 1 SYS366.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Faculty of Computer & Information Software Engineering Third year
BTS330: Business Requirements Analysis using OO Lecture 5: The Importance of Stakeholders.
Lecture: The Importance of Stakeholders.  Objective of the requirements capture and analysis phases is to understand business processes and develop requirements.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
1 Identifying System Requirements. 2 Agenda Identifying System Requirements –Stakeholder Needs –Features Project Scope Stakeholder Classifications.
1 SYS366 Business Use Case Descriptions. 2 Today Identifying Business Use Cases Documenting Business Use Cases.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 SYS366 Business Use Cases and Business Actors: How to Identify Them.
1 SYS366 Lecture - Business Use Cases How to Identify Them.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 3 Use Cases.
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
1 BTS330 Lecture: Businesses and Business Processes.
1 SYS366 Lecture Requirements Gathering: Stakeholders.
1 SYS366 Lecture: Businesses and Business Processes.
Unit 2  Topic:  Company organization chart  Company objective.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Lecture: The Importance of Stakeholders SYS366. Identifying Requirements Objective of the requirements capture and analysis phases is to understand business.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
1 SYS366 Business Use Cases. 2 Today Business Use Cases Identifying Stakeholders & Actors.
Lecture 21 Introduction to System Development Life Cycle - Part 1.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
1 BTS330 Week 4 - Lecture 1 Businesses and Business Processes.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Lecture 5d: Systems Use Case Descriptions.  Review  Systems Use Case Descriptions  Systems Use Case Authoring SYS3662.
1 SYS366 More on (Systems) Use Cases. 2 Identifying Actors and Systems Use Cases Requirements Gathering Need to find out what the user requires in the.
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Introduction to Rational Rose 2000 Create Use Case Model.
Chapter 5 – System Modeling
IST 311 – Object-Oriented Design & Software
Business Process Management Practice 2: Process Identification
CompSci 280 S Introduction to Software Development
Business and IT modeling Car Rental example Alar Krist Alar
Business Processes A business process describes a set of activities that are necessary to complete a response to a stimulus applied to an organization.
Requirements Elicitation Techniques
Chapter 5 – System Modeling
Objectives Explain the purpose and goal of the selling function
The Next Stage in Analysis: Systems Use Case Diagrams
The Next Stage in Analysis: Systems Use Case Diagrams
Online Vehicle Rental System by CustomSoft.  Objective: Online Vehicle Rental system is developed by CustomSoft to automate vehicle.
Week 2- Lecture 2 Business Processes: What Are They?
Software Design Lecture : 14.
BUSINESS ACTIVITIES Identify the three types of businesses
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Preparation for Third Party Audit
FW Product and Base Processes
Week 8 Lecture 1: Identifying Actors and Activities
Requirements Engineering
Objectives Explain the purpose and goal of the selling function
Use cases Dr. X.
Presentation transcript:

Lecture 2: Business Use Cases and Actors - How to identify them SYS366 Lecture 2: Business Use Cases and Actors - How to identify them

What is a Business Use Case? “A business use case describes how a business actor uses a business to achieve a goal and what the business does for the business actor to achieve that goal.”* *Use Case Modeling, by Bittner & Spence, p. 331.

What is a Business Use Case? “It tells the story of how the business and its actors collaborate to deliver something of value for at least one of the actors.”* *Use Case Modeling, by Bittner & Spence, p. 331.

What is a Business Use Case? “… is independent of the concrete possibilities and requirements for its (IT-related) implementation.”* *Developing Software with UML: Object-Oriented Analysis and Design in Practice, Bernard Oestereich, p. 72.

Business Use Cases How to identify a Business Use Case? Look for processes the company uses to satisfy the requests of the business actors Processes could be an event that the business needs to respond to or it could be an event where the business needs to generate some kind of response back Can include manual as well as automated processes

Business Use Cases Where does a Use case start? “At the start there is always a commercial trigger, a commercial event Customer would like to conclude a contract Customer would like to rent a vehicle Marketing department would like a statistical evaluation of reservations”* *Developing Software with UML, Object-oriented Analysis and Design in Practice,Bernard Oestereich, p. 74.

Business Use Cases Where does a Use case end? “At the end a result has been produced that has “commercial value” A vehicle registration A letter to the customer A business management evaluation”* *Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernard Oestereich, p. 74.

What is a Business Actor How to identify the Actors? Look for who is placing requirements on the system. Anybody who is directly or indirectly involved affected by the system. Directly: someone who will have direct contact with the system Indirectly: someone who does not have direct contact with the system but who is involved in the business that is supported by the system

Business Actors Example of Actors: Users of the system Other departments (Marketing, Sales) Clients or Management Customers System Administrators, Service Personnel, Training Personnel, Support Personnel System Developers, System Maintenance Personnel Buyers of the system

Business Use Cases Narrative: handle vehicle reservations and rentals. A car rental company wants a new Information System to handle vehicle reservations and rentals. The new system will provide all functions directly related to handling customers. These include customer information, reservations, vehicle rental, and invoicing. Internal Accounting, Product Planning, Vehicle Transfer are not part of the system.

Finding Business Use Cases Let’s do a lab that will show you how Business Use cases and Business Actors are used in a Rational Rose Diagram. The diagram will model the functions of one of the subsystems of the car rental company’s information system: vehicle rental (1%)