Contemporary Challenges in Requirements Discovery and Validation: Two Case Studies in Complex Environments - Intentional Perspectives on Information Systems Engineering - page 63

As a final point, a critical element of the collective exchange sessions in both
projects was the repeated generation of ad hoc scenarios which supported the explo-
ration of application-in-use for the relevant platforms. The scenarios served as an
effective mechanism for surfacing assumptions and creating productive conflict, in
which stakeholders had to work through their differences. For several years now,
the RE research community has recognized the importance of individual scenario
generation [ 35, 41, 43, 52] . However, scenario-based RE has tended to focus on
modeling approaches to scenario development, not their effective deployment. The
two cases suggest that formal scenario generation needs to advance to situations
where it can help direct requirements-oriented inquiries [ 35] .
7 Conclusion
In this study, we have explored the cognitive, social, and complexity-based impedi-
ments to effective requirements discovery and validation through two exploratory
case studies. The research has a range of implications for RE researchers and
practitioners as we wrestle with increasingly complex and heterogeneous envi-
ronments. The case studies provide an initial evaluation of the applicability of
the systemic model of requirements challenges to the practical issues faced by
project teams. In this regard, we find that many of the core challenges perceived by
practitioners are readily observed in real-world development projects. In addition,
the case studies serve to underscore the fundamental interrelatedness of require-
ments challenges. This finding suggests the need for a more system-based, holistic
approach to the requirements challenges. Our case analyses also suggest a num-
ber of areas for process and tool innovation in support of multi-party ISD efforts.
These include improved mechanisms for establishing task and process ownership
in multi-party development, use of evolutionary approaches that allow for the iter-
ative integration of requirements as an artifact comes into existence, and creating
opportunities for comprehensive exchanges across organizational, functional, and
task-based boundaries.
References
1. Aurum A, Wohlin C (2005) Requirements engineering: setting the context. In: Aurum A,
Wohlin C (eds) Engineering and managing software requirements. Springer, Berlin, pp 1-15
2. Bergman M, King J, Lyytinen K (2002) Large-scale requirements analysis revisited: the need
for understanding the political ecology of requirements engineering. Reqs Eng 7(3):152-171
3. Berry DM, Lawrence B (1998) Requirements engineering. IEEE Softw 15(2):26-29
4. Boehm B (1984) Verifying and validating software requirements and design specifications.
IEEE Softw 1(1):75-88
5. Boehm B, Egyed A, Port D et al (1998) A stakeholder win-win approach to software
engineering education. Ann Soft Eng 6(1):295-321
6. Boehm B, Grünbacher P, Briggs R (2007) Developing groupware for requirements negotia-
tion: lessons learned. In: Selby RW (ed) Software engineering: Barry W. Boehm's lifetime
contributions to software development, management, and research. Wiley, Hoboken, NJ,
pp 301-314