RICM4 2017 2018 - Connected shop SRS

This document is inspired by the following file : http://www.math.uaa.alaska.edu/~afkjm/cs401/IEEE830.pdf.

=1.  Introduction=

1.1 Purpose of the requirements document
The SRS is a document describing the software system of the Connected shop project. It describes how the system is supposed to work with functional and non functional requirements.

1.2 Scope of the product
This virtual fitting room allows users to try T-shirt on themself without moving. It display on a screen a video of the user with others clothes.

1.3 Definitions, acronyms and abbreviations
Kinect : camera device that can monitor a moving person. Unity : 3D engine that can be used with a Kinect.

1.4 References

 * The UML: https://air.imag.fr/index.php/RICM4_2017_2018_-_Connected_Shops/UML

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

2.1 Product perspective
The product would be available in clothes shops, where you could try clothes virtually.

2.2 Product functions
The product provide an image of the person trying an outfit.

The outfit is chosen by the user, by moving his hands, thanks to an interface.

2.3 User characteristics
Customers of a clothes shop. The customer must be able to see the screen.

2.5 Assumptions and dependencies
The customer must stand up while using the virtual fitting room.

=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: Try an outfit virtually

Description: The main goal of this project is to put a virtual outfit on someone who is using the virtual fitting room.

Inputs: Kinect.

Source:

Outputs: Screen.

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: