Proj-2013-2014-flying-3Dscan: Difference between revisions

From air
Jump to navigation Jump to search
No edit summary
 
(27 intermediate revisions by the same user not shown)
Line 3: Line 3:


'''Read first:'''
'''Read first:'''
* http://air.imag.fr/index.php/Scanner_3D_volant_de_batiments
* http://。。。




Line 29: Line 29:


=Introduction=
=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.
==Purpose of the requirements document==

==Scope of the product==
=Rendu=
==Definitions, acronyms and abbreviations==
* [[Media:Proj-2013-2014-Scanner 3D volant de batiments.pdf|Presentation]]
==References==
* [[Media:Proj-2013-2014-Scanner 3D volant de batiments rapport.pdf|Rapport]]
==Overview of the remainder of the document==


* [[Proj-2013-2014-Scanner 3D volant de batiments/SRS|Software Requirements Specification (SRS)]]
* [[Proj-2013-2014-Scanner 3D volant de batiments/UML|UML Diagrams]]

= Team =
= Team =
*Tutors : Didier Donsez
*Tutors : Didier Donsez
*Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng
*Members : GUO Kai , SUN Xuan , ZHANG Zhengmeng
=General description=
=General description=
Ce projet comporte deux parties principalement : point serveur et point terminal.
==Product perspective==
==Point Caméra ne sert à==
==Product functions==
*Prendre les photos en appelant la fonction de Photo sur le téléphone mobile en suivant les exigences programmées.
==User characteristics==
*Sauvegarder les photos prises sous un répertoire exclusif : /Cranberries/photo.
==General constraints==
*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).
==Assumptions and dependencies==

==..==

=Specific requirements, covering functional, non-functional and interface requirements=
=Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* document external interfaces,
Line 49: Line 57:
* design constraints,
* design constraints,
* emergent system properties and quality characteristics.
* emergent system properties and quality characteristics.
⚫
==Requirement (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=

Latest revision as of 11:17, 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.

Rendu


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 (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

Retrieved from "https://air.imag.fr/index.php?title=Proj-2013-2014-flying-3Dscan&oldid=17052"