must be drawn in uml

Analyze the SIS requirements and formalize them as use cases. You should have between four to six use cases. Generate a use case diagram showing the actors associated with each use case, and structure your use cases using , , and generalization relationships. The use case diagram must be generated by a UML drawing tool such as draw.io or Visio. Using the Final Project Part I Solution Submission Template document, provide a description for each use case in your use case diagram. Use this same document to complete and submit your deliverables. Your functional model should be complete and professional. Specifically, the following critical elements must be addressed: Creation: Analyze the SIS requirements and formalize them as use cases in a use case diagram, showing the actors associated with each use case. You should have between four to six use cases. Structure your use cases using <>, <>, and generalization relationships. Provide a description for each use case that is correct, complete, and valid for the SIS system. Testing: Verify and validate your functional model against the requirements of the SIS system.

Nonfunctional Requirements:

The student information system (SIS) should be accessible as both a website and a mobile app.

The SIS users are students and enrollment staff.

The SIS should enforce appropriate security privileges to its uses.

Functional Requirements:

Maintain Student Records

The SIS should maintain records of basic information about students such as:

First name

Middle initials

Last name

Date of birth

Student ID

Department (e.g., psychology)

Cumulative GPA (on a scale of 1.0 to 4.0)

These records are updated by the enrollment staff who has the permissions to add, modify, and/or delete any student record.

Maintain Course Records

The SIS should maintain records of all the courses offered by the college.

The system should maintain the following fields for each course:

Course ID

Course name

Credit hours

Description

Prerequisite course

These records are updated by the enrollment staff who has the permissions to add, modify, and/or delete any course record.

Maintain Class Records

Classes are offered each semester of the above courses.

There are two kinds of classes: Online classes offered over the internet are accessible via a web browser and face-to-face classes are offered on campus at the college.

A class cannot exist without an associated course in the system.

The basic information to maintain for all kinds of classes include the following:

Course ID

Class begin date

Class end date

In addition, online classes also maintain the following information:

Class URL

Class browser

Similarly, face-to-face classes should maintain this additional information about them:

Class building

Class room

These records are updated by the enrollment staff who has the permissions to add, modify, and/or delete any class record (either online or face-to-face).

Register a Student for Classes

Both students and enrollment staff should be able to register a student (either online or face-to-face) for a class offering for a course. The registration process should proceed as follows:

The student information is entered to identify the registering student.

The course information for which to register is entered to identify the course.

All future classes with start dates after the current date for this course are displayed.

The enrollment staff enter future classes for only one semester out.

A selection of one class for which to register is then made.

The selected class registration is then validated against the following registration rules:

There is no duplicate registration for the same class in one semester.

Online class registration requires students to acknowledge that they have the required hardware and software to access online classes.

No more than three class registrations are allowed for one student in one semester unless the students GPA is greater than 3.5. (In this case, there is no limit on number of class registrations.)

When the class registration is validated against the above rules, a confirmation is then displayed to confirm registration. Otherwise, a message explaining the violation of the associated rule is displayed.

The process continues, starting from item b), until the user ends the session.