Identifying & Creating Use Cases – Part 1 Month Day, Year.

Slides:



Advertisements
Similar presentations
Visio 2007 for UML Tutorial. Overview The tutorial demonstrates how to use Visio 2007 to create UML diagrams. We will focus on five most widely used UML.
Advertisements

Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Rational Rose 2000 Interaction Diagrams.
Detailing Requirements with Requisite Pro
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
©1998, 1999, 2000 Rational Software - All rights reserved Session VM08 Structuring Your Rational Rose Model Robert Bretall Rational Software.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Rational Rose Basics Visual Modeling Textbook – Chapter 3
A use case describes one “case” of how a user can use the system.
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
© Copyright Eliyahu Brutman Programming Techniques Course.
Rational Rose Overview Diagrams, Directory Structure, Working with Rose.
Introduction to Rational Rose 2000 Create Use Case Model Visual Modeling Text – Chapter 3 Original notes from Rational Software Corporation – 1998 Modified.
Rational Rose Tutorial
UML. Overview of UML Diagrams Structural : element of spec. irrespective of time Class Component Deployment Object Composite structure Package Behavioral.
Unified Modeling Language
University of Southern California Center for Systems and Software Engineering Rational Software Modeler Tutorial Pongtip Aroonvatanaporn.
Systems Analysis and Design in a Changing World, Fifth Edition
Class, Sequence and UML Model.  Has actors and use cases.
Business Modeling : basic concepts Extracted from Rational UML Profile for business modeling.mht.
Chapter 7 Structuring System Process Requirements
Lesson No:9 MS-Word Tools, Mail Merge and working with Tables CHBT-01 Basic Micro process & Computer Operation.
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
12 Systems Analysis and Design in a Changing World, Fifth Edition.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
IBM Software Group ® Overview of SA and RSA Integration John Jessup June 1, 2012 Slides from Kevin Cornell December 2008 Have been reused in this presentation.
Sequence & Statechart Diagrams Month Day, Year. Agenda Training Plan Overview Actors and Use Case Diagrams Sequence Diagrams Diagram Elements Evolution.
Introduction to RUP and Visual Modeling Month Day, Year.
Chapter 5 Models and UML Notation for The Object-Oriented Approach.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Rational Rose 2000 Class Diagrams.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
1 Structuring Systems Requirements Use Case Description and Diagrams.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Sequence Diagrams And Collaboration Diagrams HungNM.
Using COMET with Visio Visio UML Modeling. Creating a Drawing After opening Visio, you will see a list of templates available.
SWT - Diagrammatics Lecture 4/4 - Diagramming in OO Software Development - partB 4-May-2000.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Review: File Management Part 2: Formatting Text Part 3: Tools
Software Engineering Lecture 8 Object-Oriented Analysis.
CHAPTER 10 Creating a Word Document. Learning Objectives Enter text Undo and redo actions Create documents based on existing documents Select text Edit.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
Chapter 3: Introducing the UML
Using Rational Rose XDE Month Day, Year. Agenda Training Plan Overview XDE Review Next Steps.
Change Display of a Key Figure While in the Change Query (Local Definition) Hiding 1.Right click.
Change Display of a Key Figure While in the Change Query (Local Definition) Hiding 1.Right click.
Collaboration and Class Diagrams March 30, Agenda Training Plan Overview Review Sequence Diagrams Diagram Elements Use in the Models Statechart.
Chapter 6: Structuring Requirements: Use Case Description and Diagrams Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
1 Using Rational Rose ® to construct UML diagrams.
Using ClearCase Month Day, Year. Agenda Training Plan Overview ClearQuest Review Next Steps.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Interstage BPM v11.2 1Copyright © 2010 FUJITSU LIMITED CREATING A SIMPLE PROCESS.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
1 Advanced DataBases Unified Modelling Language An Introduction and Use Case Lecture 2 Susan Curtis.
Using Rational Administrator Month Day, Year. Agenda Training Plan Overview Using Rational Administrator Review Next Steps.
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Introduction to Rational Rose 2000 Create Use Case Model.
Systems Analysis and Design in a Changing World, Fourth Edition
Identifying & Creating Use Cases – Part 2
Analysis Classes Unit 5.
UML Diagrams By Daniel Damaris Novarianto S..
UML Diagrams Jung Woo.
面向对象分析与设计 Use of starUML By Wang Meihong.
UML Interaction diagrams
Analysis models and design models
Software Design Lecture : 15.
Rational Rose 2000 Instructor Notes Use Case Realization Structure
Identifying & Creating Use Cases - Part 3
Presentation transcript:

Identifying & Creating Use Cases – Part 1 Month Day, Year

Agenda Training Plan Overview Finish Overview Model Model Organization Identifying Creating Use-Cases Activity Diagram Description Activity Diagram Creation Procedures Create detailed activity diagram Create the next model level Next Steps

Training Plan Overview Introduction Using Rational Administrator Using ClearCase Using ClearQuest Using Rational Rose XDE Identifying & Creating Use-Cases – Part 1 Identifying & Creating Use-Cases – Part 2 Detailing Requirements with RequisitePro Actors and Use-Case Diagrams Sequence and Statechart Diagrams Collaboration and Class Diagrams Integration and Development with the.NET Framework

