Requirements Specication We have been asked to develop an automated Student Registration System (SRS). This system will enable students to register on-line for subjects each semester, as well as tracking a student's progress toward completion of their degree. The list of subjects (the university handbook) contains detailed information about each subject: subject number, department offering this subject, lecturer in charge, subject description. When a student rst enrolls at the university, he/she uses the SRS to set forth a plan of study as to which subjects he/she plans on taking to satisfy a particular degree program. The SRS will verify whether or not the proposed plan of study satises the requirements of the degree that the student is seeking. Once a plan of study has been established, then, during the registration period preceding each semester, students are able to view their enrolment on line, and choose whichever subjects he/she enrolls in for the coming semester. The SRS will verify whether or not the student has satised the necessary prerequisites for each requested subject by referring to the student's on-line transcript of subjects completed and grades received (the student may review his/her transcript online at any time). Assuming that (a) the prerequisites for the requested subject(s) are satised, and (b) the subject(s) meet(s) one of the student's plan of study requirements, the student is enrolled in the subject(s). It is student's responsibility to drop the class if it is no longer desired; otherwise, he/she will be billed for the subject. Students may drop a class up to the end of the rst week of the semester in which the class is being taught. Students are usually allowed to take 4 subjects per semester (5 if overloading is allowed). Lecturers in charge ofa subject should be able to see student list on-line. Tasks 1. List the primary actors using the system. 2. Create a list of use cases (draw the diagram). You can use any tools (e.g. Lucidchart or https://on|ine.visua|-paradigm.com/ rZ' or by hand) to draw the Use Case diagram. 3. Create brief descriptions for 2 use cases