Difference between revisions of "Proj-2013-2014-RobAIR-2"

From air
Jump to navigation Jump to search
Line 49: Line 49:
   
   
−
==1. Introduction==
 +
== Introduction==
 
==== Purpose of the requirements document====
  
==== Purpose of the requirements document====
 
==== Scope of the product====
  
==== Scope of the product====
Line 55: Line 55:
 
==== References====
  
==== References====
 
==== Overview of the remainder of the document====
  
==== Overview of the remainder of the document====
−
==2. General description==
 +
== General description==
 
==== Product perspective====
  
==== Product perspective====
 
==== Product functions====
  
==== Product functions====
Line 61: Line 61:
 
==== 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 68: Line 68:
 
* 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 95: Line 95:
 
'''Side-effects''':
  
'''Side-effects''':
   
−
==4. Product evolution==
 +
== Product evolution==
   
−
==5. Appendices==
 +
== Appendices==
   
−
====5.1. SRS structure====
 +
==== SRS structure====
 
The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard.
  
The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard.
   
Line 107: Line 107:
 
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]
  
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]
   
−
==6. Index==
 +
== Index==
   
 
= Progress of the project =
  
= Progress of the project =

Revision as of 12:56, 27 January 2014

Introduction

The Robair project aims to develop a platform for robotic telepresence used for both teaching ambient intelligence and testing low cost (ie well below the price of market platforms) of service robotics in real environments. This platform aims extensible and open source (open software, open hardware, open design, open data).

More information on Project RobAIR

Team

  • Tutors : Didier Donsez, Amr Alyafi
  • Members : David Levayer, Paul Mariage

Project objectives

Not decided yet (in progress...)

Software Requirements Specification

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

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

Appendices

SRS structure

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

References:

Index

Progress of the project

The project started January 14th, 2013.

Week 1 (January 13th - Janurary 19th)

Retrieved from "https://air.imag.fr/index.php?title=Proj-2013-2014-RobAIR-2&oldid=14705"