ITSU2010: Course Enrollment System Development Case Study

This report details the development of a course enrollment system for Easter State University, addressing the inefficiencies of their manual registration process. It outlines the vision, goals, and scope of the project, including definitions and assumptions. The report covers general design constraints, non-functional requirements such as usability, performance, and security, and models the static and dynamic aspects of the system using use case diagrams, class diagrams, sequence diagrams, and activity diagrams. User interfaces for different scenarios are presented, along with a usability attribute evaluation and instructions for user manuals and installation guides. The system aims to provide students with an online platform for course viewing, registration, and result access, while also serving as an information system for university staff. The report provides a comprehensive overview of the system's design and functionality, aiming to improve the course enrollment experience at Easter State University.

[Course Enrolment System development]
Case Study Report
[date]
This report is submitted as a partial requirement for the unit
ITSU2010 – Technical Documentation for Software Engineers
Members:
[Member 1 (name, Student ID)]
[Member 2(name, Student ID)]
[Member 3(name, Student ID)]
[Member 4(name, Student ID)]

[Title]
Contents
1. Introduction...................................................................................................................................4
1. Vision.........................................................................................................................................4
2. Goals and Objectives.................................................................................................................4
3. Scope.........................................................................................................................................4
4. Definitions.................................................................................................................................4
5. Assumptions..............................................................................................................................4
2. General Design Constraints...........................................................................................................4
1. Product Environment.................................................................................................................4
2. User Characteristics...................................................................................................................5
3. Mandated Constraints...............................................................................................................5
4. Potential System Evolution........................................................................................................5
3. Non-functional Requirements............................................................................................................5
1. Usability Requirements..............................................................................................................5
2. Operational Requirements........................................................................................................5
3. Performance Requirements.......................................................................................................5
4. Security Requirements...............................................................................................................5
5. Safety Requirements.................................................................................................................5
6. Legal Requirements...................................................................................................................5
7. Other Quality Attributes............................................................................................................5
8. Documentation and Training.....................................................................................................6
9. External Interface......................................................................................................................6
4. Modelling the static aspects of the system........................................................................................6
1. Use case Diagram......................................................................................................................6
2. Class Diagram............................................................................................................................7
5. Modelling the dynamic aspects of the system...................................................................................7
1. Sequence Diagram.....................................................................................................................7
2. Activity Diagram.........................................................................................................................9
6. User Interfaces................................................................................................................................10
1. User Interfaces – Scenario 1 (Sequence Diagram 1)................................................................10
2. User Interfaces – Scenario 2 (Sequence Diagram 2)................................................................10
3. Usability Attribute Evaluation..................................................................................................10
7 Manuals............................................................................................................................................10
1. User Manuals...........................................................................................................................10
2. Installation Guides...................................................................................................................11
2

[Title]
Bibliography.........................................................................................................................................12
3

[Title]
1. Introduction
The report has been developed for the explanation of the Course Enrolment System
development for the Easter State University. The organization currently performs their
registration and academic procedure manually and the process is very time-consuming and
frustrating as well. Hence, the business analyst has been hired to provide the organization
with the possible solution.
1. Vision
The Easter State University in looking to increase their business efficiency with the use of
the course registration system, which would reduce the hassles faced during a registration
process.
2. Goals and Objectives
The main goal of the system is to ease the course registration process for the Easter State
University and the student getting admitted into the University.
The main objectives of the project are:
 To provide the students with an online platform to view the details of the courses and
faculties offered by the university.
 To provide the student the option to register for the course online.
 To provide the option to avail the results for the courses that they enrol for.
3. Scope
The scope of the project is to provide the users with the online accessibility. The system
would also allow remote access to the system which would enable the user to perform their
acidity on the system without reaching the University itself.
4. Definitions
Academic: The process and the details related to the courses and the subjects in it.
Enrolment: Registration for a certain course.
5. Assumptions
It has been assumed that though the system is being developed for a course enrolment process
the system would also act as an information system for the college authorities.
2.General Design Constraints
1. Product Environment
The system would be uploaded in an online domain which would be helpful for the users
to access the system from any type of device via their web browsers. The system designed
would also be made available in the form of application in mobile devices.
4

[Title]
2. User Characteristics
The end users of the system are the students who would be able to access the system and
also the administrative staffs of the Easter State University who would handle the enrolments
of the students.
3. Mandated Constraints
The development of the systems would be done in the Asp platform and the Microsoft
database and cloud support is to be used. In addition to this, the mobile version would be
developed in the android platforms.
4. Potential System Evolution
This system can be further enhanced to create a virtual learning environment for the
students in the future where they can be used by the students to manage their courses.
3. Non-functional Requirements
1. Usability Requirements
The users of the system should be able perform their activities efficiently and the navigation
and menu features of the system are required to be implemented efficiently so that the users
would be able easily surf through the system.
2. Operational Requirements
The students should be able to visit the system and surf through the courses easily.
However, the staffs would be required to log in to perform any actions on the system.
3. Performance Requirements
The system should be reliable and it should respond efficiently to the users and provide
timely Reponses for the requests made by the users.
4. Security Requirements
The system should be able to provide security to the users so that their data do not get
hacked and the data of the users do not manipulate wrongly.
5. Safety Requirements
The authentication and data validation features for the developed system are to developed
correctly so that no unauthorised access occurs in the system.
6. Legal Requirements
The system should be able to maintain the legal aspects of system development that
compliance with the academic legislatives.
7. Other Quality Attributes
The system is accessible from remote locations so that the users would be able to perform
their actions from any locations.
8. Documentation and Training
The user manuals and the help section in the system would be helpful for the users to
understand the major procedures of the system.
5

