TWIN Project Requirements Specification
TWIN Project Requirements Specification
Version 1.0
July 13, 2017
July 13, 2017
Page 1 of 7
TWIN Project Requirements Specification
Table of Contents
1.
EXECUTIVE SUMMARY ................................................................................................................................................. 3
1.1
1.2
2.
PRODUCT/SERVICE DESCRIPTION................................................................................................................................. 3
2.1
2.2
2.3
2.4
2.5
3.
PROJECT OVERVIEW .......................................................................................................................................................... 3
PURPOSE AND SCOPE OF THIS SPECIFICATION ......................................................................................................................... 3
PRODUCT CONTEXT ........................................................................................................................................................... 3
USER CHARACTERISTICS ..................................................................................................................................................... 3
ASSUMPTIONS.................................................................................................................................................................. 3
CONSTRAINTS................................................................................................................................................................... 3
DEPENDENCIES ................................................................................................................................................................. 4
REQUIREMENTS ........................................................................................................................................................... 4
3.1
FUNCTIONAL REQUIREMENTS .............................................................................................................................................. 4
3.2
USER INTERFACE REQUIREMENTS ......................................................................................................................................... 4
3.3
USABILITY........................................................................................................................................................................ 4
3.4
PERFORMANCE ................................................................................................................................................................. 4
3.4.1
Capacity ............................................................................................................................................................... 4
3.4.2
Availability ........................................................................................................................................................... 5
3.4.3
Latency ................................................................................................................................................................. 5
3.5
MANAGEABILITY/MAINTAINABILITY...................................................................................................................................... 5
3.5.1
Monitoring ........................................................................................................................................................... 5
3.5.2
Maintenance ........................................................................................................................................................ 5
3.5.3
Operations ........................................................................................................................................................... 5
3.6
SYSTEM INTERFACE/INTEGRATION ........................................................................................................................................ 5
3.6.1
Network and Hardware Interfaces ....................................................................................................................... 5
3.6.2
Systems Interfaces ............................................................................................................................................... 5
3.7
SECURITY......................................................................................................................................................................... 5
3.7.1
Protection ............................................................................................................................................................. 5
3.7.2
Authorization and Authentication........................................................................................................................ 5
3.8
DATA MANAGEMENT ........................................................................................................................................................ 5
3.9
STANDARDS COMPLIANCE................................................................................................................................................... 5
3.10 PORTABILITY .................................................................................................................................................................... 6
4.
USER SCENARIOS/USE CASES ....................................................................................................................................... 6
5.
DELETED OR DEFERRED REQUIREMENTS ...................................................................................................................... 6
6.
REQUIREMENTS CONFIRMATION/STAKEHOLDER SIGN-OFF......................................................................................... 7
APPENDIX ........................................................................................................................ERROR! BOOKMARK NOT DEFINED.
APPENDIX A.
APPENDIX B.
APPENDIX C.
APPENDIX D.
DEFINITIONS, ACRONYMS, AND ABBREVIATIONS ........................................................... ERROR! BOOKMARK NOT DEFINED.
REFERENCES........................................................................................................... ERROR! BOOKMARK NOT DEFINED.
REQUIREMENTS TRACEABILITY MATRIX ....................................................................... ERROR! BOOKMARK NOT DEFINED.
ORGANIZING THE REQUIREMENTS .............................................................................. ERROR! BOOKMARK NOT DEFINED.
July 13, 2017
Page 2 of 7
TWIN Project Requirements Specification
1. Executive Summary
1.1
Project Overview
During this project a LED wall should be built to implement an Europe information system. The LED
wall should be controllable by pupils at the four schools from Germany, Hungary, Italy and Poland
taking part in the project. The displayed content should give information about the participating schools
and the pupil’s home towns and their school lives.
1.2
Purpose and Scope of this Specification
The purpose of this specification is to define the hardware requirements for the LED wall. This
specification is the basis for implementing the hardware during the first project phase.
The items within the scope of this requirement specification are described in the following:
In scope
This document addresses requirements related to phase 1 of the TWIN Project:
 Building a LED wall which is able to display certain digital contents.
 Controlling issues of the LED wall as far as hardware issues are concerned.
 Display quality issues.
 Mechanical issues (e.g. housing, transportability, …)
 Power requirements.
Out of Scope
The following items are out of scope in phase 1 of the TWIN Project:


Software / programming issues.
Connectivity to peripherals (smartphones, Bluetooth, wifi,…)
2. Product/Service Description
In this section, describe the general factors that affect the product and its requirements.
2.1
Product Context
The LED wall should be able to interface several wireless communication ports, e. g. Bluetooth or wifi.
In addition to this the LED should be mounted in a room large enough to reach the optimal viewing
distance. Apart from that all other context related product requirements will be defined of the software
requirement specifications.
2.2
User Characteristics
The following users are expected to control the LED wall:


