RICM4 2017 2018 - Entrepreneur AUBERT COURTIAL/ SRS

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

=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 entrepreneurs can use this website to find skills according to their project.
 * The main theme is sharing skills.
 * Anyone can go on this website and share their skills.

1.3 Definitions, acronyms and abbreviations
Meteor : Framework used for this project.

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
The user can log thanks to user account and :


 * Find a skill and offer a meeting.
 * Offer his own skill.
 * Respond to other user interested in his offers.
 * Manage his account and offers.

2.3 User characteristics
Simple user who just need to know how to log, create a account, and use a website. But the website is mainly aiming at social entrepreneurs.

2.4 General constraints
The security of the website : Users must not be allowed to modify the database themselves.

2.5 Assumptions and dependencies
The website depends on the framework Meteor and the different packages installed. It also depends on bootstrap for the css.

=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 SearchBar
Function: Search Bar

Description: Allow the users to search in the skill offer list.

Inputs: Words as String

Source:

Outputs: Skill offer list that matches the words given in parameters

Destination:

Action: Search in the database using the words input, the skill offers that matches the input.

Non functional requirements:

Pre-condition: Internet connection

Post-condition: None

3.1.2 SearchBar (in Structured Natural Language)
Function: Search Bar

Description: Search in the skill offers

Inputs: Words as String

Source:

Outputs: Skill offers that matches the words given in parameters

Destination:

Action: Search in the database using the words input, the skill offers that matches the input.

=4. Product evolution=

=5. Appendices= =6. Index=