The existing desktop system will be upgraded to web-based application and this system will be used to maintain records of students, courses, classes, and student registration and grades.

Business Requirements:

The system is capable of having the following functonalities:

· Accessibility over the Internet

· Maintains records of school students

· Maintains records of courses offered by school

· Maintain records of classes offered of the above courses (both online and face-to-face classes)

· Students registration system is included as well

Business Value:

Conservative estimates of tangible value to the company include:

· The SRS will enable the school to continue the expansion of its student population and to effectively manage the expansion

· Eliminate many school staff hours re-entering paper form student registrations by allowing the students to self-register

· Make the system easy to access from anywhere there is an Internet connection and a web browser

Special Issues or Constraints:

· The SRS must be able to handle both online and face-to-face class offerings

· The system must be accessible over the Internet to both school staff and students each with appropriate permissions

· The SRS must try to integrate with and re-use existing desktop application code and database as much as possible to reduce development cost

Validate and verify that your system request addresses the SRS Preliminary Planning Overview.

The business need area explains what the SoP is requiring the system to operate. The business requirements consist of what the system must be able to handle and the expectations of the system (once it’s completed). The business value breaks down the details of information that the new system will save on both staff hours and finances for the school. The issues area give problems that could exist once the system is implemented.

Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.

I, carefully, read the SRS Preliminary Planning Overview and highlighted the important business needs that the SRS system is to meet. I then started to complete the various sections of the System Request Form and while doing so, I referred back to the SRS overview document to confirm my conclusions and understanding. The result of this iterative process is the current System Request Form.

Week 2—Use Case Diagram and Use Cases Descriptions

Generate a use case diagram for all of your use cases, including their actors. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here:

SRS Use Case Diagram

Use this use case description template and complete the two SRS use cases of (1) Maintain Class Records and (2) Register a Student for Classes.

Maintain Class Records

Use Case Name: Maintain Class Records	ID: 1	Importance Level: 1
Primary Actor: Staff Member	Use Case Type: Fully Dressed
Stakeholders and Interests: Staff Members, Student, Teacher
Brief Description: This use case covers the maintenance of student records. It covers adding, updating and deleting student records.
Trigger: Maintain Student Record Button Type: Fully Dressed
Relationships: Association: Include: Enter courseID Extend: Add Record, Update Record, Delete Record Generalization:
Normal Flow of Events: 1. Staff Members log ins to the system. 2. Enter Course ID 3. A list of all classes for that course are then displayed. 4. If the class is to be maintained, select update or delete 5. If the user selected to add the class. 6. Enter Class type(Online / Face to Face), then 6.1 7. Enter CourseID 8. Enter Class begin Date 9. Enter Class end Date 10. Save the record
SubFlows: 4.1. If the user selected update 4.2. If the user selected delete 6.1. If the class is Online 6.2. If the class is face-to-face
Alternate/Exceptional Flows: 4.2.1. User can see all records in editable form. User will update any record and click save. 4.2.2. A respective record with entered courseID will be deleted. 6.1.1. Enter Class URL 6.1.2. Enter Class Browser 6.2.1. Enter Class Building. 6.2.2. Enter Class Room.

Register a Student for Classes

Use Case Name: Register a student	ID: 2	Importance Level: 1
Primary Actor: Staff Member	Use Case Type: Fully Dressed
Stakeholders and Interests: Staff Member/ Student
Brief Description: This use case covers the registration process of a student using SRS.
Trigger: Register Student Button Type: Fully Dressed
Relationships: Association: Include: Extend: Generalization:
Normal Flow of Events: 1. A staff member or student logs into the system. 2. A list of available courses offered are displayed. 3. User selects a course from the list and all the offered classes for the course are displayed. 4. User can select class from the class list. 5. The selected class to registration for is then validated against the registration rules 6. When the registration is valid against the rules, a registration record is created and a message is then displayed to confirm registration. 7. If registration is successful, one is added to the number of students that have enrolled in the class. 8. After the student completes the class, his registration record is updated with a grade. But the student has the option of dropping the class while taking it.
SubFlows: 5.1. No duplicate registration for the same class 5.2. Online classes registration requires students acknowledgement that they have the required hardware and software to access online classes 5.3. No more than three class registration for open classes unless student GPA is greater than 3.0. Then the student can take four classes. 5.4. The student has taken any required pre-requisite course.
Alternate/Exceptional Flows: 6.1. A message explaining the violation of the associated rule is displayed.

Validate and verify your use case diagram and use case descriptions against the SRS Requirement Definition and the SRS System Request.

SRS has 4 major functionalities which are covered in the 4 use cases, which are as follows:

