Look at the problem statment and fill out the matrix chart.

MC University Management Board approved a new Student Registration System to enable the on line course enrollments by students for the Computer Science Department. The implementation of the new system is proposed to be in place by 2022 Spring. The new system is called SRS.

What is expected from the SRS?

The SRS software should provide access to the students who are currently active to manage their student records online. The SRS shall provide the functionality to view and print the transcripts at the end of each semester. Through the SRS Software the undergraduate and graduate student advisors should be able to monitor the student course credits and flag any potential problems which can arise and hinder the graduation of the students. The SRS will provide the functionality to view the entire prior courses student enrolled in. The SRS shall provide the faculty to update the grades for their class. SRS will provide online tutoring for selected courses.

The online tutoring is administered by the TAs of the respective class with a fixed schedule. During the tutoring hours the SRS shall capture the student attendance and will record as part of the student activity.

SRS shall provide the functionality to request the class room keys needed by the teachers by providing an online request form. The teachers will collect the physical keys from designated department after SRS generates an authorization letter. The SRS shall verify the teacher request by cross checking with the department class assignment schedule by accessing Faculty Class Database.

The SRS will run on any standard browser with standard user authentication. SRS will not accept any payments directly but directed to a third party vendor to accept the payments by credit cards only. The data will be updated on SRS from the payment system by end of every day 8:00 pm.

Identify - Actors	Identify - Scenarios	Identity - Use Cases	Refine Use Cases	Identify - Relationships	Identify - Non-Functional Requirements
Actors are Role Abstraction - not necessary to map to a persons One Actor can take multiple roles Subsystems can be Actors	Scenario is a description of the behavior of an ACTOR Single Actor View point Cant replace an Use Case Types (As-Is, Futuristic, Testing and Evaluation, Training)	Aggregation of the Scenarios Use Case is initiated by an ACTOR Use Case can interact with other Actors Writing Use Case is an ART	Completeness and Correctness Any missing details to be noted and added to the User Case Go over with the client if possible. Let an outsider read the Use Case	Find the Relationship between ACTORs and Use Cases This will reduce the complexity and makes it easy for developers Identify the Common and Exceptional scenarios Reduce redundancy	Broad Categories Product, Organizational External
Which user groups are supported by the system to perform their work? Which user groups execute the systems main functions? Which user groups perform secondary functions, such as maintenance and administration? With what external hardware or software system will the system interact?	What are the tasks that the actor wants the system to perform? What information does the actor access? Who creates that data? Can it be modified or removed? By whom? Which external changes does the actor need to inform the system about? How often? When? Which events does the system need to inform the actor about? With what latency?	Number each Use Case Uniquely Name the User Case to represent the ACTION (Verb) Name the ACTORS with the Role (Noun) Exit and Entry conditions should be clear Dont write about the user interface Exceptions should be outlined clearly low of activity should be clear and numbers for easy identification	More eyes are better Run through with fine tooth comb on scenarios & User Cases	Identify common scenarios or user cases EXTEND for rarely used scenario or use case INCLUDE when the scenario is used in more than one use case Dont over use.	Under Product Performance, Security, Dependability, Usability Under Organizational Operational, Environment, Developmental standards Legal, Accounting, Regulator and Ethical