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

From air
Jump to navigation Jump to search
Line 60: Line 60:
'''Inputs''': webcam
'''Inputs''': webcam


'''Source''': directional button, webcam
'''Source''': directional button, webcam, skype


'''Outputs''': webcam
'''Outputs''': webcam
Line 74: Line 74:
'''Non functional requirements''':
'''Non functional requirements''':


'''Pre-condition''':
'''Pre-condition''': skype must be used in the server and client


'''Post-condition''':
'''Post-condition''':


'''Side-effects''':
'''Side-effects''': latency? used a new interface and not skype interface


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

Revision as of 11:11, 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.
  • Search how skype is used to

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: receive video trafic, put it on us interface and add directional buttun for control robair remotely via skype encoding (for VoIP)

Description: use skype interface for video-conference to allow us to control robair

Inputs: webcam

Source: directional button, webcam, skype

Outputs: webcam

Destination: robair

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: skype must be used in the server and client

Post-condition:

Side-effects: latency? used a new interface and not skype interface

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