System Requirements Specification for Bracketed

1. INTRODUCTION
1.1 Purpose

This SRS is prepared to evolve as the development of the software product processes. The
purpose of this document is to give description about the system, its requirements with respect
to consumers. The proposed system will be used to provide a detailed overview of the product,
its parameters and goals. It defines how our client, team and companies see the products and
its functionalities. It also assists the SDLC Model.

1.2 Document Conventions

This document is formed using IEEE template for System Requirement Specifications (SRS)
documents. Headings are in bold capital letters and wherever necessary, diagrams are
provided.

1.3 Product Scope

This System will be a Member Directory for the students, company and Training and Placement
Officer (Admin). This system will be designed to maximize the productivity by providing tools to
assist in automating the student feedback, teacher feedback and information processing which
would otherwise have to be performed manually.

More specifically, the system would store all the academic as well as personal details of the
students who wish to be part of the system. The details maybe deleted or modified to keep the
information up to date. Also, notifications would be sent to the student for academic purpose.

1.4 Product Functions

● The student will register himself/herself and will have a unique identity.
● Students can update their profiles and add details to their profiles to make it unique.
● Teacher can publish the results on the site and students can view them.
● Students get a notification about the schedule of tests and interviews.

1
2. Overall Description
2.1 Product Perspective

The proposed system shall be developed using pooled System Architecture and will be
compatible with android sdk version 19 and above. This is a self-centered product and its data
is restricted to its users and secured.

2.3. User Classes and Characteristics

1. Student

● New student has to sign up or register using complete details.

2. Administrator

● The Admin has the power to view student profile.

● Admin can notify the students regarding any change in procedures or selection process.

2.4 Operating Environment

Operating System: Android Sdk Version 19 and above

Database: SQLite

2.5 Design and Implementation Constraints

1. Application Functionality- The application through which the students take the services
should be well-functioning, error-free and easy to understand.

2. Time- No time lag to be witnessed during the service.

3. Management of a huge database

4. Security and Safety

5. Internet Connectivity

6. Large data storage capacity

7. Considerable RAM size for smooth working

8. Maintenance and timely updating.

9. Credible analysis of students’ feedback

2
3. EXTERNAL INTERFACE REQUIREMENTS
3.1 User Interfaces

● Login- To allow the users to view his details and updates his profile.
3.2 Hardware Interface

 Device should be enabled with internet.

3.3 Software Interface

● The project supports all types of android versions.

● All the student details are highly secured and privacy is maintained.

4. SYSTEM FEATURES
4.1 Login

Following credentials will be asked-

For users:

● Email ID
● Password

For Admin:

● Email ID
● Password

4.2 Register

For Students: Students need to upload the following details-

● Academic Results
● Age
● Gender
● Email ID
● Contact Number
● Branch
● Responsibilities undertaken

4.3 Updating

Students can update their profile.

3
5. OTHER NON-FUNCTIONAL REQUIREMENTS
5.1 Performance Requirements

-The software should be able to support at least three simultaneous users.

-Data should be backed up.

-System should be operable 24×7 and accessible in real time.

5.2 Security Requirements

-System will secure databases.

-No editing or modification of anything except personal information.

-Separate account for admin.

5.4 Software Quality Attributes

-Availability: Checking that the system has always something to function and generates a pop-
up error message in case of component failure.

-Usability: Checking that the system is easy to handle and navigates in the most expected ways
with no delays.

-Functionality: Checking that the system provides the right tools for editing questions
databases, creating session tests and analyzing them.

5.5 Business Rules

-The software is college specific and no other organization can use it without legal proceedings.

-All the users enrolled and facilities registered are necessarily from the host college only.