Create Process activity diagram

1
Process Specification UML Activity Diagram
Create Process activity diagram
Identify StkHlds/ sources/ roles
FORK
Model Enterprise FR with UML
Model System FR with UML

• Use Case, Sequence, Class, Activity Diagrams Etc.

Specify Constraints
Specify Constraints
JOIN
Model NFR with Depend. Graph
Finalize Models/ Specs
Specify Constraints
Define Issues Including FR

• Obtain Agreement
• Need to be here by OCT 20

FORK

• Prototype should be functional, 80/20 rule,
  demonstrate requirements

Doc Issues with Defects
Further Develop Prototype
Doc Issues with Transl. to UML
Doc NFR Issues
Compare Demo function v. Reqs.
needs improvement
meets requirements
JOIN

• Post files on 3 separate URLS, one per team member

Post Solutions Online
Turn in Hard Copy OCT 27
2
Enterprise Requirements UML Activity Diagram
Initiator
Participant
Meeting is Needed
Determine Subject Participant
Request DateRange
Respond PrefExclSet
Chang DateRange
Check PrefExclSet
Conflict?
Ask to Change Set
Receive change request
yes
yes
no
Determine Notify Date/Time
Consult for Loc
Respond Loc
Determine Notify Loc
Require to Prepare Resource
Respond Resource Prepared
Remind
Hold Meeting
Attend Meeting
Monitor Meeting
3
Enterprise Requirements UML State Diagram (for
Meeting)
Incepted
Send request
Respond by participant
Send DateRange
Pending
Planning
conflict
Ask to change PrefExclSet
No conflict
Conflict solved
Confirmed
Canceled
holding
4
Enterprise Requirements UML Class Diagram

5
Enterprise Requirements UML Sequence Diagram
6
Enterprise Requirements Dependency Graph For
Meeting Date and Time
DateRange
ExclSet i
PrefSet i

• PrefSet i is the set of dates on which
  Participant i would prefer the meeting to take
  place.
• ExclSet i is the set of dates on which
  Participant i cannot attend the meeting.
• DateRange is the set of dates prescribed by the
  meeting initiator.
• For all Participants,

7
Enterprise Requirements Dependency Graph For
Meeting Date and Time

• Solution Exists
• Solution does not Exist
• Weak Conflict
• Strong Conflict

8
Enterprise Requirements Dependency Graph For
Meeting Date and Time

• Several ways to resolve conflicts
• Participants remove dates from ExclSets.
• Participants add dates to PrefSets.
• Participants withdraw from meeting.
• Initiator extends DateRange.

Strong Conflict
Remove Dates from ExclSet
Solved by
Withdraw from Meeting
Extend DateRange
Weak Conflict
Solved by
Add Dates to PrefSet
No Conflict
9
System Functional Requirements UML Use Case
Diagram
Meeting Scheduler System
Meeting Initiator
Participant
10
System Functional Requirements UML State Diagram
Meeting Scheduler System
Initial state
Initiate changes to Exclusion/ Preference Sets/
Date Range
no solution found
acceptable solution found
request denied
request approved
11
System Functional Requirements Acti-gram
User Profile
Physical Constraints
Participant Schedule
Resource/Loc Info
Subject
Date/Time
Location
username
SDMS
Resource
password
Participant List Important, Active, General
Pref/Excl Set
A0
Initiator
Participants
Computer
Input Username, password Output Meeting
Subject, Meeting Date and Time, Meeting Location,
Meeting Resources, Participant List (including
important participants, active participants, and
general participants), and Preference and
Exclusion Sets of those potential
participants. Control Physical Constraints,
User Profile, Potential Participants Schedule,
Resource and Location Availability
Data. Mechanism Initiator, Participants, and
Computer.
12
System Functional Requirements UML Sequence
Diagram
Meeting Initiator
MS System
MS Database
Participant
Request New Meeting()
Set Date Range()
Send Date Range/ Meeting Request()
Respond with Exclusion/ Preference Sets()
Figure out solution()
Determine Date/Time()
Send Final Date/Time()
Approve Meeting()
Meeting approved()
Update Meeting Record()
Consult for Location()
Send consultation()
Respond with Location()
Check Loc Availability()
Return Loc Availability()
Inform Approved Available Loc()
Determine Location()
Send Location()
Update Meeting Record()
Request Resource Preparation()
Sent ResourcePrep Request()
Check Resource Availability()
Return Resource Availability()
Resource Prepared()
Notify Resource Prepared()
Update Meeting Record()
Remind()
Remind()
Monitor Meetings()
13
System Functional Requirements UML Activity
Diagram
system
initiator
participant
Username Password
logon
Username Password
Verify logon
UserProfileDB
Participant List
Pref/Excl Set
valid
Check Pref/Excl Set
logon invalid
Date Range Participant List General, Important,
Active
User Profile DB
Personal Schedule
Date Range Participant List

