Student Records System SRS – Requirements Definitions Non-Functional Requirements 1. The SRS should be Internet-accessible using only an Internet connection and a web browser. 2. The system should enforce security rules as determined by the school on the security permissions and privileges afforded to both the school staff and the student population in accessing the system over the Internet. Functional Requirements 1. Maintain Student Records A staff member logs into the course. A staff member enters the student ID for the student record he wishes to delete, or update. The student record displays on the screen. If the student is to be added, then the add student template will display on the screen. The SRS should add or maintain this information for each student: First Name, Middle Initials, Last Name, StudentID, department (e.g. Grad Law, Undergrad IT), and Date of Birth, GPA (scale of 1.0 - 4.0) These records can only be updated by the school staff who have the permissions to add/modify/delete any student record 2. Maintain Course Records A staff member logs into the system. A staff member enters the course ID for the course he wants to delete, or update. The course will then display on the screen. If the course is to be added, then the add course course template will display on the screen. The SRS should add or maintain this information for each course: CourseID, Course Name, Credit Hours, Description, Prerequisite Course These records can only be updated by the school staff who have the permissions to add/modify/delete any course record 3. Maintain Class Records A staff member logs into the system. A staff member enters the course ID for the class that he wants to either add, delete, or update. A list of all the classes for that course are then displayed. If a class is to be maintained, then the staff member will either update or delete it. If a class is to be added, then the type of class must be taken into consideration. There are two kinds of classes: online classes offered over the Internet which are accessible via a web browser and face-to-face classes that are offered on campus at the school. The SRS system should add or maintain this information for each class: CourseID, Class Begin Date, and Class End Date. In addition, online classes also should add or maintain this additional information: Class URL, Class Browser. Similarly, face-to-face classes should add or maintain this additional information about them: Class Building, Class Room. These records can be maintained only by the school staff that has permission to add/modify/delete any class record (either online or face-to-face) 4. Register a Student for Classes Both students and qualified school staff should be able to register a student for a class (either online or face-to-face) offering for a course. The registration process should proceed as follows: a. A staff member or student logs into the system. b. A list of available courses offered are displa.

1. Student Records System SRS – Requirements Definitions
Non-Functional Requirements
1. The SRS should be Internet-accessible using only an Internet
connection and a web browser.
2. The system should enforce security rules as determined by
the school on the security permissions and privileges afforded
to both the school staff and the student population in accessing
the system over the Internet.
Functional Requirements
1. Maintain Student Records
A staff member logs into the course.
A staff member enters the student ID for the student record he
wishes to delete, or update. The student record displays on the
screen. If the student is to be added, then the add student
template will display on the screen.
The SRS should add or maintain this information for each
student: First Name, Middle Initials, Last Name, StudentID,
department (e.g. Grad Law, Undergrad IT), and Date of Birth,
GPA (scale of 1.0 - 4.0)
These records can only be updated by the school staff who have
the permissions to add/modify/delete any student record
2. Maintain Course Records
A staff member logs into the system.
A staff member enters the course ID for the course he wants to

2. delete, or update. The course will then display on the screen. If
the course is to be added, then the add course course template
will display on the screen.
The SRS should add or maintain this information for each
course: CourseID, Course Name, Credit Hours, Description,
Prerequisite Course
These records can only be updated by the school staff who have
the permissions to add/modify/delete any course record
3. Maintain Class Records
A staff member logs into the system.
A staff member enters the course ID for the class that he wants
to either add, delete, or update. A list of all the classes for that
course are then displayed. If a class is to be maintained, then
the staff member will either update or delete it.
If a class is to be added, then the type of class must be taken
into consideration. There are two kinds of classes: online
classes offered over the Internet which are accessible via a web
browser and face-to-face classes that are offered on campus at
the school.
The SRS system should add or maintain this information for
each class: CourseID, Class Begin Date, and Class End Date. In
addition, online classes also should add or maintain this
additional information: Class URL, Class Browser. Similarly,
face-to-face classes should add or maintain this additional
information about them: Class Building, Class Room.
These records can be maintained only by the school staff that
has permission to add/modify/delete any class record (either
online or face-to-face)
4. Register a Student for Classes

