Software Requirements Specification for <Project>

This document is a software requirements specification for an application that supports the concept of physical and mental time travel to help students build a better future. It includes the purpose of the application, document conventions, intended audience, product scope, and references.

Software Requirements
Specification
for
<Project>
Version 1.0 approved
Prepared by <author>
<organization>
<date created>
Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Software Requirements Specification for <Project> Page ii
Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References.......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary...................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List...........................................................................................6
Revision History
Name Date Reason For Changes Version

Software Requirements Specification for <Project> Page 1
1. Introduction
1.1 Purpose
The purpose of the report is to design an application that supports the concept of the physical as
well as mental time travel. The objective of the application is to help the students to build a career
so that they can have a better future. The organization named Kids At Hope wants to design an
website application that will help the students build up their careers from small age itself.
1.2 Document Conventions
The document for SRS has highlighted headings that shows the title of the each section. The
heading are made bold with a numbering format that states different sections under a particular
heading. These particular categories helps the user to have a detailed learning of developing the
website application for Kids At Hope organization.
1.3 Intended Audience and Reading Suggestions
The readers of this document will be all the stakeholders associated with this project. The readers
will include project manager, the project scheduler, the project planner, communication manager,
executing manager and the project sponsors.
The next part of this SRS document has the overall description of the application, which consists of
the product perspective, product functions, the user classes and the characteristics of the
application, there is external Interface Requirements, the features that the system has and all other
non-functional requirements related with the application.
1.4 Product Scope
The main purpose of the application of Kids At Hope is to provide the students of age 7 to 10 years
the concept mental time travel and physical time travel. The main motive of this particular
application is to provide the students to have a better future. This innovative idea of time traveler
helps to excel as well as operates the kids to all the arts of the world. This application will help the
students to know the concept of time traveler.
1.5 References
Abbott, K. and Jannik, T., 2016. SRS environmental air surveillance program 1954-2015: General
trends (No. SRNL-STI--2016-00437). Savannah River Site (SRS).
Ali, S.W., Ahmed, Q.A. and Shafi, I., 2018, February. Process to enhance the quality of software
requirement specification document. In 2018 International Conference on Engineering and
Emerging Technologies (ICEET) (pp. 1-7). IEEE.
Bahill, A.T. and Madni, A.M., 2017. Discovering system requirements. In Tradeoff Decisions in
System Design (pp. 373-457). Springer, Cham.
Dinsmoor, C., Mei, M., Wong, B., Agrawal, A. and Levene, G., 2016. Software Requirements
Specification (SRS) Lane Management System 2.

Software Requirements Specification for <Project> Page 2
Jindal, R., Malhotra, R. and Jain, A., 2016, September. Automated classification of security
requirements. In 2016 International Conference on Advances in Computing, Communications and
Informatics (ICACCI) (pp. 2027-2033). IEEE.
Laplante, P.A., 2017. Requirements engineering for software and systems. Auerbach Publications.
Musgrove, T.A. and Walsh, R.H., TextDigger Inc, 2016. System and method for searching for a
query. U.S. Patent 9,400,838.
Pigin, V., NL SYSTEMS LLC, 2015. Method and system for digital rights management of
documents. U.S. Patent 9,003,548.
Saikia, L.P. and Singh, S., 2018, March. Feature extraction and performance measure of
requirement engineering (RE) document using text classification technique. In 2018 4th
International Conference on Recent Advances in Information Technology (RAIT) (pp. 1-6). IEEE.
Smith, S., Jegatheesan, T. and Kelly, D., 2016, November. Advantages, disadvantages and
misunderstandings about document driven design for scientific software. In 2016 Fourth
International Workshop on Software Engineering for High Performance Computing in
Computational Science and Engineering (SE-HPCCSE) (pp. 41-48). IEEE.
2. Overall Description
2.1 Product Perspective
The application that is being developed in this report is developing an application that can be used
for getting the future career of the students. The students are to enter their name and their grade in
the system so that the system will get to know about their future. This application that is being
developed replaces the concept of developing the travel time application that will determine the
future of the students.
2.2 Product Functions
The product functions to take the details of the student that is their name and the grade in which
they study. The system takes the input of the student’s skills and talents to determine the future of
the students. They will also have to include the place where they want to live, the place they wants
to live in, the hobbies they have, the education that want to pursue and the community and the
service they like to serve.
2.3 User Classes and Characteristics
The user classes for developing this particular application includes student class, and administrator
class. The student class has the characteristics to input their name and grade in the system. the
administrator also has to login in the system so that they can view the details of the students who
are involved in the system.