Functionality

Covered in Usecase

Maintain Student Records

Maintain Student Records

Maintain Course Records

Maintain Course Records

Maintain Class Records

Maintain Class Records

Register a Student for Classes

Register a Student for Classes

Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.

I first read the case thoroughly and then listed all the functional and non-functional requirements on the page. Then I extracted the major use-cases from them. After that I generated the flows for those use cases. After extraction of the major use-cases and their actors I build a use-case diagram and after getting the flows I end up getting the fully dressed use cases.

Week 3—Class Diagram and CRC Cards

1

Generate a class diagram for the SRS system. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here:

SRS Class Diagram

Use this CRC template and complete a CRC card for each class you designed in your SRS class diagram.

Class1 CRC Card

Front:

Class Name:

ID:

Type:

Description:

Associated Use Cases:

Responsibilities

Collaborators

Back:

Attributes:

Relationships:

Generalization (a-kind-of):

Aggregation (has-parts):

Other Associations:

Class2 CRC Card

Front:

Class Name:

ID:

Type:

Description:

Associated Use Cases:

Responsibilities

Collaborators

Back:

Attributes:

Relationships:

Generalization (a-kind-of):

Aggregation (has-parts):

Other Associations:

Class3 CRC Card

Front:

Class Name:

ID:

Type:

Description:

Associated Use Cases:

Responsibilities

Collaborators

Back:

Attributes:

Relationships:

Generalization (a-kind-of):

Aggregation (has-parts):

Other Associations:

Class4 CRC Card

Front:

Class Name:

ID:

Type:

Description:

Associated Use Cases:

Responsibilities

Collaborators

Back:

Attributes:

Relationships:

Generalization (a-kind-of):

Aggregation (has-parts):

Other Associations:

ClassX CRC Card

2

Validate and verify your class diagram and CRC cards against the SRS use case diagram and use case descriptions.

3

Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.

Week 4—Sequence, Communication, and State Machine Diagrams

Generate a sequence diagram for the SRS system Register a Student for Classes use case. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here:

Sequence Diagram for the Register a Student for Classes Use Case

Generate a communication diagram for the SRS system Register a Student for Classes use case. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here:

Communication Diagram for the Register a Student for Classes Use Case

Generate a state machine diagram for the SRS system RegistrationRecord object/class (the class that maintains the registration of a student in a class). The diagram must be generated by a UML drawing tool. Copy and paste your diagram here:

State Machine Diagram for the RegistrationRecord Object

Validate and verify your behavioral diagrams against the SRS Register a Student for Classes use case description and the SRS class diagram.

Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.

Week 5—Package Diagram

Generate a package diagram for the SRS system. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here:

SRS Package Diagram

Validate and verify your package diagrams against the SRS class diagram and the SRS Register a Student for Classes use case sequence and communication diagrams.

Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.

Week 6—Method Contract and Method Specification

Use this method contract template and complete a method contract for the GetCourseByCourseID() method of the CourseList class.

CourseList.GetCourseByCourseID() Method Contract

Method Name:	Class Name:	ID:
Clients (Consumers):
Associated Use Cases:
Description of Responsibilities:
Arguments Received:
Type of Value Returned:
Pre-Conditions::
Post-Conditions:

Use this method specification template and complete a method specification for the GetCourseByCourseID() method of the CourseList class.

CourseList.GetCourseByCourseID() Method Specification

Method Name:	Class Name:	ID:
Contract ID:	Programmer:	Date Due:
Programming Language: Visual Basic Smalltalk C# Java
Triggers/Events:
Arguments Received: Data Type:	Notes:




Messages Sent & Arguments Passed: ClassName.MethodName:	Data Type:	Notes:








Argument Returned: Data Type:	Notes:

Algorithm Specification:
Misc.Notes:

Validate and verify your method contract and method specification against the CRC card for the CourseList class and the CRC card for the Course class.

Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.

Week 7—Object-Oriented Application Coding

Copy your code text of the CourseList.GetCourseByCourseID() method and paste it here:

Code Text of Your CourseList.GetCourseByCourseID() Method

Copy a screenshot of running the unit test of the CourseList.GetCourseByCourseID() method and paste it here:

Screenshot of running the Unit Test of CourseList.GetCourseByCourseID() Method

Zip all the files you used in this coding project; copy and paste the *.zip file here so that it can be unzipped and loaded into the IDE and run on another computer:

A *.zip File of all of the Coding Project Files

Validate and verify your code and screenshot of the CourseList.GetCourseByCourseID() method against the method contract and the method specification of the same method.

Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned.

Page 21 of 27