3. Both students and qualified school staff should be able to
register a student for a class (either online or face-to-face)
offering for a course. The registration process should proceed as
follows:
a. A staff member or student logs into the system.
b. A list of available courses offered are displayed.
c. A course is selected from the list and all the offered classes
for the course are displayed.
d. A selection from the class list is then made to register for.
The process to register a student for a selected class begins.
e. The selected class to registration for is then validated against
these registration rules:
i. No duplicate registration for the same class
ii. Online classes registration requires students
acknowledgement that they have the required hardware and
software to access online classes
iii. No more than three class registration for open classes unless
student GPA is greater than 3.0. Then the student can take four
classes.
iv. The student has taken any required pre-requisite course.
f. When the registration is valid against the above rules, a
registration record is created and a message is then displayed to
confirm registration. Otherwise, a message explaining the
violation of the associated rule is displayed.
g. If registration is successful, one is added to the number of
students that have enrolled in the class.
h. 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.
SRS Requirements Definition Page 1

4. SRS Problem Domain
Activity Diagram
MAINTAIN STUDENT RECORDS
MAINTAIN COURSE RECORDS
MAINTAIN CLASS RECORDS

5. REGISTER A STUDENT FOR CLASSES
Week 2 Activity Diagram Page 1
text
COURSE
[Add Course]
Add Course
[Delete Course]
[Modify Course]
Delete Course
Modify Course

6. COURSE
Retrieve Course
List of Courses is Displayed
Display Classes for Entered Course
CLASS
[Add Class]
[Online Class]
Add Face to Face Class
[Face To Face Class]
Add Online Class
[Delete Class]
[Modify Class]
Delete Class
Modify Class
CLASS
text
[Add Class]
Display Classes for Entered Course
CLASS
[Online Class]
Add Face to Face Class
[Face To Face Class]
Add Online Class
[Delete Class]

7. [Modify Class]
Delete Class
Modify Class
CLASS
Display List of Courses
Display List of Classes of Selected Course
COURSE
STUDENT
REGISTRATION
CLASS
Select Class from Class List
Validate Registration Rules
[Valid Registration]
[Invalid Registration]
Display Violation Message
Display Confirmation Message
Create Registration Record
REGISTRATION
Update Class Enrollment
CLASS
text
Display List of Courses
Display List of Classes of Selected Course
COURSE
STUDENT
REGISTRATION

8. CLASS
Select Class from Class List
Validate Registration Rules
[Valid Registration]
[Invalid Registration]
Display Violation Message
Display Confirmation Message
Create Registration Record
REGISTRATION
Update Class Enrollment
CLASS
STUDENT
[Add Student]
Add Student
[Delete Student]
[Modify Student]
Delete Student
Modify Student
Retrieve Student
text
STUDENT
[Add Student]

9. Add Student
[Delete Student]
[Modify Student]
Delete Student
Modify Student
Retrieve Student
COURSE
[Add Course]
Add Course
[Delete Course]
[Modify Course]
Delete Course
Modify Course
COURSE
Retrieve Course
List of Courses is Displayed
Student Name: Daniel Rosado
Course:
CIS339
Session (month, year):
01/2016
Object-Oriented System Analysis and Design
The School of Prosperity
Student Records System (SRS)
Week1—System Request3

10. Week2—Use Case Diagram AND Use Cases Descriptions5
Week3—Class Diagram AND CRC Cards9
Week4—Sequence, Communication, and State Machine
Diagrams15
Week5—Package Diagram19
Week6—Method Contract AND Method Specification21
Week7—Object-Oriented Application Coding24
Week 1—System Request
1
Use this system request template and complete the SRS system
request.
System Request
The School of Prosperity
Student Records System (SRS)
Project sponsor:
The School of Prosperity (SoP)
Business Need:
New Internet-accessible Student Record System that will allow
students the capability to handle their own registration and staff
to maintain records, courses, and schedule online-face-to-face
classes.
Business Requirements:
1.) Online accessible system
2.) Reduce registration time
3.) Handle enrollment increases
Business Value:
1.) Reduction in time spent registering students by 90% from
1000 to 100 hrs.
2.) Increase in staff productivity by 10% resulting in
$50,000/yr. in cost savings
3.) Paper/Printer usage reduction resulting in approximately
$3,000 in savings/yr.
4.) Staff morale is expected to increase due to increased time

