iHelp: State of the art and requirements analysis II
Creators
- Ainhoa Azqueta1
- Miriam Cabrita2
- Calogero Casa3
- Andrea Damiani3
- Sakis Dalianis4
- Krasimir Filipov5
- Giorgos Giotis4
- Lars Gustaffson6
- Pavlos Kranas7
- Dimosthenis Kyriazis8
- Rostislav Kostadinov9
- Artitaya Lophatananon10
- Chris Orton11
- Borja Liobell Crespo12
- George Marinos8
- George Manias8
- Shwetambara Malwade13
- Nikolay Mehandjiev14
- Krisztina Mekli10
- Kenneth Muir10
- Anna Nanou8
- Petia Nikolova14
- Marzena Nieroda10
- Harm Op den Akker2
- Anastasios Pantazidis2
- Aristodemos Pnevmatikakis2
- Usman Rashid11
- Shabbir Syed-Abdul13
- Tanja Tomson6
- Usman Wajid11
- Nerea Aguado Lopez12
- Eshita Dhar13
- Te-Min Ke10
- 1. UPM
- 2. iSprint
- 3. FPG
- 4. ATC
- 5. KOD
- 6. KI
- 7. LXS
- 8. UPRC
- 9. MUP
- 10. UNIMAN
- 11. ICE
- 12. HDM
- 13. TMU
- 14. DS4
Description
This deliverable summarizes the work that has been done in the score of Task 2.1 (“State of the art and requirement analysis”) until M12. This is the second version of a series of deliverables of this task, whose main objective is to specify the pilot scenarios, their involved datasets, and their corresponding user requirements, as well as the system and technical requirements that are being imposed by the platform. As mentioned in the previous version of this deliverable (i.e. D2.1 – State of the art & Requirement Analysis I), the purpose of these series is to track those requirements throughout the project and update them during the progress of the project. As a result, this second version depicts the enhanced (primary & secondary) data requirements that have been identified after the delivery of the first versions of the scientific reports and provides an updated version of some of the technical requirements of the iHelp platform. As mentioned in the first version of this deliverable the approach that has been followed is twofold: A top-down approach that is followed with respect to the user requirements that were collected by the use case providers themselves, after specifying the business goals and objectives of the use case, along with a concrete definition of the scenario. Moreover, a bottom-up approach is additionally complemented that aims to identify and analyse the technical requirements with respect to the technical work packages that are focusing on the platform technological needs.
The result of this analysis is an updated list of measurable an unambiguous requirement that will drive the design of the overall architecture of the iHelp platform, focusing on serving all different needs of the various use cases of the project. As the project is still progressing, a final version of this deliverable will help the architecture designers of the platform and its software developers to adjust the overall architecture and its implementation accordingly, with respect to the principles of the agile methodology. Moreover, as our scope is to continuously keep track with the latest technological advances and how we can take advantage of them while developing our -a state-of-the-art analysis has been performed regarding the major technologies that are envisioned to be exploited.
This deliverable is being released on M12 of the project and its main aim is to specify the scenarios of the use cases, which drove the user requirements based on their perspective, the updated version of the secondary data requirements and the technical requirements as foreseen by the technical partners that are being involved in the design of the overall architecture of the platform. A final version of this document will be released on M18.
Files
iHelp_D2.2_State_of_the_Art_and_Requirement_Analysis_II_v1.0.pdf
Files
(3.6 MB)
Name | Size | Download all |
---|---|---|
md5:f1ce361f9caa6a96faf16883d055f8d5
|
3.6 MB | Preview Download |