Create Blank Solution Select File > New > Blank Solution Enter Solution Name Click OK

Create Blank Solution

Add Project Right Click Add > New Item Select XDE Model Select Blank Project Enter Add Contact

Add Project

Add Documentation English Use Word to check spelling and grammar Control Workspace

Packages A general purpose mechanism for organizing elements into groups. Packages may be nested within other packages Control Unit

Packages Right Click Select Add UML Select Package

Packages

Use-Cases A description of system behavior, in terms of sequences of actions. A use case should yield an observable result of value to an actor. A use case contains all flows of events related to producing the "observable result of value", including alternate and exception flows. More formally, a use case defines a set of use-case instances or scenarios.actoruse-case instances scenarios The specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system.actors

Use-Cases Business Use-Case A sequence of actions performed by a business that yields an observable result of value to a particular business actor.

Use-Cases Composite Requirements Diagrams –Activity –Sequence –Collaboration –State –Use-Case –Class –Realization Text –Database –RequisitePro Other Media

Packages Use-Case Name English Clarity Right Click Select Rename Swipe and Select Actual Name Exclude >

Use-Cases Right Click Select Add UML Select Use-Case New Use-Case highlighted

Use-Cases Paste Name Reselect the use- case

Use-Cases Reselect the use- case Right Click Add Diagram Select Activity Diagram Paste Name Select ActivityGraph Right Click Rename Paste Name

Use-Cases Reselect the use-case Right Click Add Diagram Select Use-Case Diagram Paste Name Reselect the use-case Right Click Add Diagram Select Use-Case Diagram Paste Name Add Detail

Use-Cases Reselect the use- case Right Click Add Diagram Select State Diagram Paste Name Select StateMachine Right Click Rename Paste Name

Use-Cases Reselect the use-case Right Click Add Diagram Select Sequence Diagram Paste Name + Instance Select InteractionInstance Right Click Rename Paste Name

Use-Cases Select CollaborationInsta nce Right Click Rename Paste Name

Use-Cases Reselect the use- case Right Click Add Diagram Select Sequence Diagram Paste Name + Role Select InteractionInstan ce Right Click Rename Paste Name

Use-Cases Select CollaborationInsta nce Right Click Rename Paste Name Close open diagrams

Use-Cases

Double Click the activity diagram Appears Select the Start element

Use-Cases Click Start Element Select Properties window Select Name Enter Begin Business Activity Select the Activity element Click diagram

Use-Cases Select the Transition element Connect Start element to the activity element Re-Select the Transition element Connect activity element to the End element.

Use-Cases Select Diagram Select Layout Diagram Use Format Options Align Lines Oblique Rectilinear Route Orthogonal

Use-Cases Right Click Activity Select Select in Model Explorer Right Click New Diagram Select Activity Diagram New Activity Diagram appears

Use-Cases Right Click new diagram Select Rename Paste use-case name and add “Detail”

Activity Diagrams (AD) Definition: Defines the workflow associated with the use case How used Details the actions to be taken and decisions to be made for a use case Helps identify possible use cases at next level of detail Types Regular With Swimlanes With State Transitions

Activity Diagram Symbols Start State End State Activity Decision State Transition Regular Transition To Self Horizontal and Vertical Synchronization

Activity Diagram Symbols Swimlane State Note Note Anchor Text

Analysis Steps For each identified use case Create a context and detail activity diagram Identify potential sub-use cases Create a new package, use case, and related diagrams for the identified sub- use case Move relevant activities under the sub- use case

Identifying Use Cases - Navigation Organization Packages Hierarchy Project –Use-Case View –Logical View –Component View –Deployment View Levels of Abstraction

Identifying Use-Cases - Navigation Business Use-Case Model Project The Business –Business Function 1 –Add Use-Case Use-Case Model Project The System

Identifying UCs – Add Use-Case Add basic diagrams Provide work structure Provide review structure

Identifying UCs – Add Use-Case Double Click use- case detail activity diagram

Identify UC’s – Add Activities Add Activities Don’t attempt to connect Organize Groups Hierarchy

Identify UC’s – ID UC’s Identify Sub- activities Identify a Use-Case Sub-Use-Cases Change Font Color Select Format, Font, Bold Select Font Color icon –Select a color

Identify UC’s – ID UC’s Analyze Activities Repeat process

Identify UC’s – ID UC’s Rename to match identified activity Copy Name Create a package Paste Name

Identify UC’s – Add UC’s Add Use-Case Paste Name

Identify UC’s – Add UC’s Add Diagrams Paste Name Select original diagram Select ActivityGraph of new use-case

Identify UC’s – Add UC’s Drag and drop on original activity diagram Visibility changed accordingly Delete original activity

Identify UC’s – Clean Up Return to original activity diagram Repeat for each sub- activity identified Select identified use- cases Create packages Add diagrams Repeat Regressively Organize

Next Steps Homework Homework Model Explode one top level use-case Concentrate on abstraction of detail Use modeling elements –Business Use-Case Model Level Classes Ahead Identifying & Creating Use-Cases – Part 2 Detailing Requirements with RequisitePro Actors and Use-Case Diagrams Sequence and Statechart Diagrams Collaboration and Class Diagrams Integration and Development with the.NET Framework