lOMoARcPSD|23103793

PRACTICAL – 2: Develop software requirements specification for (1

a.) and (1 b.) problem.

SRS FOR COLLEGE AUTOMATION SYSTEM

 INTRODUCTION:

The title of the project is “COLLEGE MANAGEMENT SYSTEM” (CMS). CMS is an

Internet based application that aims at providing information to all the levels of management
within an organization. This system can be used as an information management system for the
college. For a given user, the administrator will create a login id & password, using this user
can access the system to either upload or download some information from the database. The
front-end will be HTML pages with Java Script for client-side validation whereas all business
logics will be in PHP reside at middle layer. And these layers will interact with third layer of
database, which will be MySQL database. The web server will be Apache. To start working on
this project environment required is a server having Apache as web server, MySQL as
database and XAMPP as development environment.

 PROJECT SCOPE AND PRODUCT FEATURES:

This software system will be a College management system for the members of an
organization. This system will be designed to maximize the administrative, academic and
overall productivity by providing tools to assist in automating the technical procedures and
processes, which would otherwise have to be performed manually. By maximizing the users

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

work efficiency and production the system will meet the users’ needs while remaining easy to
understand and use. It is a user-friendly portal to interact, manage, access the information.

 USER CLASSES AND CHARACTERISTICS:

The target audience for CMS product is the college Administrator/students/faculty/staff

(Technical/Nontechnical) .The users for this system are:

 Administrator: The Super user of the system. Mainly focuses on administrative and
academic related issues.

 Student: A user with limited access rights.

 Staff: A user of the system who has more access rights than a normal user.

Introduction
The title of the project is
COLLEGE MANAGEMENT
SYSTEM (CMS). CMS is an
Internet based application that
aims at providing information to
all the levels of management
within an organization. This
system can be used as a
information management
system for the college.

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

For a given user, the

administrator will create a
loginid & password, using this
user can access the system to
either
upload or download some
information from the database.
The front-end will be HTML
pages with Java Script for client-
side validation whereas all
business logics will be in
PHP resides at middle layer. And
these layers will interact with
third layer of database, which
will be MySQL database.
The web server will be Apache.
To start working on this project
environment required is a
server having Apache as

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

web server, MySQL as database

and XAMPP as development
environment
1.1 Purpose
The purpose of this document is
to present a detailed
description of the College
Management System. It will
explain
the purpose and features of the
system, the interfaces of the
system, what the system will
do, the constraints under
which it must operate and how
the system will react to external
stimuli. This document is
intended for both the client
and the developers of the
system and will be proposed to

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

the Administrative head for its

approval.
1.2 Project Scope and
Product Features
This software system will be a
College management system
for the members of an
organization. This system will
be
designed to maximize the
administrative, academic and
overall productivity by providing
tools to assist in automating
the technical procedures and
processes, which would
otherwise have to be performed
manually. By maximizing the
users work efficiency and
production the system will meet

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

the users’ needs while

remaining easy to understand
and use.
It is a user-friendly portal to
interact, manage, access the
information.
1.3 Intended Audience
and Document Overview
There are different types of
intended audience for this
document, such as developers,
testers, documentation writers
and
most importantly the users. We
have divided the rest of the
document into different
subsections. We suggest that
you

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

begin with understanding the

definitions, acronyms and
abbreviations, then sequentially
go through contents, overview
section and proceeding through
the detailed description
sections that is most pertinent.
1.4 Definations,
Acronyms, and
Abbreviations
CMS- College Management
System,SRS- Software
Requirement Specification, IDLE
Python,students data entry Ex-
Name, Father name, Contact
No. etc.

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

2 Overall
Description
2.1 Product Perspective
The product will be a
standalone application and may
be run on multiple systems
within an Internet network. The
product will require a keyboard,
mouse and monitor to interface
with the users. The minimum
hardware requirements
for the product are specified in
this document
2.2 User Classes and
Characteristics
The target audience for CMS
product is the college

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

Administrator/students/faculty/s
taff (Technical/Nontechnical)
.The users for this
system are
 SOFTWARE REQUIREMENT SPECIFICATIONS:
o EXTERNAL INTERFACES:
a) Hardware platform:
▪ PIII or above
▪ RAM of 512 or above MB - Hard Disk 20GB or above

b) Software Platform: Browser :

▪ Mozilla Fire-Fox v12.0 or higher
▪ Google Chrome v27.0.1453.116m or higher

o FUNCTIONAL REQUIREMENTS:
a) Login:
This section contains students’ login menu where students have to login by
their username as well as password.
b) Marksheet:
This section contains student’s stored data. Student can find their marks by
entering detail in ‘student detail’ Option, and after feeling their data he/she
may automatically get their marks in ‘grades point option’.
c) Menu:
This section includes menu’s for students’ details such as student profile,
library system, fee report and Marksheet.
d) Search Page:
Here student can search their stored data entering roll no..
e) Student Information:
Here student can store their data in database form by entering data into
‘student information’ section.

o NON FUNCTIONAL REQUIREMENTS:

a) Performance Requirements:
Performance should not be an issue because all of our server queries
involve small pieces of data-changing screens will require very little
computation and thus will occur very quickly. Server updates should only
take a few seconds as long as the phone can maintain a steady signal.
b) Reliability:

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

Must maintain data integrity. Computer crashes and misuse should not
affect a user’s history
c) Availability:
The CMS Portal shall be available, up and running for 24*7 throughout the
year except due to the routine maintenance activities.
d) Security Requirements:
Administrator and Users with valid credentials will be able to log in to
Portal. Administrator will have access to the database structures at back-
end. Administrator will have the rights for modifications as well as any
updating work for the datasets and website. Access to the various
subsystems will be protected by a user log in screen that requires a user
name and password to be updated in future.

SRS FOR BANKING MANAGEMENT SYSTEM

 INTRODUCTION:

Online banking system provides is specifically developed for internet banking for
Balance Enquiry, Funds Transfer to another account in the same bank, Request for cheque
book/change of address/stop payment of cheques, Mini statements (Viewing Monthly
and annual statements). The Traditional way of maintaining details of a user in a bank was to
enter the details and record them. Every time the user needs to perform some transactions he
has to go to bank and perform the necessary actions, which may not be so feasible all the time.
It may be a hard-hitting task for the users and the bankers too. The project gives real life
understanding of Internet banking and activities performed by various roles in the supply
chain. Here, we provide an automation for banking system through Internet. Internet banking
system project captures activities performed by different roles in real life banking
which provides enhanced techniques for maintaining the required in- formation up-to-date,
which results in efficiency. The project gives real life understanding of Internet banking
and activities performed by various roles in the supply chain.

 USER CLASSES & CHARACTERISTIC:

1) Customers:

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

The normal users will have an account of fixed or savings and should have a minimum
balance of Rs. 500. He can transfer funds to another account of the same bank & may
view his monthly or annual statements.

2) Industrialists, Entrepreneur, Organizations academicians:

These users will have all the three accounts & should have a minimum balance of
20,000 Rs. He can view the statements of his organization or industry.

 SOFTWARE INTERFACE:

1) Front End Client:

The system is a web-based application client are requiring using modern web browser
such as Mozilla Firefox 1.5, PHP.

2) Web Server:

The web application will be hosted on one of the apache servers.

3) Back End:

We use backend as MY SQL.

 OPERATING ENVIRONMENT:

1) Hard Drive : More than 160 GB.

2) RAM : More than 1 GB

3) Processor : Pentium 4 or Higher

 FUNCTIONAL REQUIREMENTS:
1) Login Process:
This module allows valid customers to access the functionalities provided by the bank.
2) Balance Enquiry:

Downloaded by Amandeep Kaur ([email protected])

 lOMoARcPSD|23103793

This module maintains the balance details of a particular account.

3) Update Profile:
This module allows the customer to update profile of their account.
4) Funds Transfer:
This module allows the customers to transfer funds from one account to another within
the same bank.
5) Password Change:
This module allows customers to change their password.
6) Mini Statements:
This module allows customers to view their transaction details.

 NON-FUNCTIONAL REQUIREMENTS:

1) Security:
The banking system must be fully accessible to only authentic user. It should require
pin for entry to a new environment.

2) Reliability:
The application should be highly reliable and it should generate all the updated
information in correct order.

3) Availability:
Any information about the account should be quickly available from any computer to
the authorized user. The previously visited customer’s data must not be cleared.

4) Maintainability:
The application should be maintainable in such a manner that if any new requirement
occurs then it should be easily incorporated in an individual module.

5) Portability:

The application should be portable on any windows based system. It should not be
machine specific.

Downloaded by Amandeep Kaur ([email protected])