<Give Here Your Own Project Title>
Software Requirements Specification
Version 1.0
Group Id: <Mention your group id>
Supervisor Name :< Mention your supervisor name>
Revision History
Date (dd/mm/yyyy)
Current date
Version
1.0
Description
Introduction of the project
Author
Write student(s) id
Table of Contents
All the softwares are developed according to user requirements. user requirements are those functionalities that the software will provide the user (who will use this software also called as end user)
Before developing SRS document you should be clear about functional user requirements, scope, non functional requirements, business requirements, usage scenario.
Functional Requirements:
these are the requirements that tells about the functions of the developed software. Like Login, Registration, Logout etc
Non Functional Requirements:
these are the requirements that tells the functionality of system as well as how the system will operate. If functional requirements are well elaborated and fulfilled but non functional requirements are not taken under consideration then software will be rejected so both functional requirements should be fulfilled by the software system.
As Software requirement specification is the first phase of project development so in this phase all the requirements, functionalities, scope etc should be clear.
Non functional requirements can be usability, performance, userfreindliness, reliability etc
Business Requirements:
these requirements describe business objectives of developed software to an organization for example in market what will be the value of this developed system
Scope:
Software Requirements Specification
Version 1.0
Group Id: <Mention your group id>
Supervisor Name :< Mention your supervisor name>
Revision History
Date (dd/mm/yyyy)
Current date
Version
1.0
Description
Introduction of the project
Author
Write student(s) id
Table of Contents
- Scope (of the project)
- Functional Requirements Non Functional requirements
- Use Case Diagram
- Usage Scenarios
All the softwares are developed according to user requirements. user requirements are those functionalities that the software will provide the user (who will use this software also called as end user)
Before developing SRS document you should be clear about functional user requirements, scope, non functional requirements, business requirements, usage scenario.
Functional Requirements:
these are the requirements that tells about the functions of the developed software. Like Login, Registration, Logout etc
Non Functional Requirements:
these are the requirements that tells the functionality of system as well as how the system will operate. If functional requirements are well elaborated and fulfilled but non functional requirements are not taken under consideration then software will be rejected so both functional requirements should be fulfilled by the software system.
As Software requirement specification is the first phase of project development so in this phase all the requirements, functionalities, scope etc should be clear.
Non functional requirements can be usability, performance, userfreindliness, reliability etc
Business Requirements:
these requirements describe business objectives of developed software to an organization for example in market what will be the value of this developed system
Scope:
Scope gives complete concept of the developed system. It gives complete idea about the functions that the developed software will perform.
Usage Scenario :
It gives concept about interaction b/w user and the software developed. Like for Login how the system and the user will interact each other.
Usage Scenario:
Login : user will provide username and password and click on Login Button
Action : the system will check username and password If it is correct or not if it is correct then system will show message "username and password is correct" If username and password is not correct then system will show error message "username and password is not correct please login again"
If user already exists then system will show message as "user already exists please try another username"
Expectations: if the user successfully logins then homepage should appear.
Scope :
Scope can be written as
It is a web application that will allow the user to send and receive books online. user will register first to login and get access.
Functional Requirements:
Functional Requirements can be written as
Login Management
Registration Management
User Management
Account Management etc
Login Management:
This system will allow the users to login to get access to system. only registered users can be able to login and all the login management will be under administrator control.
Registration Management:
This system will allow the users to register themselves to the system. A registration page will be provided which will keep record of all the users and users will be agree on system agreement. Registration management should be under admin control
User Management
this system will keep record of all the users registered to the system. Admin should be allowed to keep this record.
Account management:
this system will allow the users to make accounts and to get registered. users can update/edit account information only Admin can delete their accounts. admin will keep all the record of developed accounts
More requirements can be added according to the software
Non Functional Requirements:
Performance:
this system will allow fast access and all the information will be accessed fastly so this system should of fast performance
Usability
This system will allow all users of average IQ to use this system effectively after a minor training
userfriendliness:
this system should be user friendly
More requirements can be added according to the software
that's y share ki hai 
ye ziadti hay waise awain hmare course may MCs ki books de di,,aur MCs walon ko aik b mba ki na di