EX-1

1)
Do the Requirement Analysis and Prepare SRS(Course Registration System)

Aim: To do Requirement Analysis and Prepare SRS for Course Registration System. And also to
draw E-R diagrams, DFD, CFD and structured Charts for Course Registration System.

Problem Statement for Course Registration System

At the beginning of each semester students may request a course catalogue containing a
list of course offerings for the semester. Information about each course, such as professor,
department, and prerequisites will be included to help students make informed decisions.
The new course registration system will allow students to select four course offerings for
the coming semester. In addition, each student will indicate two alternative choices in case a
course offering becomes filled or cancelled. Assuming perquisites are satisfied for each student.
No course offering will have more than 30 students. No course offering will have fewer than 5
students. A course offering with fewer than 5 students will be cancelled.
Once the registration process is completed for a student, the registration system sends
information to the billing system, so the student can be billed for the semester.
For each semester, there is a period of time that students can change their schedules.
Students must be able to access the course registration system during this time to add or drop
courses. The billing system will credit all students for courses dropped during this period of time.
Professors must be able to access the course registration system to indicate which courses they
will be teaching. They will also need to see which students signed up for their course offering.

Software Requirement Specification Template:

Table of Contents
Revision History
1. Introduction
1.1 Purpose
1.2 Document Conventions
1.3 Intended Audience and Reading Suggestions
1.4 Product Scope
1.5 References
2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 User Documentation
2.7 Assumptions and Dependencies
3. External Interface Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces
3.4 Communications Interfaces
4. System Features
4.1 System Feature 1
4.2 System Feature 2 (and so on)
5. Other Nonfunctional Requirements
5.1 Performance Requirements
 5.2 Safety Requirements
5.3 Security Requirements
5.4 Software Quality Attributes
5.5 Business Rules
6. Other Requirements
Appendix A: Glossary
Appendix B: Analysis Models
Appendix C: To Be Determined List

Software Requirement Specification for Course Management System:

1. Introduction

1.1. Purpose
The purpose of this SRS is to describe the requirements involved in developing a Course
management system.

1.2. Document Conventions

The document is made using Calibri where:
 Main section are indicated with bold letters font 14
 Subsections also bolded with font 14.
An appendix A is added for acronyms and abbreviations

1.3. Intended Audience and Reading Suggestions

This document is intended to be read by the customer. This is a technical document and the terms
should be understood by the customer. The customer needs to understand this document fully so
that they can draft a design document using this SRS presented to them by the analyst.

1.4. Product Scope

The network based registration system will be used by students whom may be familiar or not
to the online registration process thus the scope of the project must be user friendly for both
students and admin.
This system will allow students with prerequisites for courses offered. Each student will
select 4 courses for the semester, and indicate two alternative choices in case a course offering
becomes filled or cancelled. Once the registration process is completed for a student, the
registration system sends information to the billing system so the student can be billed for the
semester.
 The system will have to keep a billing after the registration process has been completed. The
communication and the monitoring of the application will be handled by the for a smooth
registration process.

1.5. References
Sections of this document are based upon the IEEE Guide to Software Requirements
Specification (IEEE 830)
2. Overall Description
2.1. Product Perspective
This subsection should relate the requirements of that larger system to
functionality of the software and should identify interfaces between that system and
the software.
A block diagram showing the major components of the larger system,
interconnections, and external inter-faces can be helpful.

Online Registration Process Administrator

Student

Database

The course registration system involves two actors, the administrator and the student. The
administrator controls the communication and service delivery for student, the students
communicate with the system through application for courses offered. The database system
manages for application and financial information.

2.2 Product functions

This subsection of the SRS should provide a summary of the major functions that the software
will perform.
The key features of this system can be abstracted as follows.
 Authentication through users’ personal computer
 Alternative authentication mechanism for special conditions.
 Provide student with relevant courses for registration and a course catalogue.
 Registration process –check box method.
 Provide a proof of registration once the process has been submitted and terminated.
 Billing System generates a bill for student for that semester.

