Software Requirements Specification for <Project>

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.