User Scenario Design

1
User Scenario Design

• Michael C. Daconta
• Chief Technology Officer, AIM

2
User Scenario Basics

• Able to draw in Powerpoint or on paper.
• Modified Use Case Notation
• Capture (see figure)
• Actors, Activities, Data flows and Data stores.
• Two types of views
• High-Level (Overview)
• Actors, Activities, Flows
• Detailed (Subsystem View)
• Same as High Level plus
• Steps in Activities
• Data Entities and Attributes

3
User Scenario Notation
Actors
Activities
Data
ltdata typegt
Sub- System
Activity
flow
End-user
Activity Title
External System
ltdata typegt

• Step1
• Step 2
• Step 3

store
(for Detailed View)

• Entity 1
• Attribute 1
• Attribute 2
• Entity 2

Explanatory Note
(for Detailed View)
4
Example Overview Diagram
FIS
Portal
ltlogin infogt
Create Account
ltd1gt
Scientist John Smith
ltresultsgt
Drill-Down
Visualize
ltd2gt
ltd2agt
Data Exchange Hub
Catalog
ltd3gt
ltd5gt
ltd4gt
ltd6gt
ltd4agt
External System
ltd8gt
ltd9gt
ltd7gt
Data Source Metadata
Common Data Model
Adapter
ltd10gt
ltd11gt
5
Example Detailed View
Catalog
ltcredentials 1gt
Find Data Sources

• Data Source
• Name
• Location
• Periods of Data
• Domain of Data
• Confidentiality Level

ltcriteria 1gt

• Receive User Credentials
• Receive User Search Criteria
• Query Data Store
• Return authorized results

ltresult 1gt
Get User Authorizations
Credentials 1 contains Username,
password, Authorization, etc.