Se SRS

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
2. General Description
2.1 Application Perspective
2.2 Application Functions
2.3 User Characteristics
2.4 Assumptions and Dependencies
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
3.1.3 Software Interfaces
3.1.4 Communications Interfaces
3.2 FUNCTIONAL REQUIREMENTS
3.2.1 Student Registration
3.2.2 Student Attendance Management
3.2.3 Opinion Management
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
Student’s Attendance information. The system will capture information about Student’s and
Professor’s 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 numbers 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,
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
professor’s 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
User:
There is only one user’s 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.
Administrator: The personnel and College administrator will have administrator
access to add, delete and modify information stored in the database.
Authorized User: Professors will have access to only view the data stored in the
database and can update the student’s 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.
3.3 NON-FUNCTIONAL REQUIREMENTS:
The Non-Functional requirements of our project are:
Time: This project should be completed within the stimulated time period.
Cost: The cost involved in marketing the project should be less.
Usability: This requirement is present, as this system will interact with the user.
Reliability: This system must be highly robust.
Performance: It should be fast enough to produce output.

Se SRS

Uploaded by

Copyright:

Available Formats

Se SRS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Se SRS

Uploaded by

Copyright:

Available Formats

Table of Contents

1.3 Definitions, Acronyms, and Abbreviations

2.2 Application Functions:

2.3 User Characteristics:

2.4 Assumptions and Dependencies:

3.1 External Interface Requirements

3.1.2 Hardware Interfaces

Hardware Environment Intel Core 4th Generation

3.1.3 Software Interfaces

Front End Visual Basic

3.2 Functional Requirements

3.2.1 Student Registration:

3.2.2 Student Attendance Management:

3.3 NON-FUNCTIONAL REQUIREMENTS:

The Non-Functional requirements of our project are:

You might also like