APOSDLE Use Scenarios & Requirements for 3rd Prototypes
This document presents the user and system requirements for the third prototype of the APOSDLE system (P3); it does not include the set of requirements that have been previously agreed upon for delivery in month 36 of the project (documented in D VI.3). The document builds upon other reports produced in WPVI, specifically:
- D VI.2: Use Cases and Application Requirements 1 (First Prototype)
- D VI.3: Use Cases and Application Requirements 2 (Second Prototype)
- D VI.7 Formative evaluation document
- D VI.13: APOSDLE Social solutions aligned to 2nd prototype
- D VI.15: Scope of APOSDLE Target Group, Problems and Needs
The requirements for P3 were gathered from various sources, including:
- Focus groups. They were held with a multinational manufacturing and services provider in the Aerospace, Marine and Energy markets counting thousands of employees, and a small Human-Computer Interaction consultancy providing user-centred design and research services to UK and international clients and partners. Both organisations were external to the APOSDLE consortium and the sessions yielded additional insights into the perceptions and opinions of potential customers of APOSDLE as well as possible requirements.
- Findings from the Formative Evaluation meeting. The meeting, held at City on the 15th and 16th May 2008, saw application and technical partners discussing their views on APOSDLE and the implementation of its second prototype (P2). The exchanges were audio and video-recorded and later analysed for possible requirements on P3
- The online diaries used in P2ís formative evaluation. The diaries were used for the participants to record their thoughts, reactions, experiences and opinions during their use of P2; they provided valuable data on possible requirements for P3.
- The social solutions aligned to P2. A deliverable exploring the ways in which APOSDLE needed to fit organisations? environment, culture and practices was produced (D VI.13); it detailed how these factors could affect the system?s adoption and integration, and its analysis yielded some insights into additional requirements.
- The findings were analysed by Requirements Engineers at City and presented in adapted VOLERE templates (Robertson & Robertson, 2006).