11. available for their projects
5.) Eliminate paper filing/registration errors
Special Issues or Constraints:
1.) Completion in one year
2.) Security; Students access to school files must be
addressed/restricted
3.) Possibly integrate with currently used home grown
apps/systems
2
I believe that my system request addresses the SRS Preliminary
Planning Overview because it addresses the issue of what the
customer wants, the specifics it is requiring along with the time
frame it is requesting it in.
Here are my five questions that would help clarify some project
issues/concerns:
1. Will the project team be responsible for loading all the
archived/previous semesters of data of students?
2. What are the levels of permissions/rights that will be
required at each level (i.e. Help Desk, Advisor, Dean, etc.)?
3. Does the one year time frame include deployment and
training, or is it just delivery of application/system?
4. Who will provide the architecture/infrastructure for this
deployment?
5. Is SoP looking for a licensed/supported application or are
they interested in a COTS (Custom off the Shelf) application
that they own outright?
3I completed my work by reviewing the Preliminary Planning
Overview and identifying, the request, sponsor, business
need(s), requirement(s), value and issues/constraints. I made the
decision to differentiate between what were needs/ requirements
and what were requests. The needs/requirements were where the
system was accessed (internet accessible), how/who accessed
the data/system (security) and when it needed to be in place (in

12. one year).
Week 2—Use Case Diagram and Use Cases Descriptions
1
SRS Use Case Diagram
Maintain Class Records
Use Case Name: Maintain Class Records
ID:
Importance Level:
Primary Actor: Staff
Use Case Type:
Stakeholders and Interests:
SoP Staff-Easily maintain
Students
Brief Description: This use case diagram displays the school
records of the classes offered at SoP along with full control of
the class. The staff can create, delete and or modify the class
record(s).
Trigger: SoP Staff maintaining/accessing class records
Type: External
Relationships:
Association: Staff
Include:
Extend:

13. Generalization:
Normal Flow of Events:
1. Staff accesses course listing
2. Staff enters course
3. Staff views listing of classes associated with the course
4. Staff accesses class
A. Modifies and or deletes class
B. Adds class
a. Online
b. Face to face
Alternate/Exceptional Flows:
If there is no course in the system that matches the one entered
by staff.
Register a Student for Classes
Use Case Name: Register student for classes
ID:
Importance Level:
Primary Actor:
SoP Staff
Student(s)
Use Case Type: Detail, Essential
Stakeholders and Interests:
SoP Staff - Register students for classes
Students – Register for classes
Brief Description: This use case retrieves the class and allows
the staff or student to register.
Trigger: SoP Staff or student registering
Type: External
Relationships:
Association: SoP Staff and students

14. Include:
Extend:
Generalization:
Normal Flow of Events:
1. Course listing is displayed
2. Course selected
3. Classes are listed
4. Class is selected
5. Validation is run
A. If validation returns true, student is registered
B. If validation returns false, student registration is
denied/declined
SubFlows:
1. Is class open for registration
2. No duplicate registration for the same class
3. Online classes registration requires students
acknowledgement that they have the required hardware and
software to access online classes
4. 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. The student has taken any required pre-requisite course
Alternate/Exceptional Flows:
0. When the registration is valid against the above rules, a
registration record is created and a message is then displayed to
confirm registration. Otherwise, a message explaining the
violation of the associated rule is displayed.
0. If registration is successful, one is added to the number of
students that have enrolled in the class.
0. 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.

15. 2Validated that the requirements requested were addressed and
follow necessary flow of the application.
3
The decisions that were made for this week’s iLab were
completed following the requirements laid out in SRS
Requirements Definition document. The Requirements
Document laid out the overall case diagram flow as well as the
subflows and what must be validated.
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

16. 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:

17. 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:

18. 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:

19. 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
1
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

20. 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

21. 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
2
Validate and verify your behavioral diagrams against the SRS
Register a Student for Classes use case description and the SRS
class diagram.
3
Explain how you completed your work, the decisions you made
to arrive at your conclusions, and the lessons you learned.

22. Week 5—Package Diagram
1
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
2
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.
3

23. 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
1
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

24. 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:

25. Argument Returned:
Data Type:
Notes:
Algorithm Specification:
Misc.Notes:

26. 2
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.
3
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
1
Copy your code text of the CourseList.GetCourseByCourseID()
method and paste it here:
Code Text of Your CourseList.GetCourseByCourseID() Method

27. 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:

28. A *.zip File of all of the Coding Project Files
2
Validate and verify your code and screenshot of the
CourseList.GetCourseByCourseID() method against the method
contract and the method specification of the same method.
3
Explain how you completed your work, the decisions you made
to arrive at your conclusions, and the lessons you learned.
Page 9 of 26