Use Cases Preparation for Thursday 10/2/14. Process or Workflow Model Concepts Representing task, process, procedure, workflow, actions, decisions Functional.

Slides:



Advertisements
Similar presentations
Introduction to Object Orientation System Analysis and Design
Advertisements

Withdrawal Transaction Use Case Primary Actor: Customer Pre-conditions: The customer must have a valid ATM card and PIN. Post-conditions: The customer.
7M701 1 Information Systems Modelling and Design with.
Use Case Modeling SJTU. Unified Modeling Language (UML) l Standardized notation for object-oriented development l Needs to be used with an analysis and.
USE CASE – ATM EXAMPLE Actors: ATM Customer ATM Operator Use Cases: The customer can withdraw funds from a checking or savings account query the balance.
CPSC 333: Foundations of Software EngineeringJ. Denzinger Small Test: Bank account manager System has to run on an automated teller machine. User must.
IBM Software Group ® Use Cases & System of Systems Ivar Jacobson IBM Rational Jaczone AB
CS3773 Software Engineering Lecture 03 UML Use Cases.
1 Software Testing and Quality Assurance Lecture 12 - The Testing Perspective (Chapter 2, A Practical Guide to Testing Object-Oriented Software)
January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Requirements Analysis 8. 1 Storyboarding b508.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Human.
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,
COMP1007 Intro to Systems Requirements © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Intro to System Requirements Lecture 2 Use-Cases.
COMP1007 Intro to Systems Requirements © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Intro to Systems Requirements Lecture 4 Identifying.
Requirements Analysis 4. 1 Use Case I b504.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Use-Cases.
Itntroduction to UML, page 1 Introduction to UML.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 6 - Use cases and activity diagrams Dr.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Chapter 2: Approaches to System Development
From Problem Statement to Design
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 4 - System modelling Dr Richard Clayton.
Unified Modeling Language, Version 2.0
© FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 Unified Modeling Language (UML) Case Study.
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
1 Forward and Reverse Engineering. 2 The UML is not just an OO modeling language. It also permits forward engineering (FE) and reverse engineering (RE).
CS-2852 Data Structures LECTURE 3B Andrew J. Wozniewicz Image copyright © 2010 andyjphoto.com.
UML Diagrams A tool for presentation of Architecture.
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
Use Cases -Use Case Diagram Chapter 3 1. Where are we? 2 Analysis Chapters Ch 2Investigating System Requirements Ch 3Use Cases Ch 4Domain Modeling Ch.
Michael Schloh von Bennewitz 1. Oktober 2002 The Unified Modeling Language Overview of theory and practice of the OMG Unified Modeling.
1 Graph Coverage (6). Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Section
Object Oriented Analysis and Design 1 CREATED BY RUONAN RAO Object-Oriented Analysis and Design.
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
SYSTEMSDESIGNANALYSIS 1 OO: Chapter 4 Process Modeling Jerry Post Copyright © 1997.
Lecture 4/2/16. Learning Objective Establishing requirements Define requirements Requirements discovery vs requirements gathering Classifying Requirements.
Session 1 What Is the UML? Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 5, 2011 Presented by Kang-Pyo Lee.
Copyright (C), No Magic, Inc Welcome to No Magic!
SWE 214 (071) Introduction to UML Slide 1 Introduction to UML.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
1 An Overview of UML. 2 The Unified Modeling Language UML is a graphical language used by software engineers to model software systems during development.
1 Case Study and Use Cases for Case Study Lecture # 28.
Introduction to OOAD and UML
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
IS 350 Course Introduction. Slide 2 Objectives Identify the steps performed in the software development life cycle Describe selected tools used to design.
Class 11 Outline Business – Qs on artifact model assignment? – Qs on draft project models? Activities – Card Sorting – Use Cases.
Use Cases UML. Use Cases What are Use Cases?  A statement of the functionality users expect and need, organized by functional units  Different from.
Introduction to UML.
Contents What is “RUP?” What are Requirement Types
Use Cases -Use Case Diagram
Paul Ammann & Jeff Offutt
CMPE 280 Web UI Design and Development August 29 Class Meeting
Use Case Modeling - II Lecture # 27.
Evolution of UML.
Object-Oriented Static Modeling of the Banking System - I
Methods, Models, Madness
James Miller, Julia John
Introduction to Object Oriented Analysis, Design and Unified Modeling Language (UML) Shanika Karunasekera.
A tool for presentation of Architecture
A tool for presentation of Architecture
Use Case Modeling - techniques for detailing use cases
Concepts, Specifications, and Diagrams
Paul Ammann & Jeff Offutt
Use Cases & Use Case Diagrams
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Software engineering -1
Object Oriented Analysis and Design
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
CS 425 Software Engineering
CS 425/625 Software Engineering
Presentation transcript:

Use Cases Preparation for Thursday 10/2/14

Process or Workflow Model Concepts Representing task, process, procedure, workflow, actions, decisions Functional decomposition – Given a task, what are its subtasks? – Given a subtask, what are its subtasks? – and so on. Endpoint will be individual steps that can be implemented in the system Task: Apply to Graduate School Subtasks: identify schools, take GREs, write essay, request recommendation letters, … Subtask: take GREs sub-subtasks: find a testing site, register for a test date, study, sleep well, show up… Task subtask sub- subtask

Unified Modeling Language (UML) UML is a set of process and models for system analysis and design. “Unified” because they are the result of merging 3 earlier (and similar) approaches for object-oriented modeling. – Booch, G, Rumbaugh, J. Jacobson, I. (2005) The Unified Modeling Language User Guide, 2 nd ed. Addison-Wesley “Degrees” of UML use (Miles & Hamilton). – sketching alternatives – developing blueprints – designs for program architecture and modules (e.g., for Java) We’ll focus on the sketch and blueprint level. Current version is UML 2.0. Like many models, there are variations in notation, syntax, and good style. The modeling software you use may restrict your options, and some organizations adopt a specific style. Tools and Resources – OMG Unified Modeling Language – Visio templates (shapes software) – IBM Rational Rose 01.ibm.com/software/awdtools/developer/rose/ 01.ibm.com/software/awdtools/developer/rose/

Process/Workflow Model Concepts When designing work models, first represent the happy path, then consider the unhappy path. – The happy path is the sequence of steps (user and system) that results in the desired outcome – The unhappy path is any sequence of steps that doesn’t work; it include (or results in) breakdowns. – You can’t possibly think of all the possible unhappy paths – focus on ones you’ve observed or that are most frequent. These are the ones the system should handle and/or seek to prevent. Using the ATM: getting cash Happy path: Insert ATM card enter PIN at prompt select withdraw cash enter amount remove card receive cash Using the ATM: getting cash Unhappy path: Insert ATM card enter PIN at prompt error: incorrect PIN try again, same error ATM keeps ATM card Using the ATM: getting cash ??? path: Insert ATM card enter PIN at prompt error: incorrect PIN try again select withdraw cash enter amount remove card receive cash