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

From air
Jump to navigation Jump to search
Line 50: Line 50:
   
 
==1. Introduction==
  
==1. Introduction==
−
====1.1 Purpose of the requirements document====
 +
==== Purpose of the requirements document====
−
====1.2 Scope of the product====
 +
==== Scope of the product====
−
====1.3 Definitions, acronyms and abbreviations====
 +
==== Definitions, acronyms and abbreviations====
−
====1.4 References====
 +
==== References====
−
====1.5 Overview of the remainder of the document====
 +
==== Overview of the remainder of the document====
 
==2. General description==
  
==2. General description==
−
====2.1 Product perspective====
 +
==== Product perspective====
−
====2.2 Product functions====
 +
==== Product functions====
−
====2.3 User characteristics====
 +
==== User characteristics====
−
====2.4 General constraints====
 +
==== General constraints====
−
====2.5 Assumptions and dependencies====
 +
==== Assumptions and dependencies====
 
==3.Specific requirements, covering functional, non-functional and interface requirements==
  
==3.Specific requirements, covering functional, non-functional and interface requirements==
 
* document external interfaces,
  
* document external interfaces,

Revision as of 12:55, 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


1. Introduction

Purpose of the requirements document

Scope of the product

Definitions, acronyms and abbreviations

References

Overview of the remainder of the document

2. General description

Product perspective

Product functions

User characteristics

General constraints

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

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=14698"