Preface

This document contains the Software Requirements Specification (SRS) of an Online Project Marking
System for the UNVERSITY OF KOTLI AJK. The main aim of this project is to add functionality to the order
to provide an online facility for For Online Admission for Student managing and registering students
accounts. This document has been prepared in accordance with the IEEE Std 830-1998, IEEE
Recommended Practice for Software Requirements Specifications [IEEE 1998]

1. Introduction

1.1 Purpose
The main objective of this document is to illustrate the requirements of the project Online
University System. This document describes the design decisions, architectural design and the
detailed design needed to implement the system. It provides the visibility in the design and provides
information needed for software support. The document gives the detailed description of the both
functional and non functional requirements proposed by the Teachers and students. The document
is developed after a number of consultations with the Teachers and students and considering the
complete requirement specifications of the given Project. The final product of the team will be
meeting the requirements of this document.

1.2. Document Conventions

The following are the list of conventions and acronyms used in this

document and the project as well:

Administrator: A login id representing a user with user administration

privileges to the software

User: A general login id assigned to users

Client: Intended users for the software

SQL: Structured Query Language; used to retrieve information

from a database

SQL Server: A server used to store data in an organized format

ASP: Active Server Pages: A Web Page formatted on the server

and delivered to the browser.

Layer: Represents a section of the project

Add or

Upload
 User Interface Layer: The section of the assignment referring to

what the user interacts with directly.

Application Logic Layer: The section of the assignment referring

to the Web Server. This is where all computations are completed.

Data Storage Layer: The section of the assignment referring to

where all data is recorded

Data flow diagram: It shows the dataflow between the entities.

Use Case: A broad level diagram of the project showing a basic

overview

Boolean: A true/false notation

Interface: Something used to communicate across different

mediums

Unique Key: Used to differentiate entries in a database

1.3 Scope
Online Admission System is developing for University of kotli and used to replace old paper work
system and PUMS And the main Goals of the system is to Automate the process carried out in the
organization with improved performance and realize the vision of paperless Admission

Some of the goals of the system are listed below

Manage large Number of student details.

Manage All details of student who registered for the course

Create student Account And maintain the data effectively.

View all details of the students.

Reduce the work load in interview the student for selections.

Activates like updating, modification ,deletion of record should be Easier.

2. 2. Overall Description
2.1 Product Perspective

The proposed university online Admission System is that Today in university students detail are
entered manually. The student detail in separate record are tedious task Referring to all these
record and updating is needed There is a chance for more manual errors .Goal of the system is to
automate the process carried out in the university with improved performance and realize the vision
of paperless admission .
Some of the goals of the system are listed below

Manage large Number of student details.

Manage All details of student who registered for the course

Create student Account And maintain the data effectively.

View all details of the students.

2.2 Product Features

The aim of the propsed system is to address the limitations of the current system.

The main Feature is that

 Reach to geographically scattered student: one of the important objective of the

admission system is communicate with all the student scatterd geographically.
 Reducing the time in activity
Reduce the time taken process the applications of the student admitting a student
,conductiong the online Examination,verify student marks and send call letter to the
selected students.
 Centralized data handling.
Transfer the data smoothly to all the departments and handle the data centralized way.
 Paperless Admission reduced manpower.
 Cost cutting. Reduce the cost involved in the admission process.
 Operational efficiency.improve the operational efficiency by improving the quality of
process.
There are three different users who will be using this
product:
Feature of Adminstration
The features that are available to the Administrator are: The administrator has the full
fledged rights over the system. Can create/delete an account. Can view the accounts. Can
change the password. Can hide any kind of features from the both of users.
Insert/delete/edit the information of available on system. Can access all the accounts of the
faculty members/students
Feature of students
The features available to the Students are: Can view Admission Detail available in their
system Apply online and view their marks. Of test . Can view the various reading material. 
 Can view and modify its profile but can modify it to some limited range.

2.3 User Classes and Characteristics

There are various kinds of users for the product.
Usually web products are visited by various users for different reasons.
The users include :
 Administrator
 who will be acting as the controller and he will have all the privileges of Admin
 Faculty members
Faculty members who will be using the above features by accessing the system online.
 Students
who will be using the above features by accessing the system online for Admission.

2.4 Operating Environment

The product will be operating in windows environment. Also it will be compatible with the IE
6.0. Most of the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher
version. The only requirement to use this online product would be the internet connection.

2.5 Design and Implementation Constraints

The Product is developed using PHP. The backend database for this SQL Server. The product
is accomplished with login facility so that specific function is available to specific student.

2.6 User Documentation

The product will include user manual. The user manual will include product overview,
complete configuration of the used software (such as SQL server), technical details, backup
procedure and contact information which will include email address. The product will be
compatible with the internet Browser 6.0 or higher. The databases will be created in the
MySQL database
2.7 Assumptions and Dependencies
The product needs following third party product. MySQL server to store the database. PHP
to develop the Product

3. External Interface Requirements