27.03.2014 Views

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

TABLE III.<br />

Analyze<br />

For the purpose of<br />

With respect to<br />

From the point of view<br />

In the context of<br />

GOAL OF THE 2 ND .EMPIRICAL STUDY<br />

The 2 nd version of the REMO technique<br />

Characterizing<br />

Effectiveness and adequacy of the<br />

identified requirements using the<br />

business processes in the BPMN, when<br />

compared to a traditional approach.<br />

Software Engineering Researchers<br />

A requirements elicitation carried out by<br />

graduation students and based on<br />

business processes models<br />

Hypotheses: the study was planned and conducted in order<br />

to test the following hypotheses (null and alternative,<br />

respectively) regarding the effectiveness and adequacy<br />

indicators:<br />

H01: There is no difference in t erms of effectiveness in<br />

using the REMO technique to elicit requirements regarding<br />

business processes.<br />

HA1: The REMO technique presented a difference in the<br />

effectiveness indicator, when compared to a traditional<br />

approach.<br />

H02: There is no difference in terms of adequacy of the<br />

identified requirements when using the REMO technique and a<br />

traditional approach.<br />

HA2: The REMO technique presented different results<br />

regarding the adequacy of the identified requirements (not<br />

considering false positives), when compared to a traditional<br />

approach.<br />

Context: We carried out the 2nd empirical study in<br />

November 2011, with others senior-level undergraduate<br />

students from Computer Science course (Federal University of<br />

Amazonas). In this experiment, the students also had tutorials<br />

regarding requirements elicitation and business processes<br />

modeling. The business process model chosen as object of<br />

study was part of the processes from the Academic Secretary of<br />

the University. We selected four academic processes: (a) to do<br />

enrollment adjustment; (b) to request recovery of academic<br />

credits; (c) request grades correction; and (d) monitoring<br />

application.<br />

Subjects: 20 subjects agreed to participate in this study and<br />

played the role of system analysts. These subjects were<br />

classified and divided into two groups of 10 subjects. We<br />

balanced each group regarding the subjects experience with<br />

respect to their experience in software development and<br />

requirements elicitation.<br />

Instrumentation: the main instruments in this study were<br />

the same type used in the first study: (a) an execution guide<br />

with tasks, (b) the business context document containing the<br />

BPMN processes modeling, and (c) requirements register<br />

spreadsheet. Furthermore, the group that used the REMO<br />

technique received the technique’s heuristics document.<br />

Execution: the subjects carried out the study the same day<br />

in different rooms. There was a moderator in each room to<br />

guarantee that there was no communication among the<br />

subjects. The subjects had 180 minutes to carry out the<br />

requirements elicitation. At the end of the study, all subjects<br />

returned the requirements lists and the follow up questionnaire<br />

filled out.<br />

We created a unique requirements list, in order to<br />

discriminate the requirements. A specialist in requirements<br />

elicitation carried out the discrimination process. The<br />

discrimination meeting was carried out to ide ntify which<br />

requirements were considered inadequate (false-positives).<br />

Results and Quantitative Analysis: Table IV shows the<br />

results per group of subjects. We calculated the effectiveness<br />

indicator using 152 known requirements from the business<br />

process models used as object of study.<br />

TABLE IV. QUANTITATIVE RESULTS PER SUBJECTS<br />

Technique<br />

/ Subject<br />

Experience IIR FP TRR EI AI<br />

01 High 63 21 42 27.63% 66.67%<br />

02 Medium 46 07 39 25.66% 84.78%<br />

03 Medium 59 09 50 32.89% 84.75%<br />

04 Medium 47 03 44 28.95% 93.62%<br />

05 Medium 54 09 45 29.61% 83.33%<br />

06 Low 31 07 24 15.79% 77.42%<br />

07 Low 47 15 32 21.05% 68.09%<br />

08 Low 37 10 27 17.76% 72.97%<br />

09 Low 21 09 12 7.89% 57.14%<br />

10 Low 29 05 24 15.79% 82.76%<br />

11 High 52 05 47 30.92% 90.38%<br />

12 Medium 48 16 32 21.05% 66.67%<br />

13 Medium 25 10 15 9.87% 60.00%<br />

14 Medium 26 02 24 15.79% 92.31%<br />

15 Medium 26 05 21 13.82% 80.77%<br />

16 Low 32 06 26 17.11% 81.25%<br />

17 Low 43 06 37 24.34% 86.05%<br />

18 Low 45 00 45 29.61% 100.0%<br />

19 Low 48 03 45 29.61% 93.75%<br />

20 Low 41 03 38 25.00% 92.68%<br />

Legend: IIR – Initially Identified Requirements; FP – False Positives; TRR –<br />

Total of Real Requirements; EI – Effectiveness Indicator; AI – Adequacy<br />

Indicator.<br />

In order to validate these data we used the Mann-Whitney<br />

statistic method (supported by the SPSS Statistics v17.0 tool)<br />

and the boxplots analysis. As we can see in Fig. 5, the boxplots<br />

graph shows that the effectiveness indicator was similar among<br />

the subjects who used the technique and those who used the<br />

traditional approach. When we compared the two samples<br />

using the Mann-Whitney test, we did not find any significant<br />

differences between the two groups (p = 0.850 and = 0.05)<br />

therefore, supporting the null hypothesis H01.<br />

TRADITIONAL<br />

REMO<br />

Figure 5. Boxplots for the Effectiveness indicator of the requirements.<br />

37

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!