Difference between revisions of "Proj-2013-2014-flying-3Dscan"

From air
Jump to navigation Jump to search
Line 54: Line 54:
 
* emergent system properties and quality characteristics.
 
* emergent system properties and quality characteristics.
 
==Requirement X.Y.Z (in Structured Natural Language)==
 
==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=
 
=Product evolution=

Revision as of 08:10, 9 April 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

Generate a 3-dimensional model of a building by automatically taking 2-dimensional photos around this building through a camera integrated in a programmed smartphone installed on a drone.

Documents

Team

  • Tutors : Didier Donsez
  • Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng

General description

Ce projet comporte deux parties principalement : point serveur et point terminal.

Point Caméra ne sert à

  • Prendre les photos en appelant la fonction de Photo sur le téléphone mobile en suivant les exigences programmées.
  • Sauvegarder les photos prises sous un répertoire exclusif : /Cranberries/photo.
  • Dès que connecté au serveur, point Caméra se lance automatiquement et se communique avec le serveur en transmettant les photos au serveur (discussion en cours).

..

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)

Product evolution

Progress

Week 0 (Jan 13th - Jan 19th)

Week 1 (Jan 20th - Jan 26th)

Week 2 (Jan 27th - Feb 2nd)

Appendices

Index