D.3.3 ALGORITHMS FOR INCREMENTAL ... - SecureChange

Table 3. User Study Organization
Meeting Date Participants Contents
PM1 March,
2011
RA, OBS Participants identify the research questions of
the user study, and the success criteria. Further
more, the strategy to be followed to conduct
the study is sketched.
IWS1 March, RA, OBS, DE RAs,OBSs and DEs define and agree upon the
IWS2
WS1
(day 1)
2011
March,
2011
April,
2011
RA
RA, OBS,
DE
research design.
RAs prepared the training materials (tutorials
about requirements engineering, requirements
evolution, interview guide. These documents
were distributed to all the DEs.
RA present the training material to domain experts.
Domain experts give feedback to enrich
each of discussed items, and to improve the
way they are presented.
WS1
(day 2)
April,
2011
RA, OBS, DE RA gives an introductory talk about ideas of
evolution. Next, RA presents research objects.
During each of presentation, DEs are interviewed
to collect feedbacks about the change
management process adopted by ANSPs.
IWS3 May 2011 RA,OBS The RAs analyze feedbacks from WS1 and
WS2
IWS4
June,
2011
August,
2011
prepare for WS2.
RA, OBS, DE Participants continue the validation work. DEs
elaborate more on the approach to model and
analyze requirements evolution.
RA, OBS,
RAs analyze the feedbacks collected during
the two workshops.
The table shows the organization of the user study. In this table PM = Preliminary Meeting, IWS = Internal Working Session,
WS = WorkShop.
second day of the first workshop and during the second workshop. In this session, requirements
analysts gave presentations about the proposed approach to model and reason
on evolution. The domain experts were asked whether the approach would make
sense or useful based on their experience. The domain experts also reported the existing
process to change management adopted by Air Navigation Service Providers.
4.3 Results Analysis
The qualitative data collected in the form of video recording were transcripted to understand
and review the conversations between the ATM experts and the requirement
analysts. The tool used to perform qualitative data analysis is NVivo 9 [7]. Using NVivo,
the transcription is coded (in terms of qualitative analysis) to distinguish between the
various topics of discussion and points of feedback. Different codes and their descriptions
are reported in Table 4. The coding was further analyzed to emerge with evidence
8