Proj-2013-2014-RobAIR-1: Difference between revisions

From air
Jump to navigation Jump to search
No edit summary
No edit summary
Line 32: Line 32:
* Recherche sur "comment faire un plugin skype"
* Recherche sur "comment faire un plugin skype"
* Première tentative pour faire fonctionner skype via java : skype doit, pour le moment être lancé avec son interface graphique pour que le code java fonctionne.
* Première tentative pour faire fonctionner skype via java : skype doit, pour le moment être lancé avec son interface graphique pour que le code java fonctionne.

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-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| TBC
| TBC
| TBC
| TBC
| TBC

|}


=1. Introduction=
==1.1 Purpose of the requirements document==
==1.2 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:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [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=

Revision as of 10:48, 27 January 2014

Introduction

Project RobAIR

Team

  • Tutors : Didier Donsez,Amr Alyafi
  • Members : Augustin Husson, Jérôme Barbier

Project objectives

  • Faire transiter des messages de commandes d'un pc vers une tablette sur le robot pour le contrôler
  • Utiliser skype comme intermédiaire pour faire transiter ces messages
  • Faire une interface graphique permettant facilement de faire bouger le robot sans passer en ligne de commande
  • Faire en sorte que skype fonctionne en tâche de fond (donc sans son ihm ) afin de l'utiliser exclusivement comme support
  • traduire la page actuel


Progress of the project

The project started January 14th, 2013.

Week 1 (January 13th - Janurary 19th)

  • Project discovery
  • Research of related projects

Week 2 (January 20th - Janurary 26th)

  • Mise au point des objectifs de l'équipe
  • Récupération d'un kit Rob-Air à monter
  • Initialisation de la phase d'assemblage de ce robot en partenariat avec l'équipe composée de David Levayer et de Paul Mariage
  • Recherche sur "comment faire un plugin skype"
  • Première tentative pour faire fonctionner skype via java : skype doit, pour le moment être lancé avec son interface graphique pour que le code java fonctionne.

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

1.1 Purpose of the requirements document

1.2 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-2013-2014-RobAIR-1&oldid=14684"