Architecting-problems rooted in requirements

Information and Software Technology

Volumn 50, Issue 1-2, 2008, Pages 53-66

  Ferrari, Remo N ^a   Madhavji, Nazim H ^a  

^a UNIVERSITY OF WESTERN ONTARIO   (Canada)

Author keywords

Empirical study; Process improvement; Requirements engineering; Software architecture; Software quality

Indexed keywords

FEEDBACK; PROBLEM SOLVING; QUALITY ASSURANCE; SOFTWARE ARCHITECTURE;

ARCHITECTURE MAPPING; BANKING APPLICATIONS; STAKEHOLDERS;

REQUIREMENTS ENGINEERING;

EID: 36549058665     PISSN: 09505849     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.infsof.2007.10.012     Document Type: Article

References (34)

1. M. Barbacci, R. Ellison, A. Lattanze, J. Stafford, C. Weinstock, W. Wood, Quality Attribute Workshops (QAWs), third ed., SEI Technical Report, 2003.
2. Basili V.R., and Rombach H.D. The TAME project: towards improvement-oriented software environments. IEEE Transactions on Software Engineering SE-14 6 (1988) 758-773
3. Basili V.R., and Weiss D. A methodology for collecting valid software engineering data. IEEE Transactions on Software Engineering SE-10 6 (1984) 728-738
4. Bass L., Clements P., and Kazman R. Software Architecture in Practice. second ed. (2003), Addison-Wesley, Reading, MA
5. P. Berander, Using students as subjects in requirements prioritization, in: Proceedings 7th International Conference on Empirical Assessment & Evaluation in Software Engineering, 2004, pp. 95-102.
6. M. Brandozzi, D.E. Perry, From goal-oriented requirements to architectural prescriptions: the Preskriptor process, STRAW workshop 2003.
7. J.W. Creswell, Research design: qualitative, quantitative, and mixed methods approaches, in: Thousand Oaks, Sage Publications, CA, 2003.
8. Damian D., and Chisan J. An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management. Transactions on Software Engineering 32 7 (2006) 433-453
9. A. Egyed, P. Grunbacher, N. Medvidovic, Refinement and evolution issues in bridging requirements and architecture - the CBSP approach, STRAW workshop 2001.
10. R. Ferrari, N.H. Madhavji, Impact of requirements knowledge and experience on software architecting: an empirical study, Sixth Working IEEE/IFIP Conference on Software Architecture, India, 2007.
11. Finkelstein A. The future of software engineering. ICSE 2000 Proceedings (2000)
12. D. Graham, Testing to improve requirements - is it mission impossible? 14th Requirements Engineering Conference (RE06), September 2006, Minneapolis, USA.
13. Guion L. Triangulation: establishing the validity of qualitative studies. University of Florida Extension: Institute of Food and Agricultural Sciences (2002)
14. Hancock B. An introduction to qualitative research. Trent Focus for Research and Development in Primary Health Care (2002)
15. Host M., Regnell B., and Wohlin C. Using students as subjects - a comparative study of students and professionals in lead-time impact assessment. Empirical Software Engineering (2000) 201-214
16. H. In, R. Kazman, D. Olson, From requirements negotiation to software architectural decisions, STRAW workshop 2001.
17. R. Kazman, M. Klein, P. Clements, ATAM: Method for Architecture Evaluation, SEI technical report, 2000.
18. E. Kuwana, J.D. Herbsleb, Representing knowledge in requirements engineering: an empirical study on what software engineers need to know, in: Proceedings of IEEE International Symposium on Requirements Engineering, 1993, pp. 273-276.
19. D. Liu, H. Mei, Mapping requirements to software architecture by feature-orientation, STRAW workshop 2003.
20. L. WenQian, S. Easterbrook, Eliciting architectural decisions from requirements using a rule-based framework, STRAW workshop 2003.
21. N.H. Madhavji, D. Perry, From Software Requirements to Architectures, CASCON workshop, Toronto, 5th October, 2004.
22. Mason J. Qualitative Researching (1996), Sage Publishing Ltd., London
23. L. Metze, Pride Technical Report: A Reliability Study, Western Kentucky University, 2001. Available from: (last access 2006).
24. B. Nixon, Dealing with performance requirements during the development of information systems, Proceedings of IEEE International Symposium on Requirements Engineering, pp. 42-49, 1993.
25. R.L. Nord, D. Soni, Experience with global analysis: a practical method for analyzing factors that influence software architectures, STRAW workshop 2003.
26. B. Nuseibeh, Weaving the Software Development Process Between Requirements and Architectures, STRAW workshop 2001.
27. Ramesh B., and Jarke M. Toward reference models for requirements traceability. IEEE Transactions on Software Engineering (2001) 58-93
28. L. Rapanotti, J. Hall, M. Jackson, B. Nuseibeh, Architecture-driven problem decomposition, in: Proceedings of 12th IEEE International Conference on Requirements Engineering (RE 2004), IEEE Computer Society, 2004, pp. 80-89.
29. P. Runeson, Using students as experiment subjects - an analysis on graduate and freshman student data, EASE'03, in: Proceedings 7th International Conference on Empirical Assessment & Evaluation in Software Engineering, 2003.
30. T. Silva, J. Castro, J. Mylopolous, Detailing Architectural Designing in the Tropos Methodology, STRAW workshop 2003.
31. Software Requirements to Architectures Workshop (STRAW), ICSE workshop, 2001 and 2003.
32. Sommerville I., and Sawyer P. Requirements Engineering: A Good Practice Guide (1997), John Wiley & Sons Ltd., New York
33. Thomas Thelin, Team-based fault content estimation in the software inspection process, in: 26th International Conference on Software Engineering (ICSE 2004), 2004, pp. 263-272.
34. Zave P. Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys 29 4 (1997) 315-321