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

From air
Jump to navigation Jump to search
Line 1: Line 1:
  +
The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.
= Introduction =
 
   
The StartAir-Safe project aims to develop an immersive life-size ULM flight simulator for the non-profit association Start Air. One goal is to learn to people with disabilities how to fly.
 
   
  +
'''Read first:'''
More information on [[StartAIR]]
 
  +
* 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"
=Documents=
 
  +
|+ Document History
* [[Proj-2013-2014-StartAIR/SRS|Software Requirements Specification (SRS)]]
 
  +
|-
* [[Proj-2013-2014-StartAIR/UML|UML Diagrams]]
 
  +
|
  +
!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
   
  +
|}
= Team =
 
   
*Tutors : Fabrice Dubost
 
   
  +
=1. Introduction=
*Members : Corentin Ricou, William Bobo
 
  +
==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)==
*Departement : [http://www.polytech-grenoble.fr/ricm.html RICM 4], [[Polytech Grenoble]]
 
  +
'''Function''':
   
  +
'''Description''':
= Project objectives =
 
   
  +
'''Inputs''':
The main objectif is to provide a software based on SimConnect technology able to display FSX on a multi/computer/screen system.
 
   
  +
'''Source''':
= Progress of the project =
 
== Week 1 (January 13th - Janurary 19th) ==
 
===Overview===
 
*Project discovery
 
*Initial contact with other members of the project
 
*Research about flight simulator and possiblities
 
   
  +
'''Outputs''':
===Ideas===
 
====Simulator====
 
*Flight simulator X
 
====Hardware configuration====
 
*One machine with 3 or 4 video outputs
 
*Two to three machine on the same network
 
   
  +
'''Destination''':
====Display====
 
*A front projector and 2 lateral screen (or 2 lateral projector)
 
*2 front screen and 2 lateral screen
 
   
  +
'''Action''':
== Week 2 (January 20th - Janurary 26th) ==
 
  +
* Natural language sentences (with MUST, MAY, SHALL)
===Global Configuration===
 
  +
* 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''':
[[File:diagramme_general.png]]
 
   
  +
'''Pre-condition''':
   
  +
'''Post-condition''':
   
  +
'''Side-effects''':
[[File:diagramme_startAIR.png]]
 
   
  +
=4. Product evolution=
===Meeting feedback===
 
*Take some measure
 
*Search for screen
 
   
  +
=5. Appendices=
   
  +
==5.1. SRS structure==
===Cockpit configuration===
 
  +
The document is based on template of the Software Requirements Specification (SRS) inspired of the IEEE/ANSI 830-1998 Standard.
*5 screen: 3 front and 2 lateral
 
* 50cm x 60cm [4:3]
 
* [50cm x 30cm] x 2 [16:9]
 
* ...
 
   
  +
'''References:'''
=Links=
 
  +
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
*[http://msdn.microsoft.com/en-us/library/cc526983.aspx SimConnect]
 
  +
* http://en.wikipedia.org/wiki/Software_requirements_specification
*[http://www.fsdeveloper.com/forum/showthread.php?t=88097 A thread with a similar project]
 
  +
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]
*[http://www.pilote-virtuel.com/viewtopic.php?id=1391m A tutorial for SimConnect installation]
 
  +
*[http://www.fstipsandaddons.com/tutorials/understanding-fsx-cameras.html About camera on FSX]
 
  +
=6. Index=
*[http://msdn.microsoft.com/en-us/library/ff798293.aspx ESP/FSX SDK]
 
*[http://www.fsdeveloper.com/forum/downloads.php?do=file&id=141 How to correctly use SimConnect in standalone appl]
 
*[http://www.fsdeveloper.com/forum/showthread.php?t=428057 A thread about manuverable AI]
 
*[http://www.prepar3d.com/SDKv2/LearningCenter/utilities/simconnect/sample_code/camera_system.html A essayer pour les vues]
 

Revision as of 12:50, 27 January 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


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