Software Requirements Specification for <Project> Page 3
3. External Interface Requirements
3.1 User Interfaces

Software Requirements Specification for <Project> Page 4

Software Requirements Specification for <Project> Page 5

Software Requirements Specification for <Project> Page 6
3.2 Hardware Interfaces
The logical properties that are included in the application system are:
 Understanding the protocol of the system.
 All the IP address and the interfaces should be associated with the interface.
 There should be a firewall that should be included while the application is run on a system.
The physical properties that are included in the application system are:
 Physical properties should include the Bit Error Rate that helps to specify the total number
of the bit errors in particular BERT (Bit Error Rate Test)
 BERT time should be included in which the bit error should be sampled.
3.3 Software Interfaces
The software interface of the application system includes the name of the student and the class of
the student in which he reads.
There are many other data items that are entered in the system. Those are the data rated to interest
of the student, the student has to select the skills and the talents they have so that the system can
evaluate their future.
They are also to select the place where they want to live, select the education and career, select their
community and career, and finally selects the hobbies they like to.

Software Requirements Specification for <Project> Page 7
3.4 Communications Interfaces
The communication is mainly done by email in this application. The students are to select their
respective interest and skills and according to that the system will generate their future and to keep
a copy of that the system sends an email to the system so that the students can keep a copy of that in
their mail.
The communication standards that are followed in this system is digital communication system and
the operations are done on the standards of the industry. The standards includes the syntax, the
synchronization and the semantics for the digital communications and this can be implemented in
software as well as the hardware of the system.
4. System Features
4.1 Takes Details from the Student
4.1.1 Description and Priority
The system in the home page takes details of the student so that they can proceed with the
time travel for their betterment in future. The system needs to know some basic details about
the student so that they can help the students with their future.
This has the highest priority as the system without taking details of the user cannot proceed
to time travel the student to their future. The system cannot evaluate their career.
4.1.2 Stimulus/Response Sequences
The user actions that are included in this particular system are:
 Entering the name of the student
 Entering the class of the student.
4.1.3 Functional Requirements
REQ-1: The system need to take the name of the student as an input to proceed with
the next part.
REQ-2: The system should also take the grade of the student to evaluate in which
class the student is and determine their graduate year.
4.2 Takes details of particular skills and talents from the student
4.1.1 Description and Priority
In order to evaluate the future of the student, the system needs to know about some particular
skills and talents about the student. In this system feature, the student provides the details
about their talents and skills they have.

Software Requirements Specification for <Project> Page 8
4.1.2 Stimulus/Response Sequences
The user actions that are included in this particular system are:
 Student needs to select six of the given skills and talents that the student has.
4.1.3 Functional Requirements
REQ-1: The system need to takes the details of the student’s skills and talents for
helping them in evaluation.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
The performance of the application states that the application system built for the Kids At Hope
will be able to support many concurrent users at a time (Pigin 2015). There are many students
inline and the students might accesses the online website at some time from different places. The
system should be able to support all the users at the same time. The response time of the system
being built is also to be less as because the uses should not wait for navigating from one page to
another page.
5.2 Safety Requirements
The safety requirements that are included in the system states the application system is safe to use
and all the safety measures are to be taken for developing the application system (Bahill and Madni
2017).
5.3 Security Requirements
Security involves the application system to have security within the system. The application system
should be available, reliability, and the robustness of the system. The system should also include the
exception handling and should include error tolerance within the system.
5.4 Software Quality Attributes
Quality attributes in a system can be defined in different manner (Musgrove and Walsh 2016). The
quality of the application system of Kids At Hope includes degree of excellence, may be used for
fitness purpose, so that the customer can use them efficiently, and includes the total characteristics
that are required to state the future of the student.
5.5 Business Rules
Business rules includes the structure of the business, and have a control on the influence on the
business and the behavior of the business. Business rules includes the operations that are to be
carried out, the constraints and the definition of the system that are to be applied in the organization
(Laplante 2017).

Software Requirements Specification for <Project> Page 9
6. Other Requirements
Other requirements that are to be included with the application of Kids At Hope are
implementation, interfaces, operations and packaging (Smith, Jegatheesan and Kelly 2016). The
interface of the system should be an existing one and there should be an operator who would handle
the operations.