Name: Jithendra JayaramNet-Id: jxj142430Use Case UC1: Give AttendanceScope: Attendance Tracking SystemLevel: user goalPrimary Actor: StudentStakeholders and Interests: -Student : Provide attendance for his presence at ACM meeting.-Volunteer : Make sure that all Students attending are listed.Pre-condition: The Student must be enrolled for ACM meeting.Success Guarantee: The Student should be able to give attendance for his presence in ACM meeting.Main Success Scenario: 1. Student arrives to ACM meeting.2. Volunteer asks the for Comet Card.3. Student provides the card to the Volunteer.4. Volunteer swipes the comet card as the proof of attendance.5. System displays a success message.Extensions: *a. At anytime the System may stop operation: 1. Volunteer restart the System.- System starts working as desired.2a. Student has not got the Comet Card.1. Volunteer asks the student to enter the UTD ID on the System.2. Student enters the UTD ID.4a. Not able to scan Comet Card.1. System prompts to enter UTD ID.2. Volunteer asks the student to enter the UTD ID on the System.3. Student enters the UTD ID.5a. The system records the student information.1. System obtains the UTD ID of the Student.2. The System stores the information in the table containing the list of Students attended.Special Requirements:-Comet card should be validated within 10 seconds.Technology and Data Variation List:2a. Student enters UTD ID using keypad.4. The card is scanned with the help of magnetic strip.Frequency of Occurrence: Twice in a week.Open Issues:- What if the System is not able to accept the entered UTD ID.- How to make sure that data is entered and is correct.Use Case UC2: Tracking AttendanceScope: Attendance Tracking SystemLevel: user goalPrimary Actor: OfficerStakeholders and Interests: -Officer : Track who all have attended the meeting.Pre-condition: Officer should be authorized to access the track record.Success Guarantee: The officer should be able to obtain the list of students who have attended the meeting and who have not attended along with related report.Main Success Scenario: 1. Officer will log into the system.2. Officer looks at the list of students who have attended the meeting.3. Officer makes the system list the Students who haven't attended the meeting.4. Officer makes the system generate a report on the data obtained.5. System prints out the list and the report.Extensions:*a. At anytime the card swipe system may stop operation: 1. Officer restarts the System.- System starts working as desired.2a. Attendance information not present.- System is not able to provide the list of students who have attended.4a. Report generation 1. Officer selects the required field generation of the report. 2. System takes the input provided by the Officer and generates the report.4b. System is not able to generate the report. 1. Officer uses alternate method to generate report.5a. There is no paper in the system to print. 1. Officer loads the paper into the system 2. The officer gives command for the System to print.- System prints the report.5b. System is not able to print the report. 1. Officer uses alternate method to print the report.Special Requirements:-The System should be able to produce any desired report.Technology and Data Variation List:5. System prints using an inbuilt printer.Frequency of Occurrence: Twice in a week.Open Issues:- What if the System is not able to retrieve the stored data .- What alternative is present if the System cannot print
View Full Document