Actors and Use Case Diagrams

Month Day, Year

AgendaTraining Plan OverviewReview Detailing Requirements with Requisite Pro

ConceptsSetting UpXDE IntegrationAssociating other requirementsCreating views

ActorsUse-Case DiagramsReview HomeworkNext 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

Review - ReqPro

BenefitsManage project requirements comprehensivelyPromotes communication and collaboration among team membersReduces project risk

FeaturesTool combing power of a database and Microsoft Word.

• Powerful sort and query capabilities

Requirements• Organize• Prioritize• Trace relationships• Manage requirement

changePerform real-time impact analysis

• Informed decisions• Scope management• Resource allocation

Review - ReqProRequirements Management Plan

Guidelines for establishing the requirements

• Requirement Types– Use-Case– Stakeholder Request – Feature– Supplementary– Glossary Item

• Attribute Types– Risk– Priority

Review - ReqPro• Document Types

– Vision– Use-Case

Specification– Supplementary

Requirement Specification

– Test Plan

• Views– Attribute Matrix– Traceability Matrix– Traceability Tree

Review - ReqProRequirement Types

Basic • Use-Case • Stakeholder Request • Feature• Supplementary

Specifications• Glossary Item

Other• Business Goals• Business Rules• Interface• Test

Attribute Types

Review - ReqProTraceability

Between Two Requirements

• Different• Can be same

To vs. FromEvolution

• Realization– Requirement– Model

Review - ReqProView Types

Attribute Matrix• Requirement vs.

Attribute– Illustrates the

relationships between requirements and their attributes

Review - ReqProView Types

Traceability Matrix• Requirement vs.

Requirement– Illustrates the

relationships between requirements of the same or different types

Review - ReqProView Types

Traceability Tree• Requirement vs.

Requirement– Displays all

internal and external requirements traced to or from a requirement

Review - ReqProFolders

General RequirementsModels

• Business Use-Case• Use-Case• Design

ReportsViews

Review - ReqProViews

Project Specific

Actors & EntitiesBusiness Actor

Represents a role played in relation to the business by someone or something in the business environment

Business WorkerRepresents an abstraction of a human that interacts within the systemActive

Business EntityRepresent an object that business workers access, inspect, manipulate, produce, …Provide the basis for sharing Passive

ActorRepresents someone in a role who interacts with the systemInteracts with but have no control over use-cases

EntityRepresents an object used to model information and associated behaviorMay be persistentMay be active or passive

ActorsActors represent system usersInteract with but have no control over use-casesCreate Actors at Model Level

Right click and select New UML, PackageName ActorsRight click package and select New UML, PackageName Contact ManagerRight click package and select New UML, ActorName Contact Manager

Use-Case DiagramsUse-case diagrams

Graphically depict system behaviorPresent a high level view of how the system is used as viewed from the actor’s perspective.A use-case diagram may depict all or some of the use cases of a system

Select the use-case diagram

Drag the actor and use-case on to the diagramCreate an association between the actor and the use-caseSet line style to Oblique

Use-Case DiagramsLabel to clarify Create alternative diagrams

Use-Case DiagramsComplete Use-Case Detail diagrams

Illustrate other actors or use-cases used within the context of the incorporating use-case

Use-Case DiagramsDefine Associations

• Includes– Used to partition out

parts of a workflow for which the base use case only depends on the result, not the method for reaching the result.

• Extends– Optionally, or

conditionally, add a flow to a business use case that is already complete in itself

• Generalizes– Specialization into

one or more child use cases that represent more specific forms of the parent

Use-Case DiagramsComplete other use-case diagrams of incorporated use-cases as needed

Select diagramDrag and drop model elements from model treeAdd labels

Use-Case DiagramsThe Main diagram

Provides an quick overview of the model

• Use grouping and labels to add context

Provides a navigation point for the model

• Right click actor and use-case and select

– Select in Browser

Use-Case Diagrams

Actors - DetailSelect View, Other Windows, Model Documentation

Actors - DetailRight click and select Properties Window

Select UML sectionSelect Stereotype

• Add business worker

Select Persistence

• Select Transient

Actors - Detail

Actors - DetailSelect UML section

• Select Multiplicity

Actors - DetailSelect a multiplicity

Actors - DetailAttributes

Not typical of actors, but could be use for establishing role profile attributesSelect Attribute tabClick Attribute Icon to add

Actors - Detail• Enter at least Name• Enter other attribute values

Repeat as necessaryClose

Actors - DetailComponents

Not typical of actors, but could be use for establishing role profile attributesDefines attributes derived from other classes

Actors - DetailOperations

Not typical of actors

Actors - DetailRelationships

A relationship is a connection between model elementsRelationship types are:

• Associations• Dependencies• Generalizations• Realizations• Transitions

Actors - DetailAssociations

An association is a structural relationship showing that objects of one classifier (actor, use case, class, interface, node, or component) are connected and can navigate to objects of another classifier The are numerous association types

Uses AssociationUses Association shows which processes the actor is involved Right cick and select Properties Window

Select UML section

• Enter Name

Uses AssociationSelect End 1 Section

• Enter Multiplicity

Select End 2 Section

• Enter Multiplicity

Uses AssociationQualifiers

Acts as a constraint• Can be at either end of relationship

AggregationPersistence

Uses Association

Uses Association

Next StepsHomework

Homework Model• Explode another top level use-case• Continue to concentrate on abstraction of detail• Use modeling elements

– Business Use-Case Model Level• Add Use-Case Diagrams

Classes AheadSequence and Statechart DiagramsCollaboration and Class DiagramsIntegration and Development with the .NET Framework