6 2 Final Project Part II Submission SIS Structural Model CRC Cards and Class Diagrams PDF

Preview

Summary

Module 6...

Description

IT 315 Final Project Part II Solution Submission Template Name: Kenneth Posley Date: 8/8/2021

This template is a guide for you to organize your information. Some information may be too large or too small for the area which it is intended. Resize or rearrange the area as necessary. 1.

Using this class responsibility collaboration (CRC) card template, document each class you identified from your student information system (SIS) functional model:

CRC Card 1 Front: Class Name: Course

ID: 1

Type: Domain, concrete

Description: The Course will contain classes that are taken by students Responsibilities: Add Course Delete Course Retrieve Course Display Course Modify Course Back:

Collaborators:

Attributes: Course ID Course Name Credit Hours Description Prerequisite Course Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations:

CRC Card 2 Front:

Associated Use Cases: Maintain Course Records

Class Name: Class

ID: 2

Type: Domain, Abstract

Description: The Classes which are part of the Course to be Undertaken by Students

Associated Use Cases: Maintain Class Records

Collaborators: Course

Responsibilities: Display Classes Delete Class Modify Class Add Class Display Courses Back: Attributes: Course ID Class Begin Date Class End Date Class Status Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations:

Course

CRC Card 3 Front: Class Name: Student

ID: 3

Type: Concrete, Domain

Description: This class contains the records of students for various classes. Responsibilities: Add Student Retrieve Student Delete Student Modify Student Back: Attributes: First Name Middle Initial Last Name Student ID Department Date of Birth GPA Relationships:

Associated Use Cases: Maintain Student Records

Collaborators: Course, Class

Generalization (a-kind-of): Aggregation (has-parts): Other Associations:

Course, Class

CRC Card 4 Front: Class Name: Face to Face ID: 4 Type: Domain, Concrete Classes Description: As a sub-class of the Class Abstract, Associated Use Cases: Maintain Class Records it contains details about the face-to-face classes. Responsibilities: Collaborators: Class Display Classes Delete Class Modify Class Add Face to Face Class Display Courses Create Account Enable Registration Back: Attributes: Class Building Classroom Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations:

Class

CRC Card 5

Front: Class Name: Online Classes ID: 5

Type: Domain, Concrete

Description: As a sub-class of the Class Abstract, it contains details about the face-to-face classes.

Associated Use Cases: Maintain Class Records

Collaborators: Class

Responsibilities: Delete Class Modify Class Add Online Class Display Courses Enter login Create Student Account Back: Attributes: Class URL Class Browser Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations:

Class

CRC Card 6

Front: Class Name: Registration

ID: 6

Type: Domain, Concrete

Description: Student’s registration Process for Associated Use Cases: Student classes registration Responsibilities: Collaborators: Class, Student, Course Validate Registration Display Validation Message Display Confirmation Message Create Registration Record Update Class Enrollment Select Class from List Display Courses Display Classes Retrieve Student Back: Attributes: Student ID Course ID Registry Date Student GPA Relationships: Generalization (a-kind-of):

Course, Class, Student

Aggregation (has-parts): Other Associations:

SIS Class Diagram

2. Verify and verify your CRC cards and class diagram to your SIS functional model by doing the following:

To verify my CRC Cards and class diagrams, I conducted an analysis in many areas, including external consistency, internal consistency, and whether or not the unique models of the same type are in accordance with comparable business requirements.

When creating the class-to-course diagrams for each course, I utilized a regular

association with one-to-many connections since each course has many class relationships. When connecting the Class to the Online Class/Face to Face Class, I utilized a parent-child connection to represent the fact that a class may be conducted either face-to-face or online. I utilized an aggregate association for the association of two Student/Course/Courses since the registration process would need to access a portion of each of the three classes, rather than the full class, and so I used an aggregation association. The aggregate connection is also more suitable in these situations since registration will occur from more than one class. Because each student is only enrolled for one specific course, I utilized a one-to-one connection for the registration to Student/Course cardinality association. To represent cardinality in the Registration to Class connection, I used the one to any relationship since a student may register for more than one class at a time if they meet all other requirements and pass the validation criteria. To make the CRC cards more legible, I utilized standard spacing for the characteristics on the cards. Camel Case was utilized in the illustration. 3. Describe your approach to the issue, the choices you made to arrive at your solution, and the steps you took to finish it. For example: There was an issue with the CRC cards since the Concrete domain, which was utilized in the cards, should have been automatically generated inside the scope of the domain. The class domain could not be created on its own since it is either an online class or a face-to-face class, therefore it was not feasible to do so. The registration card necessitated further explanations due to the fact that each of the characteristics on the card was calculated independently.

To arrive at a solution, I decided to use object-oriented software design as a key element. This approach allowed me to create software systems that were more sophisticated, more adaptable to

changes in the environment, and that included classes that were more easily reused. I was able to finish this project via collaboration, and the courses offered as part of this strategy contribute to the achievement of the program's goals. Because of how difficult it may be to split a program into isolated situations and to separate a specific class into strategies that are independent of one another, the usage of an object-oriented software design method proved to be very helpful. 4. A Personal Reflection on the Observation and the lessons learned Essentially, I've learnt that including the CRC cards into the whole planning process guarantees that the "Responsibilities" section accurately represents the assignments that an item of the class is expected to complete by giving a detailed explanation of what is expected of them. I did not identify specific areas of interest in the way in which tasks should be done, nor did I provide comprehensive instructions. The “Class Name” part just includes the name of the class, while the “Collaborators” section comprises classes that are required by the objects for them to execute their different tasks. Also possible are the inclusion of classes that make use of the object....