CS-CLOSAR Team Prometheus

1. CS-CLOSARTeam Prometheus Orchestrating better solutions through the Rational Unified Process

2. Use Cases: Actors User Any individual who intends to access the CS-CLOSAR system through the web-based UI. All other roles are inherited from the User role. Student An individual enrolled in a section of a course. Instructor An individual responsible for teaching a section of a course. Director An individual with the role of Chair or Associate Chair of the CS department. Blackboard Online course management tool with capability to authenticate users.

3. Use Cases: Model

4. Use Cases: Login • The system prompts for a user name and password. • The user provides the requested information • The system validates the information • The system determines the user’s role. • The system presents the main screen.

5. Use Cases: Display Courses • The user navigates to the course display. • The system retrieves the user’s assigned courses for the semester. • The system presents the courses.

6. Use Cases: Complete Survey • <<includes 02 Display Courses>> • The Student selects a course survey to complete. • System presents the survey to the Student. • Student completes the survey • System informs the Student that once stored, the survey cannot be modified. • Student chooses to store the survey. • System stores the survey results. • System presents the Student’s courses again.

7. Use Cases: Release Survey • <<includes 02 Display Courses>> • The Director tells the system to release all surveys. • The system requests confirmation to release the surveys • The Director confirms the release. • The system releases the specified surveys. • The system displays the courses and updated release statuses.

8. Use Cases: Email Student Reminders • <<include 02 Display Courses>> • Instructor selects a course which has an active survey. • The system retrieves and displays a list of students that have yet to complete the survey. • The instructor chooses to send an email reminder. • The system seeks confirmation to send the emails. • The instructor confirms. • The system sends the email reminder. • The system informs the instructor that the emails were sent.

9. Use Cases: View Survey Report • <<include 02 Display Courses>> • The user chooses to view the report of a course. • The system retrieves and displays the report for the chosen course.

10. Use Cases: Add Instructor Comment • <<includes Use Case 06 View Survey Report >> • The Instructor chooses to add comments to the report. • The system prompts the Instructor for the comment. • The Instructor provides comment. • The system adds the comment to the report. • The system redisplays the survey report.

11. Use Cases: View Course History • <<include 02 Display Courses>> • The Director chooses to view the history for a specific course. • The System retrieves the survey reports for each instance of the course. • The System displays a chart of the survey results over time.

12. Use Cases: Finalize Report • <<includes Use Case 06 View Survey Report >> • The Instructor chooses to finalize the report. • The system informs the instructor that comments cannot be further modified after finalization, and requests confirmation to continue. • The Instructor confirms. • The system finalizes the report. • The system informs the instructor that the report has been finalized.

13. Architecture

14. Architecture

15. Architecture

16. Project Risk I-001 Project Timeframe (0.72) 0.54 E-001 Transition Phase Length 0.54 I-002 Team Experience with web interfaces (0.42) 0.20 I-003 Team Experience with RUP 0.32 E-002 Team Experience with RUP Documents 0.54 I-004 Team has never worked together before (0.3) 0.10 I-005 Team is geographically separated (0.12) 0.10 I-006 Limited number of and access to user stakeholders 0.3 I-007 Stakeholder has been known to waffle on requirements 1.0 I-008 Stakeholder time will be split between three teams 0.2

17. Project Plan