1. Student Attendance System Requirement Analysis Presentation

2. Background Customer: Miami Dade College –6 Campuses and Multiple outreach centers –Largest College in the US (> 160,000 Students per year) Problem: New Federal Government regulations regarding the disbursement of Financial Aid funds

3. Objectives Provide a system that allows the college to meet federal financial aid requirements Allow for the electronic collection of student attendance data without direct instructor intervention Make the collected data available to both Staff and Students Leverage the College’s existing technology investments

4. Target Technology Environment Microsoft Windows 2000/2003 Platform.NET Framework Internet Information Server (IIS) (ASP.NET) Web interface for students / faculty College ID Card (Magstripe) Ethernet & TCP/IP for connectivity

5. The Customer’s Expectation

6. Scenarios Student Scenarios –Student goes to class and uses his/her ID to check-in –Student verifies his attendance history Faculty Scenarios –Faculty views class attendance for his/her class –Faculty inputs override information (manual check-in for student who forgot id card/or remove improper check-in) –Faculty exports attendance data for their class Fin-Aid Administrators –Fin-Aid Administrators exports a report of all classes for transfer to customer enterprise system System Administrators –System Administrators imports Students, Classrooms and Classes from Customer Enterprise system (system data loads) (a daily automatable process) –System Administrators administratively updates student check-in data (like faculty override information above) –System Administrators associate specific attendance devices with specific classrooms

7. Use Cases

8. Class Diagram 1/3

9. Class Diagram 2/3

10. Class Diagram 3/3

11. Use Case: Student Checks In –Use Case Name: Student Checks-in to Class Participating Actors: Student Entry Condition: –The student swipes his/her College ID card in the card reader Flow of Events: –The system verifies that the presented card is valid and that the associated student belongs in the current class –The system logs the check-in –The system acknowledges the user's check-in as being successful. Exit Condition: –o The reader responds acknowledging the student's check-in. Use Case Name: Unable to Check-In Participating Actors: Student Entry Condition: – Student Swipes an ID card to Reader to Check In to classs –Exception/Error condition that occurs when a students check- in request cannot be completed (i.e. they use an expired, invalid or otherwise bad ID card in the system, wrong room, etc) Flow of Events: – System Records the invalid information for auditing purposes –System informs user why the provided ID card is unacceptable and aborts check-ino The reader responds acknowledging the student's check-in. Exit Condition: – User is informed that the check-in process was not accepted.

12. Seq Diagram: Student Checks In

13. Giancarlo Use Cases –Login –View Attendance History –View Class Attendance History

14. Use Case: Login

15. Use Case: Login continued Use Case Name: Login ---------------------------------------------------------------------------------------------- Actors: Student, Faculty, Administrator, Fin-Aid Admin ---------------------------------------------------------------------------------------------- Entry Condition: Actor has navigated to System web site. ---------------------------------------------------------------------------------------------- Flow of Events: 1. System displays logon web page. 2. User enters login name and password. 3. System checks login to determine if student, faculty, or administrator. 4. System displays respective home page. ---------------------------------------------------------------------------------------------- Exit Conditions: Client terminal displays appropriate home page. ---------------------------------------------------------------------------------------------- Exceptions: User entered invalid login information, ---------------------------------------------------------------------------------------------- Special Requirements: N/A

16. Login Sequence

17. Use Case: View Attendance History

18. Use Case: View Attendance History continued Use Case Name: View Attendance History ---------------------------------------------------------------------------------------------- Actors: Student ---------------------------------------------------------------------------------------------- Entry Condition: Student logged on to web interface. ---------------------------------------------------------------------------------------------- Flow of Events: 1. Student selects to view attendance history. 2. System displays currently enrolled course list. 3. Student selects course to view attendance. 4. System server sends a request to the database to retrieve a students information. 5. Database retrieves the information. 6. System server sends the response to the client terminal. ---------------------------------------------------------------------------------------------- Exit Conditions: Client terminal displays the attendance history with continue or logout options. ---------------------------------------------------------------------------------------------- Exceptions: Student is not enrolled in any classes. ---------------------------------------------------------------------------------------------- Special Requirements: N/A

19. View Attendance History Sequence

20. Use Case: View class Attendance History

21. Use Case: View class Attendance History continued Use Case Name: View class Attendance History ---------------------------------------------------------------------------------------------- Actors: Faculty ---------------------------------------------------------------------------------------------- Entry Condition: Faculty logged on to web interface. ---------------------------------------------------------------------------------------------- Flow of Events: 1. Faculty selects to view class attendance history. 2. System displays classes currently being taught by faculty. 3. Faculty selects class to view attendance. 4. System server sends a request to the database to retrieve a class information. 5. Database retrieves the information. 6. System server sends the response to the faculty terminal. ---------------------------------------------------------------------------------------------- Exit Conditions: Faculty terminal displays the class attendance history with continue or logout options. ---------------------------------------------------------------------------------------------- Exceptions: Faculty not instructing any classes. ---------------------------------------------------------------------------------------------- Special Requirements: N/A

