Requirements Engineering Process Improvement: An Industrial Case Study

Markov, Georgi; Hoffmann, Alex C.; Creighton, Oliver

doi:10.1007/978-3-642-19858-8_4

Cited by 2 publications

(1 citation statement)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The presence of a requirements repository arranged into catalogues and the internal organisation of requirements within catalogues provide a starting point for the realisation of effective searches that deliver accurate results . Traceability is highly desirable when building a requirements specification, although it is sometimes insufficient in industrial practice . For its part, requirements reuse emphasises the usage of requirements traceability .…”

Section: Experimental Interventions: Requirements Specification Technmentioning

confidence: 99%

Co-located and distributed natural-language requirements specification: traditional versus reuse-based techniques

Gea

Nicolás

Alemán

et al. 2016

J. Softw. Evol. and Proc.

View full text Add to dashboard Cite

Requirements Engineering (RE) includes processes intended to elicit, analyse, specify and validate systems and software requirements throughout the software life cycle. Mastering the principles of RE is key to achieving the goals of better, cheaper and quicker systems and software development projects. It is also important to be prepared to work with remote teammates, as distributed and global projects are becoming more common. This paper presents an experiment with a total of 31 students from two universities in Spain and Morocco who were assigned to either a co-located or a distributed team. Both traditional and reuse-based requirements specification techniques were applied by the participants to produce requirements documents. Their outcomes were then analysed, and the approaches were compared from the point of view of their effect on a set of performance-based and perception-based variables in co-located and distributed settings. We found significant differences in only productivity (Z = À2.320, p = 0.020) and difficulty (Z = À2.124, p = 0.034) as regards the scores attained for non-reuse and reuse conditions, both in the co-located modality. Our findings show that, in general, the participants attained similar results for requirements specification when using the two strategies in both distributed and non-distributed environments.

show abstract

Section: Experimental Interventions: Requirements Specification Technmentioning

confidence: 99%