Overview

Programming is often described as both an art and a science. Given that even the simplest programming task can yield many possibly solutions, one of the most powerful ways of learning the art of programming is to see other programmers' solutions. These discussions offer you the opportunity to explain your process, reflect on the experience, ask questions for clarification, and gain insight from your classmates' responses and instructor's guidance.

Prompt

Your initial post should include an embedded use case diagram for the Courses and Classes Records Requirements, an explanation of your process, verification and validation of your model, and a reflection of what was learned in the activity. If you are unable to successfully complete the assignment by the initial deadline, you should post what you have achieved and an explanation of the process you have gone through to try and solve any problems you are encountering. This is an opportunity to reach out to your course community.

 

Your initial post should include the following:

• Comprehension: Provide a use case diagram.
• Comprehension/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.
• Verification and Validation: Verify and validate your use case diagram and use case descriptions against the SIS requirements definition. Check your diagram against the CIS requirements and compelete 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? does the use cases combined perform as a complete, coherent system?
• 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.
• Explain the steps you took to complete the activity.
• Verify and validate your use case diagram.
• Reflect on your experience and what you learned.

 

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:

1. First name
2. Middle initials
3. Last name
4. Date of birth
5. Student ID
6. Department (e.g., psychology)
7. 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:

1. Course ID
2. Course name
3. Credit hours
4. Description
5. 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:

1. Course ID
2. Class begin date
3. Class end date

• In addition, online classes also maintain the following information:

1. Class URL
2. Class browser

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

1. Class building
2. 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:

1. The student information is entered to identify the registering student.
2. The course information for which to register is entered to identify the course.
3. All future classes with start dates after the current date for this course are displayed.
4. The enrollment staff enter future classes for only one semester out.
5. A selection of one class for which to register is then made.
6. The selected class registration is then validated against the following registration rules:
7. There is no duplicate registration for the same class in one semester.
8. Online class registration requires students to acknowledge that they have the required hardware and software to access online classes.
9. No more than three class registrations are allowed for one student in one semester unless the student's 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.

Courses and Classes Records System Requirements Definitions

 

Nonfunctional Requirements

• The system should be accessible over the internet sentence.
• Only staff members are the users of the system.
• The system should ensure that only allowed users are able to use the system.

Functional Requirements

• Maintain Course Records
• The system should maintain CRUD operations on (i.e., provide CREATE, READ, UPDATE, and DELETE operations on) course records with the following attributes:

1. Course identification (e.g., IT 315)
2. Course name (e.g., Object-Oriented Analysis and Design)
3. Credit hours
4. Description

• Maintain Class Records
• Of the above courses, classes are offered each semester. There are two kinds of classes. Online classes are offered over the internet and accessible via a web browser; face-to-face classes that are offered on campus at the college. A class cannot exist without an associated course in the system
• The system should maintain CRUD operations on (i.e., provide CREATE, READ, UPDATE, and DELETE operations on) class records with the following attributes:

1. Course identification
2. Class begin date
3. Class end date

• In addition, online classes maintain the following additional attributes:

1. Class URL
2. Class browser

• Similarly, face-to-face classes maintain the following additional attributes:

1. Class building
2. Class room