RICM4 2017 2018 - OpenCity: Difference between revisions

From air
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
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
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}



=1. Introduction=
=1. Introduction=
Line 49: Line 20:
* Didier DONSEZ
* Didier DONSEZ
* Georges-Pierre BONNEAU
* Georges-Pierre BONNEAU

==1.1 Purpose of the requirements document==
==1.2 Scope of the product==
==1.3 Definitions, acronyms and abbreviations==
==1.4 References==
==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''':

'''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''':

=4. Product evolution=

=5. Appendices=
=6. Index=

Revision as of 09:26, 5 February 2018

1. Introduction

Présentation

Projet RICM4 - 2017/2018 - Polytech Grenoble

Objectif : Construire une solution de datavisualisation des données sociales du département de l’Isère.

Cliquer ici pour suivre notre projet via Trello.

Équipe

Étudiants :

  • Quentin FOMBARON
  • Amina BOUCHERIMA

Enseignants :

  • Didier DONSEZ
  • Georges-Pierre BONNEAU