https://air.imag.fr/api.php?action=feedcontributions&feedformat=atom&user=Adrian.Houbron
air - User contributions [en]
2026-06-11T03:03:08Z
User contributions
MediaWiki 1.39.17
https://air.imag.fr/index.php?title=RICM4_2017_2018_-_ESP32_D/_SRS&diff=38970
RICM4 2017 2018 - ESP32 D/ SRS
2018-02-05T09:39:27Z
<p>Adrian.Houbron: Created page with "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-an..."</p>
<hr />
<div>The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.<br />
<br />
<br />
'''Read first:'''<br />
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx<br />
* http://en.wikipedia.org/wiki/Software_requirements_specification<br />
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]<br />
<br />
{|class="wikitable alternance"<br />
|+ Document History<br />
|-<br />
|<br />
!scope="col"| Version<br />
!scope="col"| Date<br />
!scope="col"| Authors<br />
!scope="col"| Description<br />
!scope="col"| Validator<br />
!scope="col"| Validation Date<br />
|-<br />
!scope="row" |<br />
| 0.1.0<br />
| TBC<br />
| TBC<br />
| TBC<br />
| TBC<br />
| TBC<br />
<br />
|}<br />
<br />
<br />
=1. Introduction=<br />
==1.1 Purpose of the requirements document==<br />
==1.2 Scope of the product==<br />
==1.3 Definitions, acronyms and abbreviations==<br />
==1.4 References==<br />
==1.5 Overview of the remainder of the document==<br />
=2. General description=<br />
==2.1 Product perspective==<br />
==2.2 Product functions==<br />
==2.3 User characteristics==<br />
==2.4 General constraints==<br />
==2.5 Assumptions and dependencies==<br />
=3.Specific requirements, covering functional, non-functional and interface requirements=<br />
* document external interfaces,<br />
* describe system functionality and performance<br />
* specify logical database requirements,<br />
* design constraints,<br />
* emergent system properties and quality characteristics.<br />
<br />
==3.1 Requirement X.Y.Z (in Structured Natural Language)==<br />
'''Function''':<br />
<br />
'''Description''':<br />
<br />
'''Inputs''':<br />
<br />
'''Source''':<br />
<br />
'''Outputs''':<br />
<br />
'''Destination''':<br />
<br />
'''Action''':<br />
* Natural language sentences (with MUST, MAY, SHALL)<br />
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)<br />
* Mathematical Notations<br />
* Tabular notations for several (condition --> action) tuples<br />
<br />
'''Non functional requirements''':<br />
<br />
'''Pre-condition''':<br />
<br />
'''Post-condition''':<br />
<br />
'''Side-effects''':<br />
<br />
=4. Product evolution=<br />
<br />
=5. Appendices=<br />
=6. Index=</div>
Adrian.Houbron