COMSATS University, Islamabad

Department of Computer Science

Assignment No. 03

Online Course Registration System

Submitted by:

Sadaf Kayani
FA17-BSE-121

Umay Haani
FA17-BSE-139

Noor-ul-Ain Nasir
FA17-BSE-149
Table of Contents
1. Introduction ------------------------------------------------------------------------------------------
1.1. Purpose ------------------------------------------------------------------------------------------
1.2. Document Conventions ------------------------------------------------------------------------
1.3. Project Scope ---------------------------------------------------------------------------------
1.4. References ---------------------------------------------------------------------------------
2. Overall Description ---------------------------------------------------------------------------------
2.1. Product Perspective --------------------------------------------------------------------------------
2.2. User Classes and Characteristics ---------------------------------------------------------------
2.3. Operating Environment ------------------------------------------------------------------------
2.4. Design and Implementation Constraints ------------------------------------------------------
2.5. Assumption and Dependencies ---------------------------------------------------------------
3. System Features ------------------------------------------------------------------------------------------
3.1. System Feature X ---------------------------------------------------------------------------------
3.2. Description ------------------------------------------------------------------------------------------
3.3. Functional Requirements ------------------------------------------------------------------------
4. Data Requirements ---------------------------------------------------------------------------------
4.1. Logical Data Model --------------------------------------------------------------------------------
4.2. Data Dictionary ---------------------------------------------------------------------------------
4.3. Reports ------------------------------------------------------------------------------------------
4.4. Data Acquisition, Integrity, Retention, and Disposal ------------------------------------
5. External Interface Requirements ------------------------------------------------------------------------
5.1. User Interfaces ---------------------------------------------------------------------------------
5.2. Software Interfaces ---------------------------------------------------------------------------------
5.3. Hardware Interfaces ---------------------------------------------------------------------------------
5.4. Communication Interfaces ------------------------------------------------------------------------
6. Quality Attributes ---------------------------------------------------------------------------------
6.1. Usability ------------------------------------------------------------------------------------------
6.2. Performance ------------------------------------------------------------------------------------------
6.3. Security ------------------------------------------------------------------------------------------
6.4. Safety ------------------------------------------------------------------------------------------
6.5. [others] ------------------------------------------------------------------------------------------
7. Internationalization and Localization Requirements ---------------------------------------------
8. Other Requirements ---------------------------------------------------------------------------------
9. Appendix A: Glossary ---------------------------------------------------------------------------------
10. Appendix B: Analysis Models ------------------------------------------------------------------------
1. Introduction
Presently, the online course registration system at COMSATS is only nominal; time and again
students have encountered innumerable problems with the pre-existing system, hence, the
university management has decided to opt for a fully functional and effective Online Course
Registration System. The Online Course Registration System is a web based system that will
show students what courses are available to them for registration, allow them to register
courses prior to the commencement of classes, withdraw or add courses within the defined
timelines and give them more control over their schedule. Additionally, the system shall not
only allow admins to set and modify the schedule but it shall also allow teachers to view the
courses and classes that have been assigned to them.

Unlike the current system that is neither fully manual nor fully online, the new system will
save students the time and confusion involved in course registration and will prove time saving
for the management team as well.

1.1. Purpose

1.2. Document Conventions

Font Family:
This document is written in Times New Roman Font.

Font Size:
 Main sections are written in bold with font size 18.
 Sub-sections are written in bold with font size 14.
 Inner text is in font size 12.

Appendices:
 An appendix named ‘Glossary’ is added at the end; it provides explanation for
acronyms and abbreviation that are used throughout this document.
 Also included is Appendix B - titled ‘Analysis Models’ - which contains a list of
figures that are used in this document.

1.3. Project Scope

1.4. References

2. Overall Description
2.1. Product Perspective

Students Admin
Login Login
Student Admin

Teachers
Login

System
Database
Teacher

Figure 1 Online Course Registration System Environment

The Online Registration System is being developed and designed to compensate for the lack
of a fully functional registration system. It shall act as a replacement for the previously existing
registration system which functions partly online and partly manually. Once the system is
functioning properly, it will be integrated with other systems that are also operating within the
university environment (such as students portal, teachers portal, administrative portals etc.);
for that, interfaces will be established between these systems.
The Online Course Registration System involves three primary actors who will be able to
access their corresponding portal through their respective login systems.
 Admin
 Student
 Teacher
The system also involves a secondary actor namely the System Database. The information flow
between the system and its database shall be bi-directional i.e. information shall be retrieved
from as well added to the database.
2.2. User Classes and Characteristics

Mentioned below are the three user classes involved in this system:

2.2.1. Admin Class

Admin

+ First Name + Last Name

+ ID - Password
login()
viewCourses()
setSchedule()
modifySchedule()
assignCourse()
assignTeacher()
setTimeSlot()

Figure 2 Admin Class

 Admin shall login to the system by providing ID and password.

 After user authentication, admin can access the system functionalities