22. View class Attendance History Sequence

23. Frank Use Cases –Override Attendance Info –Get associated classes –Retrieve Class attendance data

24. Use Case: Override Attendance Info

25. Use Case: Override Attendance Info continued Use Case Name: Override Attendance Information -------------------------------------------------------------------------------------------------------------------- Participating Actors: Faculty Employee, System Administrator -------------------------------------------------------------------------------------------------------------------- Entry Condition: o User is currently viewing the Attendance information for a particular class -------------------------------------------------------------------------------------------------------------------- Flow of Events: o User selects a student and date to override attendance Information o The system presents the user with the student's current attendance information o The user updates the attendance information for the student o The system makes the change and records it in a audit log. ------------------------------------------------------------------------------------------------------------------- Exit Condition: o The system acknowledges whether the requested changes have been made or not -------------------------------------------------------------------------------------------------------------------

26. Override Attendance Sequence

27. Use Case: View Associated Classes Use Case Name: View Associated Classes ---------------------------------------------------------------------------- Actors: Student, Faculty ---------------------------------------------------------------------------- Entry Conditions: The system needs to determine which classes are associated to a given user ---------------------------------------------------------------------------- Flow of Events: The system determines the associated classes for the given user ---------------------------------------------------------------------------- Exit Conditions: The class data is returned to the initiating use case

28. View Associated Classes Sequence

29. Use Case: Retrieve Class Attendance Data Use Case Name: Retrieve Class Attendance Data ---------------------------------------------------------------------------------------------- Actors: Faculty, Sys Admin, Fin-Aid Admin ---------------------------------------------------------------------------------------------- Entry Conditions: o The system needs to retrieve Class attendance data for the user ---------------------------------------------------------------------------------------------- Flow of Events: o System verifies the current user has permission to access the requested class attendance data o The system retrieves the class data from the system ---------------------------------------------------------------------------------------------- Exit Conditions: o The class data is returned to the initiating use case

30. Retrieve Class attendance Data Sequence

31. Kasturi Use Cases –Export Class Attendance Data –Export All Attendance Data

32. Use Case: Export Class Attendance Data

33. Use Case Name: Export Class Attendance Data Participating Actors: Faculty Entry Condition: Faculty selects option to export attendance data Flow of Events: System uses the “Retrieve Class Attendance" use case to generate an export file for the current class and uploads it to the User Exit Condition: The user completes download of Attendance Data Use Case Name: Retrieve Class Attendance Data Participating Actors: Faculty, Sys Admin, Fin-Aid Admin Entry Condition: The system needs to retrieve Class attendance data for the user Flow of Events: System verifies the current user may access the requested class attendance data The system retrieves the class data from the system Exit Condition: The class data is returned to the initiating use case Use Case Name: No Security for Requested Class Participating Actors: Faculty Entry Condition: Faculty selects option to export attendance data for a particular class Flow of Events: The system attempts to verify the user has access to the class, but the user does not. Exit Condition: The system rejects the users request and displays message indicating no access.

34. Seq Diagram: Export Class Attendance Data

35. Use Case: Export All Attendance Data Use Case Name : Export All Attendance Data Participating Actors : Fin-Aid Admins Entry Condition: Fin-Aid Admin selects option to export all attendance data Flow of Events: System uses the “Retrieve Class Attendance" use case to generate an export file for classes and uploads it to the User Exit Condition: The user completes download of Attendance Data. Use Case Name: Retrieve Class Attendance Data Participating Actors: Faculty, Sys Admin, Fin-Aid Admin Entry Condition: The system needs to retrieve Class attendance data for the user Flow of Events: System verifies the current user may access the requested class attendance data The system retrieves the class data from the system Exit Condition: The class data is returned to the calling use case

36. Seq Diagram: Export All Attendance Data

37. Suzette Use Cases –Import System Data –Associate Attendance Devices

38. Use Case: Import System Data

39. Import System Data continued

41. Import System Data Sequence

42. Use Case: Associate Attendance Devices

43. Associate Attendance Devices - View

44. Associate Attendance Devices – View

45. Associate Attendance Devices – Add

46. Associate Attendance Devices - Add

47. Associate Attendance Devices – Add

48. Associate Attendance Devices – Delete

50. Student Attendance System Thank You!