RICM4 2017 2018 - Entrepreneur AUBERT COURTIAL/ SRS
Revision as of 13:30, 5 February 2018 by Julien.Courtial (talk | contribs) (→2.1 Product perspective)
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
Read first:
- http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
- http://en.wikipedia.org/wiki/Software_requirements_specification
- IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998
| Version | Date | Authors | Description | Validator | Validation Date | |
|---|---|---|---|---|---|---|
| 0.1.0 | TBC | TBC | TBC | TBC | TBC |
1. Introduction
1.1 Purpose of the requirements document
This Software Requirements Specification (SRS) identifies the requirements for the Entrepreneur project. The purpose of the present document is to explain how we organize our project, the different steps of the conception and the project achievement.
1.2 Scope of the product
- The purpose of this project is to create a website for an association.
- Social entrepreneur can use this website to find skills according of his project.
- The main theme is sharing skills.
- Anyone can went on this website and share their skill(s).
1.3 Definitions, acronyms and abbreviations
Meteor Framework used for this project.
1.4 References
1.5 Overview of the remainder of the document
2. General description
2.1 Product perspective
This project is a website targeting social entrepreneurs to share skills with each other.
The website will be created with the framework Meteor.
2.2 Product functions
2.3 User characteristics
2.4 General constraints
2.5 Assumptions and dependencies
3.Specific requirements, covering functional, non-functional and interface requirements
- document external interfaces,
- describe system functionality and performance
- specify logical database requirements,
- design constraints,
- emergent system properties and quality characteristics.
3.1 Requirement X.Y.Z (in Structured Natural Language)
Function:
Description:
Inputs:
Source:
Outputs:
Destination:
Action:
- Natural language sentences (with MUST, MAY, SHALL)
- Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
- Mathematical Notations
- Tabular notations for several (condition --> action) tuples
Non functional requirements:
Pre-condition:
Post-condition:
Side-effects: