SYS366 Week 6 - Lecture 1 Business Use Cases: How to Identify them & How to Document them.

Slides:



Advertisements
Similar presentations
Karolina Muszyńska Based on:
Advertisements

Use Case Model. C-S 5462 Use case model describes what the user expects the system to do –functional requirements may describe only the functionalities.
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
SYS366 The Last Stage in Analysis: System Use Case Descriptions created through the Use Case Authoring Process.
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes.
1 SWE Introduction to Software Engineering Lecture 16 – System Modeling An Example.
Software Testing and Quality Assurance
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Feb. 13, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #9 Tuesday, Feb. 13, 2001.
Slide 11C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
Lecture 2: Businesses and Business Processes  archaic : purposeful activity : BUSYNESSBUSYNESS  usually commercial or mercantile activity engaged in.
Using Rational Rose Creating an Activity Diagram Dr. Neal CIS 480.
Documenting Requirements using Use Case Diagrams
Use Case Analysis Chapter 6.
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,
Slide 7C.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
UFCEPM-15-M Object-oriented Design and Programming Jin Sa.
Lecture 4 Business Use Cases: How to document them 1 SYS366.
Chapter 7: The Object-Oriented Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Jerry KotubaSYST39409-Object Oriented Methodologies1 Object Oriented Methodologies Week04.
Intro to UML - OO Class Diagrams Week 5 CMIS570. Plan for Tonight Object terms Unified Modeling Language history Class Diagrams Intro to Oracle Oracle.
Object-Oriented Modeling
CS 360 Lecture 6.  A model is a simplification of reality  We build models to better understand the system being developed.  We build models of complex.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Object-Oriented Sequence Diagrams
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Key Takeaway Points A use case is a business process; it begins with an actor, ends with the actor, and accomplishes a business task for the actor. Use.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
1 SYS366 Business Use Case Descriptions. 2 Today Identifying Business Use Cases Documenting Business Use Cases.
9/01RUT1 NASA OSMA SAS '01 R equirements U se case T ool James R. McCoy SRS Information Services NASA Software Assurance Technology Center
Example Template for Project Presentation
Use Case Modeling Chapter 7 Part of Requirements Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
1 Structuring Systems Requirements Use Case Description and Diagrams.
1 SYS366 Business Use Cases and Business Actors: How to Identify Them.
1 SYS366 Lecture - Business Use Cases How to Identify Them.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
1 BTS330 Lecture: Businesses and Business Processes.
Design Model Lecture p6 T120B pavasario sem.
 Week08.  Review Schedule Weeks 8-14  This week o Review last class o Introduce Class Diagrams o ICE-03 Sheridan SYST Engineering Quality Systems.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
McGraw-Hill/Irwin © 2013 The McGraw-Hill Companies, Inc., All Rights Reserved. Chapter 12 Sales/Collection Process.
What functionality of each group people will get Customer Sales Agent Sales Manager National Manager Managing Director.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
IntellAgile Copyright © 2002 Craig Larman. All rights reserved. Writing Use Cases: Requirements in Context.
Lecture 6: Chapter 4:Test-based Use case Process Modeling Dr. Taysir Hassan Abdel Hamid November 17, 2013.
1 SYS366 Business Use Cases. 2 Today Business Use Cases Identifying Stakeholders & Actors.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Technical Module C Object Modeling Objects Object – a valuable resource: Money (Account Receivable) Material (Product) Machines (Delivery Truck) Personnel.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Dissecting the Problem Document Identify potential s/w classes from a description document--a written description of the system to implement  Identify.
Chapter 11 Inheritance © 2008 Pearson Education Inc., Upper Saddle River, NJ. All rights reserved. Marilyn Bohl/Maria Rynn Tools for Structured and Object-Oriented.
1 BTS330 Week 4 - Lecture 1 Businesses and Business Processes.
System modeling and the Unified Modeling Language (UML) CS
acknowledge your understanding of this program via to Catherine
CMPE 280 Web UI Design and Development August 29 Class Meeting
Lecture 2: Business Use Cases and Actors - How to identify them
BTS430 Systems Analysis and Design using UML
Use Case Model.
Week 2- Lecture 2 Business Processes: What Are They?
Use Cases 1.
Engineering Quality Software
Week 8 Lecture 1: Identifying Actors and Activities
Presentation transcript:

SYS366 Week 6 - Lecture 1 Business Use Cases: How to Identify them & How to Document them

Today Identifying Business Use Cases Documenting Business Use Cases

Business Use Cases documents a case of using the business system and the actors who use it. “An abstract form of use case that is independent of the concrete possibilities and requirements for its (IT-related) implementation.” * *Developing Software with UML: Object-Oriented Analysis and Design in Practice, Bernd Oestereich, p. 72.

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

Vehicle Rental Use Case diagram

Today Identifying Business Use Cases Documenting Business Use Cases

Documenting Business Use Cases To document a business use case, include the following: Name of the use case Short description Actor(s) – role played to interact with use case Trigger – what started the use case Result(s) e.g. Actor’s goal satisfied

Documenting Business Use Cases A template is to be used to document a Business Use Case. Format of the template: Business Use Case Name: The name this business use case has been given. Short Description: A brief description of what this business use case does. Actors: The names of the person or persons who use or are affected by this business use case. Trigger: What causes this business use case to start Results: What is the output of this business use case How does it satisfy the actor’s goal

Documenting Business Use Cases Example: Reserve Vehicle Business Use Case. * Business Use Case Name: Reserve Vehicle Short Description: A customer reserves a vehicle for a defined period. Actors: Customer, Call Centre Employee Trigger: A Customer would like to reserve a vehicle. Results: Vehicle Reservation, reservation confirmation. *Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernd Oestereich, p. 73.

Documenting Business Use Cases Example: Complete Vehicle Rental Contract Business Use Case. * Business Use Case Name: Complete Vehicle Rental Contract Short Description: A reserved vehicle is handed over to a customer for his/her use. Actors: Customer, Rental agent, Vehicle Transfer Staff Trigger: A Customer would like to pick up a reserved vehicle. Results: Rental contract was completed, vehicle keys were handed over. *Developing Software with UML, Object-oriented Analysis and Design in Practice, Bernd Oestereich, p. 73.

Prep for WP2 create a .doc file for each business use case relate it to the Business Use Case in your Rational Rose model do the Use Case Descriptions for your Business Use Cases