SRS - GrenobloisFuté

From air
Revision as of 21:24, 5 April 2016 by Adrien.Delaporte (talk | contribs) (1.2 Scope of the product)
Jump to: navigation, search
Document History
Version Date Authors Description Validator Validation Date
0.1.0 January 18, 2016 Delaporte Adrien, Lucidarme Benjamin, Mouret Adrien Creation of the document TBC TBC

1. Introduction

1.1 Purpose of the requirements document

The Software Requirements Specification (SRS) is a document describing the software system of our project: GrenobloisFuté. It describes how the system is supposed to work with functional and non functional requirements.

1.2 Scope of the product

Our application is intended for all motorists Grenoble. The goal is to display the traffic and work presented in the Grenoble area to be able to adjust his path.

1.3 Definitions, acronyms and abbreviations

1.4 References


Home Page

1.5 Overview of the remainder of the document

2. General description

2.1 Product perspective

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: Amplifying sounds to enable people who have hearing problems to hear properly







Non functional requirements:




4. Product evolution

5. Appendices

6. Index