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.

This template is a guide for you to organize your information. To complete it, replace the bracketed text with the relevant information. Some areas may be too large or too small for the information youre inserting. Adjust the size of the areas as necessary.

Name: [Insert your name.]

Date: [Insert the date.]

Creation: Generate your student information system (SIS) use case diagram. Refer to textbook pages 121129.

[Copy and paste your diagram here.]

Using the use case description template (refer to textbook pages 141148), provide a description for each use case in your use case diagram:

Use Case Name: [Insert information.]	ID: [Insert information.]	Importance Level: [Insert information.]
Primary Actor: [Insert information.]	Use Case Type: [Insert information.]
Stakeholders and Interests: [Insert information.]
Brief Description: [Insert information.]
Trigger: [Insert information.] Type: [Insert information.]
Relationships Association: [Insert information.] Include: [Insert information.] Extend: [Insert information.] Generalization: [Insert information.]
Normal Flow of Events: [Insert information.]
SubFlows: [Insert information.]
Alternate/Exceptional Flows: [Insert information.]

Use Case 1 description template:

[Insert information.]

Use Case 2 description template:

[Insert information.]

Use Case X description template:

[Insert information.]

Testing: Verify and validate your use case diagram and use case descriptions against the SIS requirements definition.

Check your diagram against the SIS requirements and write this review. In doing verification, the objective is to make sure that you are building software according to user specifications. Ask questions like these: Does each use case have the required functionality? Do all the use cases combined perform as a complete coherent system?

[Insert information.]

Approach Explanation: Explain your approach to the problem, the decisions you made to arrive at your solution, and how you completed it.

Explain why you chose these particular use cases and why you chose the relationships between them. Explain your approach to creating your functional model and the design decisions you made to create it.

[Insert information.]

Self-Reflection: Reflect on this experience and the lessons you learned from it.

These are your reflections on what you learned. Address what you found challenging and what you found easy. Discuss your experience creating your functional model and the lessons you learned from it. Specifically, draw connections between your experience and the object-oriented techniques and methods discussed in this course.

[Insert information.]