Software Requirement Specification

A Software Requirement Specification (SRS) is a requirements specification for a software

system that is a complete description of the behavior of a system to be developed. It includes a
set of use cases that describe all the interactions the users will have with the software. Use cases
are also known as functional requirements. In addition to use cases, the SRS also contains non-
functional (or supplementary) requirements. Non-functional requirements are requirements that
impose constraints
on the design or implementation (such as performance engineering requirements, quality
standards, or design constraints).

The initial specifications of user requirements may be based on interviews with the database
users and on the designers own analysis of the enterprise. The basic issues that the SRS writer(s)
shall address are the following:

Functionality:
What is the software supposed to do?
External interfaces.
How does the software interact with people, the systems hardware, other hardware, and other
software?
Performance.
What is the speed, availability, response time, recovery time of various software functions, etc.?
Attributes.
What is the portability, correctness, maintainability, security, etc. considerations?
An SRS should be:
a) Correct
b) Unambiguous
c) Complete
d) Consistent
e) Ranked for importance and/or stability
f) Verifiable
g) Modifiable
h) Traceable
Table of Contents
1. Introduction 1
1.1 Purpose 1
1.2 Scope 1
1.3 Definitions, Acronyms and Abbreviations 1
2. General Description 2
2.1 Application Perspective 2
2.2 Application Functions 2
2.3 User Characteristics3
2.4 Assumptions and Dependencies 3
3. Specific Requiremens 4
3.1 External Interface Requirements 4
3.1.1 User Interfaces4
3.1.2 Hardware Interfaces4
3.1.3 Software Interfaces4
3.1.4 Communications Interfaces4
3.2 FUNCTIONAL REQUIREMENTS 5
3.2.1 Student Registration 5
3.2.2 Student Attendance Management 5
3.2.3 Opinion Management 5
 1. Introduction
Student Attendance Management System has become important factors in modern education
field. This system will help the institutions to streamline the administrative task and provide
real-time access to the data Building this system in offline based interface will further help the
ease of accessibility through any windows. The study findings enable the definition of the
project problem statement, its objectives, scopes and advantages of the Student Attendance
Management System.

1.1 Purpose
The purpose this document is to present a detailed description of the Student Attendance
Management System. It will explain the purpose and features of the software, the interfaces
of the software, what the software will do, the constraints under which it must operates and
how the software will react to external stimuli. This document is intended for both the end
users and the developers of the software.

1.2 Scope
This document covers the requirements for the Student Attendance Management System.
This software will provide a graphical environment in which the users of the system will be
able to perform various operations that are associated with storing, marinating, updating and
retrieving Students Attendace information. The system will capture information about
Students and Professors personal details and courses. Storing, updating and retrieving in a
fast and accurate way.

1.3 Definitions, Acronyms, and Abbreviations

The Student Attendance Management System has to handle records for many number of
students and maintenance was difficult. Though it has used an information system, it was
totally manual. Hence there is a need to upgrade the system with a computer based
information system. Student Management System

2. General Description

2.1 Application Perspective

The application Student Attendance Management system, is an independent product and
does not depend on any other product or system. The product will automate various tasks
associated with handling student details and better organizing the stored information and
optimum performance, thus helping the Colleges to ensure smooth working of these
processes.

2.2 Application Functions

Our system has two types of accessing modes,
i) Administrator:
Administrator has to update and monitor the registered student details, add a new student,
provide register number for all students, assign each student a course etc., Administrator can
also add the professors details and create a separate login for him/her and assign that
particular course handled by them, and also can give help to the Professors in usage of
Student Attendance Management System
ii) User:
There are only one users login created
Professor:
Professor can get logged in, mark attendance, checkup the results of the student updated by
admin and can also inform the students about their shortage in that particular course

2.3 User Characteristics

This software gives access to two kinds of users.
1. Administrator: The personnel and College administrator will have administrator access to
add, delete and modify information stored in the database.
2. Authorized User: Professors will have access to only view the data stored in the database
and can update the students attendance in the form of formatted reports.

2.4 Assumptions and Dependencies

We assume that the Office personnel do all the data entry based and the correct
values obtained from forms and registers.
We assume that the computers that will use the software will be part of the college .
Users with administrator access should be careful in deleting or modifying any
information knowingly or unknowingly which will lead to inconsistency of the
database.

3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
GUI along with meaningful Frames and buttons
Reports are generated as per the requirement

3.1.2 Hardware Interfaces

Hardware Environment Intel Core 4th Generation

System Configuration RAM- 1 GB HDD - 80GB
Operating system Any Windows

3.1.3 Software Interfaces

Front End Visual Basic
Back End MySQL [ Oracle ]

When invalid inputs are given to the modules then the error messages will be popped up in order to
inform the user that the input provided is not taken by the database. When incomplete information is
provided by the user and the user tries to submit the form in order to store the details in the database
the system will pop up a message box asking the user to enter all the details required.

3.2 Functional Requirements

Student Attendance Management System involves the following functions

3.2.1 Student Registration:

- Details of students is been maintained and entered at the back end by Administrator
3.2.2 Student Attendance Management:
- Easily track attendance information of students.
- Quickly alerts the shortage of the attendance of particular subjects.

4. NON-FUNCTIONAL REQUIREMENTS:

The Non-Functional requirements of our project are:

4.1) Time:

This project should be completed within the stimulated time period.

4.2) Cost:

The cost involved in marketing the project should be less.

4.3) Usability:

This requirement is present, as this system will interact with the user.

4.4) Reliability:

This system must be highly robust.

4.5) Performance:

It should be fast enough to produce output.