1. Personnel Availability & Scheduling System (PASS)
Client XX
This is not a real project, but a student project carried out for a system requirements course at American University, supervised by Deloitte.
Team
Member 1 Member 2 Member 3 Member 4

2. Today’s agenda System Concept Business Process Model Use Case Diagram
Data Model
Conclusions

3. System Concept
Provide an effective method for scheduling security personnel into assigned shifts, while taking into account their individual schedule preferences
Personnel are geographically dispersed across the U.S.
“Round-the-clock” shifts – 24/7/365
Saves administrative time while better meeting mission requirements

4. Business Process Model

5. Business Process Model

6. Business Process Model

7. Business Process Model

8. Business Process Model

9. Use Case Diagram Squad Leader Squad Member Inputting Preferences
Review Members’
Availability
Review Squad
Schedules
Review Field
Office Schedules
Field Office Administrator
Corporate Office Administrator
Inform Field Office
of Requirements
Schedule
Annual RDOs
Publish Schedules
Data Entry & Maintenance Clerk
Modify Employee
Data
Configure System
Tables
System Administrator

10. Representative Use Case Review Field Office’s Preliminary Schedule
Actor – Corporate Office Administrator - Preconditions - Process - If requirements are not met, Use case Modify Field Office’s Preliminary Schedule is initiated - If requirements are met, schedule is approved - Approved schedule file is created - The period for the Field Office closed

11. Key tables Core Tables User Member Schedule Squads
Field Office Locations
Field Office Requirements
Periods
Support Tables
Squad Approval
Field Office Approval
System Roles
Period Days
Availability Status
Approval Status

12. CRUD Matrix R, U C, U R C,R,U C Inputting Preferences (UC-10)
Field Office Loc
Squad
Mbrs
Field OfficeRqmt
Schd
Avail
Stat
ApprStat
Period
Day
User
Syst.
Role
Field Office Appr
Squad Appr
Periods
Inputting Preferences (UC-10)
R, U
C, U R
Review Squad Member’s Availability (UC-20)
Review Squads’ Preliminary Schedule (UC-30)
Review Field Offices’ Preliminary Schedule (UC-40)
Inform Field Offices of Threshold Requirements (UC-60)
C,R,U C

13. Entity Relationship Diagram

14. Conclusion Where we are now: The next steps: Requirements
BPM
Use Cases
CRUD
ERD
The next steps:
- Development
Testing
Training
Documentation
Pilot
Deployment

15. Questions?