2.3
Students / pupils will select and share information on the LED wall by using their smartphones
Teachers and experienced students / pupils will update and service the contents.
Assumptions
The cost of LED wall fits in the budget and LED modules of a certain quality are available.
2.4


Constraints
The size of the LED wall is limited by the mounting room.
As the LED wall will be placed in a public building specific guidelines have to be obeyed (for
example fire protection issues)
July 13, 2017
Page 3 of 7
TWIN Project Requirements Specification
2.5


Dependencies
The LED wall hardware has to be identical at all participating schools.
The viewing distance is limited to 2-3 m.
3. Requirements
Priority Definitions
The following definitions are intended as a guideline to prioritize requirements.


Priority 1 – The requirement is a “must have” as outlined by policy/law
Priority 2 – The requirement is needed for improved processing, and the fulfillment of the
requirement will create immediate benefits
Priority 3 – The requirement is a “nice to have” which may include new functionality

3.1
Functional Requirements
Req#
Requirement
Priority
TWIN_01
The LED wall should provide a resolution high enough to meet
an optimal viewing distance of 2-3 m.
1
TWIN_02
The LED wall should be controlled by a microcontroller or a
PC.
1
TWIN_03
The framerate of the LED wall should be sufficient for
displaying videos.
1
TWIN_04
The size of the LED wall should be about 2 m x 1.5 m.
1
TWIN_05
The LED wall should be able to display typical widescreen
formats.
1
TWIN_06
The LED wall should consists of full color LEDs
1
TWIN_07
The brightness of the LED wall should be sufficient for indoor
use.
1
TWIN_08
The housing of the LED wall should be in compliance with the
legal fire protection requirements.
1
3.2
User Interface Requirements
The User Interface Requirements are part of the software requirement specifications and out of the
scope of these requirements.
3.3
Usability
The Usability is part of the software requirement specifications and out of the scope of these
requirements.
3.4
Performance
The Performance is part of the software requirement specifications and out of the scope of these
requirements.
July 13, 2017
Page 4 of 7
TWIN Project Requirements Specification
3.4.1 Capacity
The Capacity is part of the software requirement specifications and out of the scope of these
requirements.
3.4.2




Availability
Hours of operation: 8 hours per day, five days a week
Level of availability required: no safety issues, therefore restoration of availability within one week
Impact of downtime on users and business operations: None.
Reliability: acceptable mean time between failures (MTBF): 8 days.
3.4.3 Latency
The maximum acceptable time for a service request is one week.
3.5
Manageability/Maintainability
3.5.1 Monitoring
The LED wall should be protected by a virus scanner / fire wall to prevent any unauthorized
manipulation.
3.5.2 Maintenance
The Maintenance is part of the software requirement specifications and out of the scope of these
requirements.
3.5.3 Operations
The Operations are part of the software requirement specifications and out of the scope of these
requirements.
3.6
System Interface/Integration
3.6.1 Network and Hardware Interfaces
The used hardware interfaces highly depend on the software requirement specifications and therefore
are out of the scope of these requirements.
3.6.2 Systems Interfaces
The System Interfaces are part of the software requirement specifications and out of the scope of these
requirements.
3.7
Security
3.7.1 Protection
The LED wall should be protected by a virus scanner / fire wall to prevent any unauthorized
manipulation.
3.7.2 Authorization and Authentication
Authorization and Authentication issues will be discussed in the software requirement specifications.
3.8
Data Management
Data Management issues will be discussed in the software requirement specifications.
July 13, 2017
Page 5 of 7
TWIN Project Requirements Specification
3.9
Standards Compliance
The housing of the LED wall should be in compliance with the legal fire protection requirements.
3.10 Portability
In some schools a portable version of the LED wall is necessary: The portability only concerns
mechanical movements of the LED wall. The LED wall will not be moved during operation.
4. User Scenarios/Use Cases
The content displayed on the LED wall should give information about the participating schools and the
pupil’s home towns and their school lives. The information should be selected by using a smartphone.
5. Deleted or Deferred Requirements
Req#
Requirement
Status
Priority
TWIN_09
The LED wall should provide a live
video chat functionality
Deferred to phase 2 (software
development phase)
3
July 13, 2017
Page 6 of 7
TWIN Project Requirements Specification
6. Requirements Confirmation/Stakeholder sign-off
Meeting Date
Attendees (name and role)
Comments
11/16/201511/20/2015
July 13, 2017
Page 7 of 7