ToyLabs D3.1 - Technology Requirements and ToyLabs Components Analysis - v1

Deliverable D3.1 titled as “Technology Requirements and ToyLabs Components Analysis-v1” is used to document the preliminary efforts undertaken within the context of Tasks 3.1 (and also 3.2, 3.3 and 3.4), with the aim to identify the requirements of the ToyLabs platform and of its structural components. Towards this end, the scope of the deliverable at hand is used to collect and analyse the functional and non-functional requirements of the platform. This is achieved by following a well-defined requirements extraction technique, inspired from the agile software development process, adopting the main principles of epics and user stories. The overall methodology is described in the necessary detail and tries to remain at a high level to be understandable by both developers as well as business users, as it is essential to convey the main concepts and requirements to both groups. This will help them validate each envisioned operation of the platform from the very early stages of software design process and assess the platform’s added value. As a result, D3.1, following the prescribed methodology, identifies the main actors, the epics of the overall platform, and matches those to the envisaged components that come out of the work conducted in WP2. As a next step, D3.1 goes on with the identification of the user stories which has been conducted in a collaborative manner between all business, pilot and the technical partners of the consortium. Furthermore, and based on those user stories, the consortium managed to distil a larger list of functional requirements, noting also the importance of each requirement for the overall platform. At the end of the process, non-functional requirements regarding the overall platform have been also identified. It needs to be note that D3.1 hands over the backlog identified to the next deliverable (D3.2), which will work on their prioritisation and on the definition of the ToyLabs MVP, that will also prescribe the development roadmap. Those steps are also described in the methodology presented in D3.1. At the end of the tasks that formulated D3.1, the consortium managed to identify 8 actors, draw 28 Epics, out those 150 user stories were defined in order to cover the whole ToyLabs methodology and its tools as they have been defined in deliverable D2.1. These resulted at the end to a list that contained 174 functional and 12 nonfunctional requirements