Broadcast Request
Send Request
Date Range
Respond with Excl/Pref Sets
Solving Algorithm Physical Constraint
User Profile DB
Calculate Earliest Solution
Date Range Participant List General, Important,
Active
Pref/Excl Set
no solution
solution exist
Participant List User Profile DB Meeting Record DB
Date/Time
User Profile DB
Define and Broadcast
Date/Time Important/Active Participant List

Consult Loc/Rescourse
Broadcast Consult
Date/Time
Send Preferred Loc /Needed Resource
Location DB Resource DB
Check Loc/ Resource Availability
Location List Resource List
14
System Functional Requirements UML Activity
Diagram
system
initiator
participant
Best Available Location Available Resource
Participant List User Profile DB Meeting Record DB
Update and Broadcast
Complete Meeting Info Participant
List Date/Time Location Resource
Participant List User Profile DB Meeting Record
DB
Remind
Date/Time Location Resource
Meeting
Monitor when meeting was held
NOTE
Meeting Minutes
Control
Data (Input/Output)
Activity
15
System Functional Requirements UML Activity
Diagram Activity Class Definition

• Logon
• Input Username, Password.
• Output Username, Password.
• Control null.
• Mechanism Initiator.
• Verify Logon
• Input Username, Password.
• Output A boolean variant notifying whether user
  logged on successfully or not.
• Control User Profile DB.
• Mechanism Computer.
• Check Pref/Excl Set
• Input Potential Participant List.
• Output Date Range.
• Control Participants Preference and Exclusion
  Set.
• Mechanism Initiator.
• Send Request

16
System Functional Requirements UML Activity
Diagram Activity Class Definition

• Respond With Pref/Excl Set
• Input Date Range.
• Output Pref/Excl Set.
• Control Personal Schedule.
• Mechanism Participant.
• Calculate Earliest Solution
• Input Pref/Excl Set.
• Output Date/Time.
• Control Solving Algorithm and Physical
  Constraint.
• Mechanism Computer.
• Define and Broadcast
• Input Date/Time.
• Output Date/Time.
• Control User Profile DB, Participant List,
  Meeting Record DB.
• Mechanism Computer.
• Consult Loc/Resource

17
System Functional Requirements UML Activity
Diagram Activity Class Definition

• Check Location/Resource Availability
• Input Location List/Resource List.
• Output Best Available Location, Available
  Resource List.
• Control Location/Resource Info DB.
• Mechanism Computer.
• Update and Broadcast
• Input Best Available Location, Available
  Resource List.
• Output Complete Meeting Info, including
  Date/Time, Subject, Location, Resources,
  Participant List.
• Control Participant List, User Profile DB, and
  Meeting Record DB.
• Mechanism Computer.
• Remind
• Input Complete Meeting Info.
• Output Date/Time, Subject, Location, Resource.
• Control Participant List, User Profile DB, and
  Meeting Record DB.
• Mechanism Computer.
• Monitor when Meeting was held

18
System Non-Functional Requirements Dependency
Graph
SDMS System
provides
optimize
provides
provides
promotes
supports
Performance
Reliability
Security
Flexibility
Extensibility
Availability
allows
Dynamically Schedules Manages Constraints Convenie
ntly Schedules
Quickly Schedules
For 24h7d
Accurately Schedules
Meeting
Requires Longin
Quickly updates
Can Delegate
Teleconference
Accurately Keeps Record of
Accurately Gives Best Solution
Location
Provides variety of
Participant
Accurately Gives Earliest Solution
Date/Time
Equipment