D2.5 Lessons Learned and updated requirements report I

A public report, led by IN-JET, documenting the Lessons Learned and updating the initial requirements

This deliverable provides an overview of the requirements engineering work performed in the first half of the project through the iterative process adopted for the COMPOSITION project. The deliverable documents the Lessons Learned and changes in the requirements compared to the information provided in D2.2 Initial Requirements Specification. A further update will be provided in D2.6 Lessons Learned and Updated Requirements Report II, which is due in M28 (December 2018).

The requirements derived from the use cases will be enhanced in an iterative process to assure that the user-centred approach outlined in the DoA is followed in all phases of the project. Lessons Learned are part of COMPOSITION’s commitment to Knowledge Management, promoting recurrence of successful outcomes and precluding the recurrence of unsuccessful outcomes. Lessons are learned during project research and technology development work, during testing and integration as a part of the validation of project prototypes and can thus be learned throughout the project work. The Lesson Learned process adopted by COMPOSITION has six steps: Collection, verification, storage, dissemination, reuse and identification of improvement opportunity. For collection and storage, a repository has been established in the COMPOSITION Confluence Wiki

A total of 26 Lessons Learned has been reported in the first cycle. Compared with the list of requirements in D2.2 Initial Requirements Specification, 37 requirements have been added. Not all of these are the result of the Lessons Learned; some are technical requirements derived from new or existing user requirements. All requirements have been updated, though the majority not in substance, but rather as a result of adding Custom Labels for various purposes, e.g., filtering/structuring. Fourteen of the original requirements have been rejected. As of mid-November 2017, the COMPOSITION JIRA repository contains 125 active requirements, 8of which have been implemented, while 70have status “Part of Specification”, 17 have passed QC check and 30 are Open. The group “Part of Specification” covers many requirements that have been partially implemented. All requirements have been reassessed, and if appropriate, Requirement Priority has been changed to reflect the priority of the use case(s) they are part of. With minor deviations within each group, Requirement Priority ‘Major’ includes requirements in the Tier 1 Use Cases (approx. 64%), ‘Medium’ the requirements in the Tier 2 Use Cases (approx. 21%), and the rest are Tier 3.

With the further development of the COMPOSITION architecture, the list of Components has been extended and now comprises 23 entities. This includes five added components: Building Management System, Data Collection System, Marketplace, Marketplace UI and Service Catalogue. Through the “Component” field in the requirement definition template, all requirements are associated with one or more components, providing a structural overview relative to the COMPOSITION architecture described in D2.3 The COMPOSITION Architecture Specification I.