AIR UNIVERSITY MULTAN CAMPUS,

MULTAN

MSCS (2nd Semester)

Software Engineering

[First Deliverable for College Management Information

System of Higher Education Department]

Submitted to : Sir. Ahmad Mohsin

Submitted by : Muhammad Amin (121170

M. Naveed Qadri (121178)
M.Adnan Faisal Khan(121182)
COLLEGE MANAGEMENT
INFORMATION SYSTEM OF
HIGHER EDUCATION
DEPARTMENT
1. Introduction

Requirements engineering is one of the most important process in the software developments life
cycle. The better we perform this portion better we have results. The bottom line of all the products being
developed is the Quality. One aspect of the Quality is achieved through better understanding of user
requirements and their conformance in the final product. In this document call Software Requirements
Specification Document will be documenting all the necessary Requirements for “ Online the College Wing
of Higher Education Department Punjab” System which is a web based application.

Higher Education Department Punjab is a Government higher education management department

in Lahore (Punjab). It deals with all matter of higher education in Punjab. Currently, this web based
application is being used only by the consultants or divisional NDBA.

1.1 Purpose

Up to now the SRS of this system has not been created. By developing its SRS will not only improve
the software Quality but it will also increase the academia background of the Requirements gathering team.
The purpose of the Requirements Specification Document is to specify all requirements for “Online the
College Wing of Higher Education Department Punjab” System which will provide a solid foundation for
System understanding.

This will help the software designers in developing this system in accordance with the requirements
given in this specification document. This specification describes Higher Level Business Requirements,
User Requirements all the functional and non-functional requirements, constraints, and other factors
necessary to provide a complete and comprehensive description of the overall software to be designed and
developed tested and finally put into the implementation phase.

1.2 Scope

The scope of this document is to specify requirements for the software to be delivered. Here the
scope of this document is limited to identify the Business, User, functional and nonfunctional Requirements
and their description, and what are the assumption and constraints by the clients that will be applicable to
the required system.

2. Overview

Adviser Logic offers a blend of different business planning services which enables company’s
consultants/advisers make predictions and suggest improvements in the business operations of their
clients. The system also allows them to give financial advice and appropriately communicate with the clients
seeking advice.

Target customers of the system are the financial planners of Alias Bit. Advisers maintain the entire database
of their clients’ information including all their expenses, investments and liabilities. Advisors may also
communicate with their clients by sending out different email through Communication manager.

So far two versions of the system have been released, but in the absence of formal requirement engineering
techniques and processes they are facing serious issues related to the delivery of quality services. We
proposed to make a thorough documentation of the System Requirements thereby producing a proper
Requirements Document and at the end of the day validating these documents using various RE tools and
techniques. Before moving towards 3rd version of the system we should have proper documentation first.
We will combine both the Developer’s team and SQA team in Requirements Engineering phase along with
RE team. This will increase their overall productivity of the services they are providing to the clients.
In this document we will cover:

 Business Level Requirements

 User Level Requirements

 Functional Requirements for the system

 Non-functional requirements

Constraints or assumptions of the Specification.

Business Requirements:
Business requirements are what must be delivered to provide value. Products, systems, software, and
processes are the ways how to deliver, satisfy, or meet the business requirements whats. Consequently,
the topic of business requirements often arises in the context of developing or procuring software or other
system; but business requirements exist much more broadly. That is, 'business' can be at work or personal,
for profit or non-profit.

“It is the time now to switch all the data and information
regarding the gazztted staff of the Higher Education department
from manual to computerized, for that reason a huge data base
is required which can handle this data. The system should be able
to maintain the profile of the teachers, their particulars, their
annual results, their STR (Student Teacher Ratio), their Annual
confidential Report (ACR). Along with all this data the portal can
also manage the student enrollment (class wise, subject wise and
discipline wise). So department started a portal “Online the
College Wing of Higher Education Department Punjab” that can
easily manage all this data.”

User Requirements
 Log into the system
 Manage the Staff Profile
 User can use the switch board
 Manage the Notice Board
 Can view the institutes
 Manage the Vacancy Position
 Add/Edit the staff statement
 Add the new teacher’s Profile
 User Logout the system
 User Login

Home Page

Switch Board Notice Board

Notice Add/Delete Personal Profile View Institute Notice View

Notice Add/Delete NIC

View College
View Personal Profile
Information

View Student View Vacancy Position

View Staff Information
Enrollment Information Information

Functional Requirements
FR01: User Login
FR01-01 System shall allow user to login
FR01-02 System shall get Username from user
FR01-03 System shall get password from user
FR01-04 System shall authenticate user when he / she submits username and
password on login button
FR01-05 System shall allow user to remember his username and password.

FR02: Manage staff Profile

FR02-01 System shall allow user to change current teaching staff profile present in
college.
FR02-02 System shall allow user to change personal information by entering the
CNIC no in the text box.
 FR02-03 The system shall allow the user to add/update all the information in
different text boxes.
FR02-04 The system shall allow the user to upload his picture upto size of 20KB by
clicking on a browse button.
FR02-05 The system shall allow the user to save all the changes by clicking on
save button.
FR02-06 The system shall allow the user to cancel the changes by clicking on
cancel button.

FR03: User can use the switch board

FR03-01 System shall display menu on switchboard.

FR03-02 System shall allow user to switch to different interfaces website.

FR03-03 System shall allow power user to update the menu on switchboard

FR03-04 System shall enable user to edit any information in any web part

FR04: Manage the Notice Board

FR04-01 System shall display information on noticeboard. And also shall allow
user to configure noticeboard.
FR04-02 System shall allow user to add his/her information on noticeboard
FR04-03 System shall allow user to change/update notices on noticeboard.

FR04-04 System shall allow user to delete any information from noticeboard.

FR05: Can view the institutes

FR05-01 System shall allow the user to view institutes through switchboard.

FR05-02 System shall allow user to select his/her particular district given in the list
box.
FR05-03 System shall allow user to select his/her particular college.
FR05-04 System shall allow user to update the information of particular college.
FR06: Manage the Vacancy Position
FR06-01 System shall allow user to view the sanctioned posts of all gazzetted staff
in the colleges.
FR06-02 System shall allow user to view the contractee and regular posts of
college.
FR06-03 System shall allow user to edit the vacancy position of college.
FR06-04 System shall allow user to save the updated vacancy position by clicking
on update button.

FR07: Add/Edit the staff statement

FR07-01 System shall allow user to view staff statement.

FR07-02 System shall allow user to add new teacher record in college.

FR07-03 System shall allow user to delete existing teacher record from college.
FR07-04 System shall allow user to modify the information of particular teacher.

FR07-05 System shall allow user to add the pending teacher information
transferred from other college.

FR08: User Logout the system

FR08-01 System shall allow user to logout

FR08-02 System shall provide option in switch board to logout

FR08-03 System shall prompt user to sure for logout
FR08-04 System shall display logout acknowledge to user.

1.1 NFR01: Performance

NFR01-01 The Average load time of the starting page of the system must be less
than 5 seconds.
 NFR01-03 System Mean Time to Failure should not be more than 30 seconds
within 24 hours of use.

NFR01-03 Average system response time should not be greater than 5 seconds.

NFR01-04 System must successfully run on a client machine with 256 MB RAM or
above.

NFR01-06 Multiple authorized user may access the site without losing response
rate

NFR01-07 System shall be able to handle multiple requests over the Internet of
100 users at the maximum

1.2 NFR02: Security

NFR02-01 System must provide access to authorized users only that enter through
the login module.

NFR02-02 System must not provide access to ANY user EXCEPT the designated
user to update the database.

NFR02-03 A user must allowed to see her/his prevl any other users overall business
transactions.

NFR02-04 After the end of a user Session, no information must be saved any where
on the client machine.

All access to the system shall be logged

NFR02-05

A proper mechanism shall be adopted in order to avoid any hacker’s

NFR02-06
attacks on the application.
1.3 NFR03: Availability

This web based application shall be available 24 hours a day.

NFR03-01

User may access it from any part of the world

NFR03-02

1.4 NFR04: Documentation

NFR04-01 User Documentation must be done giving details of all the functionalities.
.

NFR04-02 Online help should be available in case of any problem..

NFR04- Help documentation must be complete in providing information about each

01 and every module and functionality provided by the system.

NFR04- Help option must be easily accessible on all system web pages.
02

NFR04- Help must be written using minimal technical terms; any technical terms
03 used must be additionally defined at the end of the document

1.5 NFR05: Disaster Recovery

NFR05-01 This should be made sure that a proper recovery system exists in case
of any disaster.

NFR05-02 In case of client /server crash all information/data should be recoverable

within 30 minutes of the incidence.

1.6 NFR06: Usability

NFR06-01 The system should be easy to use for a novice user.

 NFR06-02 Time to learn overall interface of the system should be minimal.

1.7 NFR03: Defects-Maintenance

NFR03- Post Release defects of the system must not exceed 1 critical bug per
01 month.

NFR03- Post Release bug fixing should not take more than 5 hours.
02

1.8 NFR04: Documentation

NFR04- Help documentation must be complete in providing information about each

01 and every module and functionality provided by the system.

NFR04- Help option must be easily accessible on all system web pages.
02

NFR04- Help must be written using minimal technical terms; any technical terms
03 used must be additionally defined at the end of the document

1.9 NFR05: Disaster Recovery

NFR05- In case of client /server crash all information/data should be recoverable
01 within 30 minutes of the incidence.

Actors:

1. MIS Incharge Higher Education Department

2. System Analyst (SA)
3. Director Colleges Punjab (DEC)
4. Principal Colleges Punjab (PC)
5. Network/Database Administrator (NDBA)
6. Data Entry Operator(DEO)