Proj-2013-2014-StartAIR-2

Progress of the project

UML

=1.  Introduction=

1.1 Purpose of the requirements document
This Software Requirements Specification (SRS) identifies the requirements for the project StartAir Safe. In case of a open source project, we must present the requirement to others potential contributors. This document is a guideline about the functionalities offered and the problems that the system solves.

1.2 Scope of the product

 * The software we are developping is a plugin for Microsoft Flight Simulator
 * It is an Open Source software
 * Our software is design only for Windows plateforms

1.3 Definitions, acronyms and abbreviations

 * FSX(ESP): Miscrosoft Flight Simulator X is flight simulator for windows devices


 * SimConnect: SimConnect is a SDK that can be used to write add-on components for ESP


 * PBH(pitch, bank, heading):


 * UDP: User Datagram Protocol is a network protocol use to send datagram

1.5 Overview of the remainder of the document
=2.  General description=

2.1 Product perspective
The StartAIR project is one part of a big Multi-department project (TIS, MATERIAUX, 3I). The aim is to build a realistic flight simulator to help doctors work with asperger people. The project use a multi-computer systèm based on windows devices. The 3I project consist of the creation of a new command board, the TIS part consit of building a close systèm to interact with asperger people and the MATERIAUX project is to build acoustic walls to create a realistic airplane cockpit.

2.4 General constraints

 * Platform constraints:
 * Must run on Windows XP/7/8/8.1


 * Acces to an USB hub or a local network

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
 * IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998

=6. Index=