[Title]
9. External Interface
The users should be having any web application or even a mobile application would be
helpful for the users to access the systems.
4. Modelling the static aspects of the system
1. Use case Diagram
Use Case List
The details of the use cases are provided in the table below:
Use Case ID Primary Actor Use Cases
UC-1 Student View Courses
UC-2 Student View Faculties
6

[Title]
UC-3 Student Enrolment
UC-4 Student Visit Website
UC-5 Professors, Staffs Log in
UC-6 Student View Marks
UC-7 Professors View Course Enrolments
Use Case Descriptions
View Faculties
Use Case ID: UC-2
Use Case Name: View Faculties
Created By:
Date Created:
Actors: Student
Description: The student can access details of the professors on the system
Trigger: Clicking on a details of a professor
Preconditions: Visit Website
Post conditions: View the details
Normal Flow: Users Systems
1. View Website
2. Click on a professors
1. Display list of professors
2. Provide the details of the
professors
Alternative Flows: NA
Exceptions: An exception can occur if the professor has updated wrong details
Includes: Visit Website
Frequency of Use: Very High
Special Requirements: NA
Assumptions: It is assumed that the students would have prerequisite knowledge about
which professor to visit.
Notes and Issues: Certain professors tech only certain courses.
Enrolment
7

[Title]
Use Case ID: UC-3
Use Case Name: Enrolment
Created By:
Date Created:
Actors: Student
Description: The students can enrol themselves into the system.
Trigger: Selection of course
Preconditions: View curses
Post conditions: View marks
Normal Flow: Users Systems
1. View Website
2. Click on a Course
3. Enrol
1. Display list of courses
2. Provide the details of the
course
3. Store Student details
Alternative Flows: NA
Exceptions: An exception can occur if there is no course which the student is looking for.
Includes: Visit Website
Frequency of Use: Very High
Special Requirements: Provide student details
Assumptions: It is assumed that the students would have prerequisite knowledge about
which Course to visit.
Notes and Issues: Students should have knowledge on the perquisite courses.
View Course Enrolments
Use Case ID: UC-7
Use Case Name: View Course Enrolments
Created By:
Date Created:
Actors: Professors
Description: The professors can view the students who would be in their class
Trigger: Clicking on a details of a Subject
8

[Title]
Preconditions: Visit Website
Post conditions: View the details
Normal Flow: Users Systems
1. Visit Website
2. Click on a subject
3. View students
1. Show the list of subjects
2. Show the list of students
3. Show student details
Alternative Flows: NA
Exceptions: An exception can occur if the professor has updated wrong details
Includes: Visit Website
Frequency of Use: Very High
Special Requirements: NA
Assumptions: It is assumed that the professors would have some subjects assigned to
them.
Notes and Issues: Certain professors tech only certain courses.
2. Class Diagram
9

[Title]
5. Modelling the dynamic aspects of the system
1. Sequence Diagram
The diagram provided below provides the details of the enrolment process of the system:
The description of the admin logging in and viewing the details of the enrolments are described
in the diagram below:
10

[Title]
11

[Title]
2. Activity Diagram
2.1. Activity Diagram 1:
12

[Title]
13

[Title]
2.2. Activity Diagram 2
14

[Title]
15

[Title]
6. User Interfaces
1. User Interfaces – Scenario 1 (Sequence Diagram 1)
2. User Interfaces – Scenario 2 (Sequence Diagram 2)
3. Usability Attribute Evaluation
System Status Visibility:
The system would be able to guide the system throughout their navigation procedure.
In addition to this, the users would be provided with a guide to the system that would help
them in using the system.
Error Prevention:
The developed system does not have any errors. All the system would also provide
checks other that the validations and authorizations. This would be preventing the users from
having repeated errors in the system.
Minimalistic designs:
The designs developed for system are officials and does not contain any type of
commercial designs and are developed strictly for the university which would be helping the
users in the reaching to their destination without any fuss.
7 Manuals
1. User Manuals
For using the system, the following instructions are followed:
 Login to the system with your credentials
 Look for the courses on the left and look for the professors on the right
 Select a course to view the details. Click on enrol for enrolment.
16

[Title]
2. Installation Guides
The system can be accessed from any type of web application. The link to system would
be obtained from any type of web browsers. In addition to this, the application would be
available in the android versions. The apk file would be provided to the users for
installations. After installation the users would be able to log into the system and perform
their tasks.
17

[Title]
Bibliography
Sherman, W.R. and Craig, A.B., 2018. Understanding virtual reality: Interface, application, and
design. Morgan Kaufmann.
Zhu, Y., Zhan, K. and Hou, X., 2018. Interface design of nanochannels for energy utilization. Acs Nano,
12(2), pp.908-911.
18