Proj-2013-2014-flying-3Dscan: Difference between revisions

From air
Jump to navigation Jump to search
No edit summary
No edit summary
Line 29: Line 29:


=Introduction=
=Introduction=
== Purpose of the requirements document==
==Purpose of the requirements document==
== Scope of the product==
==Scope of the product==
== Definitions, acronyms and abbreviations==
==Definitions, acronyms and abbreviations==
== References==
==References==
== Overview of the remainder of the document==
==Overview of the remainder of the document==
= Team =
= Team =
*Tutors : Olivier Richard
*Tutors : Olivier Richard
*Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng
*Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng
= General description=
=General description=
== Product perspective==
==Product perspective==
== Product functions==
==Product functions==
== User characteristics==
==User characteristics==
==General constraints==
==General constraints==
==Assumptions and dependencies==
==Assumptions and dependencies==
=3.Specific requirements, covering functional, non-functional and interface requirements=
=Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* document external interfaces,
* describe system functionality and performance
* describe system functionality and performance
Line 50: Line 50:
* emergent system properties and quality characteristics.
* emergent system properties and quality characteristics.


==3.1 Requirement X.Y.Z (in Structured Natural Language)==
==Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':
'''Function''':


Line 77: Line 77:
'''Side-effects''':
'''Side-effects''':


=4. Product evolution=
=Product evolution=
=Progress=

==Week 0==
=5. Appendices=
=6. Index=
==Week 1==
=Appendices=
=Index=

Revision as of 11:38, 27 January 2014

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


Read first:


Document History
Version Date Authors Description Validator Validation Date
0.1.0 TBC TBC TBC TBC TBC


Introduction

Purpose of the requirements document

Scope of the product

Definitions, acronyms and abbreviations

References

Overview of the remainder of the document

Team

  • Tutors : Olivier Richard
  • Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng

General description

Product perspective

Product functions

User characteristics

General constraints

Assumptions and dependencies

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.

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:

Product evolution

Progress

Week 0

Week 1

Appendices

Index