Identifying & Creating Use Cases – Part 1

Month Day, Year

AgendaTraining Plan OverviewFinish Overview ModelModel OrganizationIdentifying Creating Use-Cases

Activity Diagram DescriptionActivity Diagram Creation Procedures• Create detailed activity diagram• Create the next model level

Next Steps

Training Plan OverviewIntroductionUsing Rational AdministratorUsing ClearCaseUsing ClearQuestUsing Rational Rose XDEIdentifying & Creating Use-Cases – Part 1Identifying & Creating Use-Cases – Part 2Detailing Requirements withRequisiteProActors and Use-Case DiagramsSequence and Statechart DiagramsCollaboration and Class DiagramsIntegration and Development with the .NET Framework

Create Blank SolutionSelect File > New > Blank SolutionEnter Solution NameClick OK

Create Blank Solution

Add ProjectRight Click Add > New ItemSelect XDE ModelSelect Blank ProjectEnter Add Contact

Add Project

Add ProjectAdd Documentation

EnglishUse Word to check spelling and grammar

Control Workspace

PackagesA general purpose mechanism for organizing elements into groups. Packages may be nested within other packagesControl Unit

PackagesRight Click

Select Add UMLSelect Package

Packages

Use-CasesA 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. The specification of a sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system.

Use-CasesBusiness Use-Case

A sequence of actions performed by a business that yields an observable result of value to a particular business actor.

Use-CasesComposite

Requirements• Diagrams

– Activity– Sequence– Collaboration– State– Use-Case– Class

– Realization• Text

– Database– RequisitePro

• Other Media

PackagesUse-Case Name

EnglishClarity

Right ClickSelect Rename

Swipe and SelectActual NameExclude <<>>

Use-CasesRight Click

Select Add UMLSelect Use-Case

New Use-Case highlighted

Use-CasesPaste NameReselect the use-case

Use-CasesReselect the use-case

Right Click Add Diagram Select Activity DiagramPaste NameSelect ActivityGraphRight Click RenamePaste Name

Use-CasesReselect the use-case

Right Click Add DiagramSelect Use-Case DiagramPaste Name

Reselect the use-case Right Click Add DiagramSelect Use-Case DiagramPaste NameAdd Detail

Use-CasesReselect the use-case

Right Click Add DiagramSelect State DiagramPaste NameSelect StateMachineRight Click RenamePaste Name

Use-CasesReselect the use-case

Right Click Add DiagramSelect Sequence DiagramPaste Name + InstanceSelect InteractionInstanceRight Click RenamePaste Name

Use-CasesSelect CollaborationInstanceRight Click RenamePaste Name

Use-CasesReselect the use-case

Right Click Add DiagramSelect Sequence DiagramPaste Name + RoleSelect InteractionInstanceRight Click RenamePaste Name

Use-CasesSelect CollaborationInstanceRight Click RenamePaste Name

Close open diagrams

Use-Cases

Use-CasesDouble Click the activity diagram

Appears

Select the Start element

Use-CasesClick Start ElementSelect Properties window

Select Name Enter Begin Business Activity

Select the Activity element

Click diagram

Use-CasesSelect the Transition element

Connect Start element to the activity element

Re-Select the Transition element

Connect activity element to the End element.

Use-CasesSelect Diagram

Select Layout Diagram

Use Format Options

AlignLines

• Oblique• Rectilinear• Route Orthogonal

Use-CasesRight 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 RenamePaste use-case name and add “Detail”

Activity Diagrams (AD)Definition: Defines the workflow associated with the use caseHow used

Details the actions to be taken and decisions to be made for a use caseHelps identify possible use cases at next level of detail

TypesRegularWith SwimlanesWith State Transitions

Activity Diagram SymbolsStart StateEnd StateActivityDecisionState Transition

RegularTransition To Self

Horizontal and Vertical Synchronization

Activity Diagram Symbols SwimlaneStateNoteNote AnchorText

Analysis StepsFor each identified use case

Create a context and detail activity diagramIdentify potential sub-use cases

Create a new package, use case, and related diagrams for the identified sub-use caseMove relevant activities under the sub-use case

Identifying Use Cases - NavigationOrganization

PackagesHierarchy

• Project– Use-Case View– Logical View– Component View– Deployment View

Levels of Abstraction

Identifying Use-Cases - NavigationBusiness Use-Case Model

Project• The Business

– Business Function 1

– Business Function 1

– Add Use-Case

Use-Case ModelProject

• The System

Identifying UCs – Add Use-CaseAdd basic diagrams

Provide work structureProvide review structure

Identifying UCs – Add Use-Case

Double Click use-case detail activity diagram

Identify UC’s – Add ActivitiesAdd Activities

Don’t attempt to connect

OrganizeGroupsHierarchy

Identify UC’s – ID UC’sIdentify Sub-activitiesIdentify a Use-Case

Sub-Use-CasesChange Font Color

• Select Format, Font, Bold

• Select Font Color icon

– Select a color

Identify UC’s – ID UC’sAnalyze Activities

Repeat process

Identify UC’s – ID UC’sRename to match identified activity

Copy Name

Create a packagePaste Name

Identify UC’s – Add UC’sAdd Use-Case

Paste Name

Identify UC’s – Add UC’sAdd Diagrams

Paste Name

Select original diagramSelect ActivityGraph of new use-case

Identify UC’s – Add UC’sDrag and drop on original activity diagram

Visibility changed accordingly

Delete original activity

Identify UC’s – Clean UpReturn to original activity diagram

Repeat for each sub-activity identified

• Select identified use-cases

• Create packages• Add diagrams

Repeat RegressivelyOrganize

Next StepsHomework

Homework Model• Explode one top level use-case• Concentrate on abstraction of detail• Use modeling elements

– Business Use-Case Model Level

Classes AheadIdentifying & Creating Use-Cases – Part 2Detailing Requirements withRequisiteProActors and Use-Case DiagramsSequence and Statechart DiagramsCollaboration and Class DiagramsIntegration and Development with the .NET Framework