corresponding to his/her ID.
 Admin can view all the courses being offered to all the semesters and all the
programs of his/her department.
 Admin can set schedule for each semester of every program; assign courses
to each semester, assign teachers to each section, set time slots for each class.
 Admin can modify the schedule if it has already been set but some changes
are to be made.

2.2.2. Student Class

Student

+ First Name + Last Name

+ Student ID - Password
 login()
viewCourses()
registerCourse()
withdrawCourse()
submitRegForm()

Figure 3 Student Class

 Student shall login to the system by providing student ID and password.

 After user authentication, student can access the system functionalities and data
corresponding to his/her ID.
 Student can view all the courses being offered his/her semester.
 Student can register any course of his/her choice.
 Student can withdraw a course within specified time limit.
 Student can submit registration form once they have made all the choices
pertaining to their schedule.

2.2.3. Teachers Class

Teacher

+ First Name + Last Name

+ Teacher ID - Password
login()
viewCourses()
viewClasses()

Figure 3 Student Class

 Teacher shall login to the system by providing student ID and password.

 After user authentication, teacher can access the system functionalities and data
corresponding to his/her ID.
 Teacher can view all the courses that have been assigned to him/her.
 Teacher can view all the classes that have been assigned to him/her.

2.3. Operating Environment

As it has been previously mentioned, the Online Course Registration System shall operate
within the university environment and shall be integrated with other systems that are
already operating in the university. These systems include the students portal, teachers
 portal and other administrative/management systems. This integration must ensure that
the entire system functions smoothly without any discrepancy and incongruity.

2.4. Design and Implementation Constraints

 As a partially functioning course registration system is already available, so,

instead of devising the system from scratch, developers must build upon the
functionality that is previously available.
 Being a web based system, the system should fully support all web browsers.
 The system shall use MySQL database for all data management tasks.

2.5. Assumption and Dependencies

Assumptions:
 AS-I: All users have internet access.
 AS-II: As user information is sensitive, so, it is assumed that users are connected
to a reliable network.
 AS-III: Students are registered in the university and have a valid registration
number/ID.
 AS-IV: Registration fees are cleared prior to course registration.
 AS-V: In case of no registration activity by a student, his/her registration shall
stand cancelled by the system.
 AS-VI: It is assumed that each admin can manage schedule only for one
department, therefore, the system functionality will be designed to accommodate
that.
Dependencies:
 DE-I: As new courses shall be offered based upon previous course history,
therefore, the system shall need access to previous database.
 DE-II: As the new system shall function entirely online, therefore, massive dataset
will need to be stored. Hence, smooth and quick functioning of system is highly
dependent upon the database.

3. System Features
3.1. System Feature X

3.2. Description

3.3. Functional Requirements

4. Data Requirements
 4.1. Logical Data Model

4.2. Data Dictionary

4.3. Reports

4.4. Data Acquisition, Integrity, Retention, and Disposal

5. External Interface Requirements

5.1. User Interfaces
Screen Resolution
The standard screen resolution of the system will be 1046x768.
Most of the displayed material will be in HD.
Keyboard Shortcuts

5.2. Software Interfaces

5.3. Hardware Interfaces

5.4. Communication Interfaces

6. Quality Attributes
6.1. Usability

Priority: 5
 The user interface of the system should provide ease of navigation to the user.
 Layout of components within the system should be predictable i.e. it should be
easy to locate each and every component.

6.2. Performance

Priority: 4
 In case of a request by a user for viewing course catalogue, the system should
display the course list within three seconds.s
 The system shall support up to 2000 simultaneous users against the central
database at any given time.

6.3. Security
 Priority: 7
 As the system contains users’ personal data, therefore, the system should only
accept a password with a strength value of 8 or more on a scale of 0-10.
 The university management team should define the criteria for strength values
of password.
 The system shall lock a user’s account after four consecutive unsuccessful
login attempts within a period of five minutes.
 A user shall have to change the temporary password assigned by the security
officer to a previously unused password immediately following the first
successful login with the temporary password.

6.4. Availability

Priority: 5
 Two weeks before the onset of new semester and three weeks into the semester,
the system must be available at least 98 percent of the time.

6.5. Integrity

Priority: 6
 The system shall protect against the unauthorized addition, deletion, or
modification of data.
 If a change in data is made on the students end, the system shall introduce that
change persistently at all other ends (admin and teacher) as well.

6.6. Interoperability

Priority: 4
 The OCRS shall be able to operate efficiently when it is integrated with other
systems in the environment.

6.7. Efficiency

Priority: 3
 At least 30 percent of the database capacity and memory available to the system
shall be unused once 95 percent of the registration process has been finalized.

6.8. Reusability

Priority: 4
  At least 30 percent of the system architecture should be reusable in newer
environments.

7. Internationalization and Localization Requirements

8. Other Requirements
Appendix A: Glossary
Appendix B: Analysis Models