Update Requirements authored by Nicolas Pope's avatar Nicolas Pope
......@@ -61,17 +61,17 @@ The prototype is to focus on tele-immersive video and interfaces required to ope
* **O4.3:** Use the platform for non-remote data capture for participant research, providing at least some analysis or data extraction tools to demonstrate potential towards S1 and S4.
# 2. OVERALL DESCRIPTION
The prototype will be a new platform that enables the capture, mixing, filtering, analysis, recording and streaming of 3D audio-visual data in a modular and flexible manner so that individual data sources or algorithms can be replaced or evolved in the future. The key components are therefore:
The prototype will be a new platform that enables the capture, mixing, filtering, analysis, recording and streaming of 3D audio-visual data in a real-time, modular and flexible manner so that individual data sources or algorithms can be replaced or evolved in the future. The key components are therefore:
* **C1:** 3D Scene Capture from fixed lab spaces as a 3D-AV data source
* **C2:** 3D-AV mixing and filtering system, regardless of data source
* **C3:** 3D-AV Analysis system to extract higher-level data about a scene
* **C4:** Recording 3D-AV and playback as a data source
* **C5:** Lossless and lossy compression of 3D-AV for storage and streaming
* **C6:** Visualisation front-end(s)
* **C1:** *Capture* - 3D Scene Capture from fixed lab spaces as a 3D-AV data source
* **C2:** *Mixing* - 3D-AV mixing and filtering system, from any number of arbitrary data sources
* **C3:** *Analysis* - 3D-AV Analysis system to extract higher-level data about a scene
* **C4:** *Recording* - 3D-AV and playback as a generic 3D-AV data source
* **C5:** *Streaming* - Lossless and lossy compression of 3D-AV for storage and streaming
* **C6:** *Presentation* - Interactive visualisation front-end(s) from a 3D-AV stream
## 2.1 USER NEEDS
What is to be captured, the kinds of mixing and filtering, as well as expectations on interaction and visualisation all depend upon the target audiences initially identified by the 5 usage scenarios in section 1.
## 2.2 DEPENDENCIES AND ASSUMPTIONS
......
......