2.3. User Classes and Characteristics

This subsection of the SRS should describe those general characteristics of the intended users of
the product including educational level, experience, and technical expertise.
Users are students and admin.
Their characteristics:
 The user should be familiar with the Internet.
 User should be computer literate.

2.4 Operating Environment

Course registration system is an internet oriented application, it set to operate on a high
available and Qos network, since registration is a sensitive thing, the quality of the network
should be good for this process. Mostly a device that can access the internet and can support a
huge web application for registration. Any OS can support this system as it is not particularly
software or hardware dependent.
2.5 Design and Implementation Constraints
The system is internet based system, a webapp that should be developed to support any web
browser to be used, registration in the University is a sensitive issue an must be secure , the
system design should include a lot of DB and SYSTEM validation . Courses are billed by the
University policy so this part must be secure ,so developers needs to be always there to support
the delivered system in terms of validation and maintenance.

2.6. User Documentation

The project is available on the internet. The University website should provide a user
manual on how to use an online registration application. Users of the system will be guided by
the system all the way when registering.

2.7 Assumptions and Dependencies

The assumptions and dependencies relevant to the system are as follows.
 All users have an a computer or any web enable device
 User should have internet access.
 The user must have access or be on a reliable network.
 Users should have been admitted to the University, and have a student number. Users with
prerequisites are given student number.
 User should read course catalogue careful in order not to make mistakes , cause they are
un-reversible
 Besides the user catalogue to be given, users must know which course is expected of them
to register.
 Users should view bill for the registered course.

3. External Interface Requirements

3.1. User Interfaces
The user is going to interact with the system through different interfaces. Listed below are the
different components of user interfaces under their respective headings:
 student log-in / create profile
  Registration process.
 View and print

3.2. Hardware Interfaces

Minimum Hardware Requirements:
The system will run on different hardware gadgets. Below are the minimum hardware
requirements for the smooth running of the system:
 1GB RAM PC
 1.8Hz processor
 14” color monitor
 120GB HDD CPU
 Proper running internet

3.3. Software Interfaces

Databases: Oracle
Operating systems : Any OS like Windows7, Linux, Mac OS
Programming Language: Java
Front end: HTML, Java Script

3.4. Communications Interfaces

The main communication link that the system will be using is the internet.

4 System Features
4.1 . System Feature
The Course registration system comprises of two main features, namely, internet
connectivity which will enables users to communicate with the server through a browser or web
agent, and secondly the system requires database service to store the user’s data. In a nutshell
this system is web application and thus is only operational in an internet enabled environment.
4.2. Functional requirements
REQ-1: The system shall be internet oriented and require an online server.
REQ-2: The system shall save the user’s details to a remote database service
REQ-3: The system shall allow users to register and to log in a user account
REQ-4: The system will allow users to register for courses following the University Rules.
REQ-5: The system shall automatically update the course catalog
REQ-6: The system will allow users to view and print application and bill of applied courses.
 5. Other Nonfunctional Requirements
5.1. Performance Requirements
The system is required a fair amount of speed especially while browsing through the catalogue
and presenting different possibilities for the schedule.
The database shall be able to accommodate a minimum of 10000 records of students.
The software will support multiple users, with their respective accounts of course.

5.2. Safety Requirements

The system is required provide a protection of the database of the university.
5.3. Security Requirements
The main security concern is for users account hence proper login mechanism should be used to
avoid hacking. The online registration system shall not disclose personal information of students
to unauthorized users or the public.

5.4. Software Quality Attributes

Availability : Both catalogue and database will have to be available to students 24/7.

5.5. Business Rules

 The online registration system shall include two types of accounts: the administrators and
the students.
 To log in to the system user name and password is required. User name shall be the
student number of the student and the password as they prefer.

6. Other Requirements No other requirements.

Appendix A: Glossary
DB – database
SQL – simple query language
Admin –Administrator
SRS –software requirements specification
Webapp – web application
ID – identity
Std no: - student number
RAM – random access memory
PC – personal computer
CPU – central processing unit
OS – operating system