RICM4 2017 2018 - OpenCity/ SRS

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

Document History

	Version	Date	Authors	Description	Validator	Validator Date
	0.1.0	05/02/2018	Quentin F.	Adding the template + Writing part.1 and 2

1. Introduction

1.1 Purpose of the requirements document

• Bootstrap documentation
• D3js documentation

1.2 Scope of the product

With this specific project, the interested area is limited to the department, here the Isère (38). But the entire world can have access to the data.

1.3 Definitions, acronyms and abbreviations

In French :

• AssMat : Assistante Maternelle

• EAJE : Equipement d'accueil du jeune enfant

• PAJE : Prestation d'accueil du jeune enfant

• AEEH : L'allocation d'éducation de l'enfant handicapé

• AM : Allocation Mensuelle

• SU : Secours d’Urgence

• École 1er Degré : Ecole primaire (école maternelle + école élémentaire)

1.4 References

Start from scratch.

1.5 Overview of the remainder of the document

None at the moment.

2. General description

2.1 Product perspective

The department will be able to modify and update the data, so all the data visualisation need to be dynamic.

2.2 Product functions

Our product is a responsive website of data visualisation of Isère’s social data. The client has a narrative experience in the website, it is a important point to permit to everyone to understand the high quantity of information.

2.3 User characteristics

Two possibilities :

• If it is an individual, it can see all the data and navigate browse the website.
• If it is a department member, it can modify data through a special interface.

2.4 General constraints

The most important point is that everyone could easily and quickly understand the high quantity of data. A special attention is given to the narrative aspect to allow the client to be in immersion

2.5 Assumptions and dependencies

• Isère’s social data

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:

6. Index

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.