Proj-2015-2016-Extensions IPOPO/SRS: Difference between revisions

From air
Jump to navigation Jump to search
(Created page with " {|class="wikitable alternance" |+ Document History |- | !scope="col"| Version !scope="col"| Date !scope="col"| Authors !scope="col"| Description !scope="col"| Validat...")
 
Line 26: Line 26:
In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.
In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.


==1.2 Scope of the product==
==Scope of the product==

==1.3 Definitions, acronyms and abbreviations==
==1.3 Definitions, acronyms and abbreviations==
==1.4 References==
==1.4 References==

Revision as of 14:12, 18 January 2016

Document History
Version Date Authors Description Validator Validation Date
0.1.0 January 18, 2016 Marwan HALLAL, Rémi GATTAZ, Abdelaziz FOUNAS IPOPO description TBC TBC


1. Introduction

1.1 Purpose of the requirements document

This Software Requirements Specification (SRS) identifies the requirements for project StartAir Safe. In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.

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

5.1. SRS structure

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

References:

6. Index

Retrieved from "https://air.imag.fr/index.php?title=Proj-2015-2016-Extensions_IPOPO/SRS&oldid=25835"