RICM4 2017 2018 - Connected shop SRS

From air
Jump to navigation Jump to search

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

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.4 General constraints

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:

4. Product evolution

Not acting only for disabled students but also for a wider pool of individuals.

5. Appendices

SRS related documents used to establish this page :

2. General description

2.1 Product perspective

Getting involved in other institutions linked to the health sector.

Building a system capable of recognizing vocal phrases for visually impaired individuals.

2.2 Product functions

Providing an answer adapted to the requests of a disabled user thanks to an automaton.

It should be able to lead a discussion in a logical and consistent way from the beginning to the end of it, which means its interactions have to be as close as possible from the ones a real human would have.

It also needs to collect some important informations about the user it’s discussing with.

This conversation will take place on a web/mobile app.

2.3 User characteristics

Disabled students (essentially deaf and dumb individuals) living in Grenoble and studying in the Grenoble-Alpes University.

2.4 General constraints

Disablement of users. Web hosting, database and user files.

2.5 Assumptions and dependencies

The disabled student must have an access to a smartphone or a computer in order to use the application.

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 1 :

Function:

Description:

Inputs:

Source:

Outputs:

Destination:

Action:

Non functional requirements:

Pre-condition:

Post-condition:

Side-effects:

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

Not acting only for disabled students but also for a wider pool of individuals.

5. Appendices

SRS related documents used to establish this page :

Retrieved from "https://air.imag.fr/index.php?title=RICM4_2017_2018_-_Connected_shop_SRS&oldid=41542"