Assignement 1 (SRS)

Software Requirement Specification (SRS)
Table of Contents
1. Introduction----------------------------------------------------2
1.1 Purpose----------------------------------------------------
1.2 Scope----------------------------------------------------
1.3 Definitions----------------------------------------------------
1.4 References----------------------------------------------------
1.5 Overview----------------------------------------------------

2. Overall Requirements----------------------------------------------------
2.1 Product Perspective----------------------------------------------------
2.1.1 Hardware Interfaces. ----------------------------------------------------
2.1.2 Software Interfaces. ----------------------------------------------------
2.1.3 Communication Interfaces. ----------------------------------------------------
2.1.4 Memory Constraints. ----------------------------------------------------
2.2 User Characteristics----------------------------------------------------
2.3 Design Constraints----------------------------------------------------
2.4 Functional Requirements----------------------------------------------------
2.4.1 Non- Functional Requirements----------------------------------------------------

3. Software system attributes
3.1 Reliability------------------------------------------------------------------------------
3.2 Security--------------------------------------------------------------------------------
3.3 Availability----------------------------------------------------------------------------
3.4 Maintibilty-----------------------------------------------------------------------------
3.5 Scalability----------------------------------------------------------------------------
4. Other requirements--------------------------------------------------------------------
4.1 Assumptions--------------------------------------------------------------------------
4.2 Future Requirements. -------------------------------------------------------------







Introduction:

1.1 Purpose
The purpose of this SRS document is to completely define and explain each and every requirement/intended functionality and their inter-dependencies. The documents will help project stakeholders, users, suppliers able to understand the intended functionality of our APS Zamzama software The users and stake holders related to this project are:


Principal
Admission Clerk
Accountant Clerk
Examination Controller.


Scope:
The scope of the project (APS Zamzama software) is to automate the Admission, Examination, Accounts and Employee departments. This will include automation of all manual tasks such as student fee records, file keeping, report generation, maintaining the student progress through out the year regarding different assignments, quizzes and examinations. The benefit of automating these departments will help reduce error rate and improve performance by improving response time. The application will also help reducing time-consuming jobs. The will in turn improve the efficiency of the school management and the school itself. Management can spend more time planning and executing other managerial tasks.




Definitions:

YOU WILL WRITE BY YOURSELF. Application/software/system , record, response time, user interface, APS Zamzama,

References:

Name: IEE_Standard_For_SRS.pdf – Document ID: Std-830-1998
Name: APS Report.doc


Overview:
This SRS document contains the functional and non-functional requirements. It will also explain some of the assumptions, future requirements and some design constraints. Overall this document will help explain the requirements of the APS Zamzama software.





















Overall Description


Hardware interfaces:
q Switches, Router, Hardware Firewall
System Requirement:
q 600 MHZ Processor, 128MB RAM, 20GB, Network Card.

Software interfaces:

Name;
Specification number;

Version number
Source
Windows 2003 Server
5.2.1.4
2003
Microsoft
SQL Server 2000 for
5.2.1.4
2000
Microsoft
VB-6

6
Microsoft


Communications interfaces:

TCP/IP protocol, File Transfer Protocol , Local Area Network, IP addresses
ICMP (“Ping” To Check Network Communictions)














Functional Requirements:

v Secure login (password based)
v To store record of Students and Employees department wise.
v Display student record.
v Update all student records.
v Delete records.
v Use of buttons to provide users with functions like:
- Scroll through records
- Move to previous record
- Move to last record
- Move to first record
v Retrieve records.
v Output Records- System should be able to generate reports based on the data available in the database and selection made specifically by the users.
v Search: System shall allow the users of the system to search through records/database.
v System should provide voice messages/commands to the user’s.
v All grids used in the application shall be flex grid.
v System shall allow to store student pictures.
v Application will allow for data backup and recovery procedures.

Non-Functional Requirements:

v Maximum response time per record should not be greater than 2 seconds.
v Searching through all databases should not exceed 5 seconds.
v Should have user-friendly interface.
v The application should be delivered in 5 months



User Characteristics


Users
Expertise level
Education
Principal:

Intermediate
Post Graduate
Vice Principal
Intermediate
Post Graduate
Admission Clerk:

Beginner
Intermediate
Controller Examination:

Beginner
Intermediate
Accounting Clerk:

Beginner
Intermediate


Design Constraints:
n The application only runs on Intel Based Platforms.
n Only VB 6 shall be used to run the application.
n The application will be developed in a time span of 4 months only.
n The application cost shall not exceed Rs 50,000.
n The application will be developed using VB6 on the front end, SQL Server 2000 on backend and Microsoft Seagate Crystal Reports 8i for Outputs.





Software system attributes


Reliability Requirements:

The use of this software the user will expects good and some more relaxation because before this software they store record into the registers. And know they store record into the computer and easily save record, easily search data, delete data, update data etc.

Security Requirements:

Without user no one can open the database only those persons will enter into the database that know the password. The software is perfectly secure. The user can take the backup on daily basis or weekly basses.

Scalability Requirements:

Scalability is building an infrastructure that supports both vertical growth (increase in the number of sales for a specific product) as well as horizontal growth (increase in breadth of product).
The infrastructure must be flexible enough to support growth in network size, transaction handling, data throughput and security. This requires sophisticated tools that can model capacity planning on the site and network.

Maintainability Requirements:

Every one to three months (sometimes sooner), new features are offered in new product iterations. Many of these iterations are developed in parallel with each other. The work products, from the requirements to the code, must be easily maintained in order to keep to this rigorous schedule. Conforming to standards defined by the organization (and by international standards organizations) facilitates the making of products that are easily updated and maintained through each iteration.

Usability Requirements:

The use of this software is so easy, there is no complicated things that user cannot understand. And also the documents are given to the user.



























Other Requirements

Assumptions:
- The management will provide with desktops to the entire user of this software.
- The hardware should be able to support 32-bit applications.
- All systems will be able to run Windows XP/98.
- All systems shall be having a network adapter card installed.
- Operating environment shall allow systems to work on optimum.

Future Requirements:

--Create a web-based application of APS Zamzama software.
-- Create a flash intro of the application.
-- Upgrade Database to SQL Server 2005.