1. Task Management System Client xx Team Member 1 Member 2 Member 3 This is not a real project, but a student project carried out for a system requirements course at American University.

2. Agenda System Concept –BPM –Context Diagram Use Cases –Use Case Diagram –Elaborated Use Case Data Model –Key Tables –CRUD Matrix Conclusions

3. System Concept “An electronic checklist system to facilitate deployment” Current project: Facilitate ERP deployment for the U.S. Army Replaces an Excel “readiness” checklist “Reusable” electronic system to handle task management –Allow stakeholders to understand their roles during deployment –Provide an automated system of reminders –Track deployment progress

4. System Features Set-up Management Execution Notification Reporting “Dashboard”

5. System Actors Administrator Set-up Project Manager Review and approval Task Manager Assign tasks Assignee Complete tasks Viewer Read-only Template Manager Manage Task Templates

6. Business Process Model

7. BPM: Set-Up Phase

8. BPM: Management Phase

9. BPM: Close-Out Phase

10. Context Diagram

17. Use Cases UC-001: Create Users and Set Permissions UC-002: Import External Tasks UC-003: Search Templates UC-004: Create Template from Existing Project Tasks UC-005: Modify Template UC-006: Apply Template to Project UC-007: Create New Task UC-008: Assign (Reassign) Task UC-009: Complete Task UC-010: Modify Task UC-011: Delete Task UC-012: Send Readiness Reports UC-013: Close-Out Project UC-014: Reassign Manager UC-015: Send Reminders

18. Use Case Diagram

19. Representative Use Case Use Case IDUC-008 Use CaseAssign (Reassign) Task ActorsP: Task Manager, S: Assignee Pre-conditionsA task has been created in the system Flow of Events 1.The Task Manager selects an existing task or group of tasks. 2.The Task Manager enters a date for the task to be completed. 2.1 The date must be greater than today’s date. If the Task Manager enters a date prior to today’s date, the system will display an error message and prompt the Task Manager to enter a different date. 3.The Task Manager selects an Assignee in the system. 3.1 To assign a task, the Assignee must exist in the system. If the Assignee does not exist in the system, the Task Manager must contact the Administrator. 4.The Task Manager assigns the task to the Assignee. 4.1 If the task already has been assigned to another Assignee, the system displays a message notifying the Task Manager that the task already has an Assignee and asks the Task Manager to confirm the action. 4.1.1 If the Task Manager does not confirm, the system prompts the Task Manager to select another task (go to flow 1.1). 4.1.2 If the Task Manager confirms, the system assigns the task to the Assignee. 5.The system notifies the Assignee that a task has been assigned. 5.1 If the notification subsystem does not notify the Assignee, the task still displays on the dashboard. 6.The system designates the task as “outstanding.” 6.1 If the tasks are being monitored manually, the Task Manager is responsible for notifying all Assignees of their new and current tasks. Post- conditions Assignee has notification of the new task in the system and the task is denoted “outstanding” in the system.

20. Data Model

21. Key tables Core Tables Tasks Users Projects Support Tables Roles Status Reminders Notifications ActionHistory Clients Permissions

22. CRUD Matrix

25. Conclusion Complete: -Requirements -BPM -Context Diagram -Use Cases -CRUD -Data Model Next Steps: -Development -Testing -Training -Documentation -Pilot -Deployment

26. Questions?