Академический Документы
Профессиональный Документы
Культура Документы
Specification
for
Sports Management
SLTIET
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 main moto behind this project is to provide the students, participants and faculties a simple and
secure interface to registration, issuereturn kit and much more and reduce burden from the people
working.
1.2 Document Conventions
Every requirement specification statements are having their own same level priority and not any
external or distinguished priority set for any requirements.
1.3 Intended Audience and Reading Suggestions
This document is for developers, project managers, marketing staff, students, teachers, testers and
documentation writer of the SLTIET and project team.
The reading sequence of this document is starting from introduction to overall description of the
project, external interfaces and system functionalities and at last the revision history.
1.4 Product Scope
This product is built to provide easy interaction to students and sports teacher with the existing
system. They can easily register, issuereturn kit, game rules, schedule, notifications, results of the
game and much more other things.
1.5 References
We got the idea of registration because we face lots of difficulties and delays during register our self
for the game, we thought of registration in Khelmahakumbh and got the idea of notification,
schedule and results from the web apps like crickbuzz.
2. Overall Description
2.1 Product Perspective
The system surely gone be updated after release. Since data are continuously updating and data
cleaning is also required for memory efficiency. It provides interface for admin and student both but
with different functionalities. Admin users are allowed to do much more important things compare
Software Requirements Specification for <Project> Page 2
to student users. Basically the product is established in the form of website furthermore it may
extend to android and iOS application as user increases.
2.2 Product Functions
Registration
Issue kit
Return kit
Schedule
Notification
Data of available kit
Remotely access of all the functionalities provided by the institute for sports.
2.3 User Classes and Characteristics
Students
Sports teachers
Coaches
Teachers
Administrators
2.4 Operating Environment
The product can be run on any operating system. It requires internet connection and a browser to
run the site and stay updated with the current situation of the database.
2.5 Design and Implementation Constraints
The product needs to be completed within the 3 to 4 months. The technologies that are used to build
the product is HTML, CSS, JavaScript, SQL, Java and JSP. The developer team has used tools like
NetBeans, Sublime Text, Xampp, Dreamweaver. Simple local database with SQL and Xampp is
used for the demonstration.
2.6 User Documentation
User will be provided how to use? help? Contact Us, features to solve any quires regarding the
product. They have also been given feedback form to suggest and to make complains if any.
2.7 Assumptions and Dependencies
We assume to give online payment option but it surely not gone be included in the first version and
it also little bit unsecure since it can be possible using third party softwares like paytm, net banking,
upi etc.
Software Requirements Specification for <Project> Page 3
3. External Interface Requirements
3.1 User Interfaces
Student
Login page with submit button
After successful login there will be homepage with
Notification
Navigation Links
About Us
Contact Us
Site map
Kit issue and return request
Admin
Login page with submit button
After successful login there will be homepage with
Add notification
Open Registration for event
Accept kit issue and return request
CRUD operation on database
3.2 Hardware Interfaces
For hardware interface few things are required which are any device like computer or mobile phone
from the user and admin side to complete the process and server on the admin side to store and
retrieve the data.
3.3 Software Interfaces
Software interface include interaction and passing of data between database tables for the process of
registration, issue and return kit and many other things.
For example, for the registration the registration page will make request to the database to display
the player’s details and for kit issue or return requested page will be provided available kit data.
3.4 Communications Interfaces
4. System Features
The major feature provided by the system is registration and issuereturn kits.
4.1 Registration
4.1.1 Description and Priority
This feature has the highest priority as it is one of the main purpose of the product.
4.1.2 Stimulus/Response Sequences
Students have to login to the page and whenever an event will have organized than if they
want to register their shelf for it than they just need to make few clicks on the links. As the
data of that student is already been stored in the database so that will be linked to the
requested result and remaining things will be done by the system.
4.1.3 Functional Requirements
Functional requirement for the product is that users’ data has must be store in the database
and he/she is allowed by the admins to access the functionalities.
4.2 Kit issuereturn
4.2.1 Description and Priority
This feature also has the same priority as the previous one.
4.1.2 Stimulus/Response Sequences
Students can easily get the idea about the available kits and easy process to issue and return
kit. For issue kit student needs to request for the kit which will be approved by the admin and
then that kit will be attached with that student and if the kit will not be return on time than
charges will be applied and on safely return of the kit they simple request for the return kit
and then again it is accepted by the admin and from the database the kit will release from that
student and available kit data table will get update.
4.1.3 Functional Requirements
To use these feature, the user required the enrolment number allocated to them and available
kits.
Software Requirements Specification for <Project> Page 5
5. Other Nonfunctional Requirements
5.1 Performance Requirements
For the best performance the high speed connection and upgraded system and browsers are required
for the best and fast user interface.
5.2 Safety Requirements
For the shake of safety back up devices are required to save the data if server get crash or any other
harming things happened on server.
5.3 Security Requirements
For the shake of security, the users and admins are suggested to not to share their personal details
like passwords and user ids with others and not to use any third party tools to access the site.
5.4 Software Quality Attributes
The additional attributes in the product is as follow:
Schedule
Game Results
Notifications
Gallery
Winners of previous event
Upcoming events
5.5 Business Rules
Features like registration, schedule and notification are only for particular time when the event is
running after the completion of event such features are not accessible any more.
6. Other Requirements
The other requirement which is the most required thing is providing a domain and the server to the
product to run. Addition to this the details of all the people which directly or indirectly connect with
the product and institute is required.
Software Requirements Specification for <Project> Page 6
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>
Appendix B: Analysis Models
<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams,
state-transition diagrams, or entity-relationship diagrams.>
Appendix C: To Be Determined List
<Collect a numbered list of the TBD (to be determined) references that remain in the SRS so they
can be tracked to closure.>