D4.1 Pilots Requirements Analysis Report
Main Authors: | Julián Moreno-Schneider, Georg Rehm |
---|---|
Format: | Report publication-deliverable Journal |
Terbitan: |
, 2018
|
Subjects: | |
Online Access: |
https://zenodo.org/record/1256830 |
ctrlnum |
1256830 |
---|---|
fullrecord |
<?xml version="1.0"?>
<dc schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"><creator>Julián Moreno-Schneider</creator><creator>Georg Rehm</creator><date>2018-05-31</date><description>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.
Preparation of a survey to collect, from the pilot use cases partners, their primary needs.
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.
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.
</description><identifier>https://zenodo.org/record/1256830</identifier><identifier>10.5281/zenodo.1256830</identifier><identifier>oai:zenodo.org:1256830</identifier><relation>doi:10.5281/zenodo.1256829</relation><relation>url:https://zenodo.org/communities/lynx</relation><rights>info:eu-repo/semantics/openAccess</rights><rights>https://creativecommons.org/licenses/by/4.0/legalcode</rights><subject>pilots requirements</subject><title>D4.1 Pilots Requirements Analysis Report</title><type>Report:Report</type><type>Other:publication-deliverable</type><recordID>1256830</recordID></dc>
|
format |
Report:Report Report Other:publication-deliverable Other Journal:Journal Journal |
author |
Julián Moreno-Schneider Georg Rehm |
title |
D4.1 Pilots Requirements Analysis Report |
publishDate |
2018 |
topic |
pilots requirements |
url |
https://zenodo.org/record/1256830 |
contents |
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.
Preparation of a survey to collect, from the pilot use cases partners, their primary needs.
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.
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.
|
id |
IOS16997.1256830 |
institution |
ZAIN Publications |
institution_id |
7213 |
institution_type |
library:special library |
library |
Cognizance Journal of Multidisciplinary Studies |
library_id |
5267 |
collection |
Cognizance Journal of Multidisciplinary Studies |
repository_id |
16997 |
subject_area |
Multidisciplinary |
city |
Stockholm |
province |
INTERNASIONAL |
shared_to_ipusnas_str |
1 |
repoId |
IOS16997 |
first_indexed |
2022-06-06T04:28:02Z |
last_indexed |
2022-06-06T04:28:02Z |
recordtype |
dc |
_version_ |
1734902173994582016 |
score |
17.608969 |