May 31, 2018 Project deliverable Open Access

D4.1 Pilots Requirements Analysis Report

Julián Moreno-Schneider; Georg Rehm

This report provides an overview of the process and methodology applied in Lynx for gathering the requirements of the pilot use case partners, structured in three phases.

1. Preparation of a survey to collect, from the pilot use cases partners, their primary needs.
2. Organisation of face-to-face workshops with the pilot use case partners to collect, in a systematic and detailed way, the needs in their respective use cases.
3. Elicitation process to further specify and prioritise the requirements obtained from the face-to-face workshops to formulate concrete sets of use case specific requirements.

This three-phase-process resulted in a complex set of 42 requirements for the three business cases (pilots). The business cases are composed of four scenarios: data protection, labour law, CE marking and geothermal energy. From these scenarios, sets of use cases were extracted: three use cases for data protection, three use cases for labour law, two use cases for CE marking and two use cases for geothermal energy. The use cases have been defined in such a way that they can guide the further development process by defining example users (persona approach). Each of the personas includes representative workflows provided by the Lynx platform.

The detailed list of prioritised requirements for the three Lynx pilot business cases is shown in and 18. The requirements are divided into two groups: (i) those that focus on the functionalities of the different pilots (scenarios); (ii) those that focus on the functionality of the Lynx platform.

• Selected example features of individual pilots (scenarios) are:
  • User management
  • Upload of files and queries
  • In-document navigation
  • Simple payment feature (optional)
• Selected example features of the Lynx platform are:
  • Access to relevant documents in each scenario (GDPR, labour law, standards etc.)
  • Offer services through APIs so that they can be integrated in existing platforms
  • Allow storage of private information in the Legal Knowledge Graph
  • Manage information (and translations) in EN, ES, DE and NL
  • Accept and generate different file formats: PDF, XML, HTML, plain text

Apart from the prioritised list of business case requirements (related to functionalities of the platform), it is equally important to determine the requirements related to datasets. Each business case (and scenario and use case) requires different datasets in order to perform its functionality. The main datasets that are needed in the business cases are:

• GDPR
• Labour law
• Standards

Now that the pilots requirements analysis has been completed, the next steps include:

• Preparation of concrete software development specifications based on the requirements
• Discuss and agree upon the division of the tasks, i.e., to map services onto requirements
• Discuss and agree upon an (optional) process to update the requirements.