Views

• All requirements
• Scenario - scene view
• Keywords
• Authors
• Companies

Priority

• mandatory - must be implemented. Without the mandatory requirements SPICE cannot be implemented.
• high - it is recommended to be implemented. Without the high priority requirements, it would be difficult, but possible to implement SPICE.
• medium - it would support SPICE functionality a lot.
• low - it would be nice to have in SPICE.

Type

• functional - these requirements specify particular behaviors of SPICE.
• non-functional - these requirements specify criterias, that can be used to judge the operation of SPICE (e.g. performance, quality, reliability, safety, security, etc.).

Demo

• implemented - these requirements map to features, which will be implemented and demonstrated at Probe2 at the end of SPICE project.
• concept - these requirements map to features, which will be demonstrated using Powerpoint slides at Probe2 at the end of SPICE project.

Category

• open market
• enterprise
• device
• technical
• user
• regulatory

SPICE_value

• service creation
• service roaming
• service matching
• (seamless) service adaptation
• service execution