Software architecting without requirements knowledge and experience: What are the repercussions?

Journal of Systems and Software

Volumn 81, Issue 9, 2008, Pages 1470-1490

  Ferrari, Remo ^a   Madhavji, Nazim H ^a  

^a UNIVERSITY OF WESTERN ONTARIO   (Canada)

Author keywords

Architectural assessment instrument; Architecture and requirements technology; Attribute Driven Design (ADD) method; Empirical study; Hiring and training; Quantitative and qualitative research; Requirements knowledge and experience; Software Architecture; Software engineering curriculum; Software quality

Indexed keywords

ARCHITECTURE; COMPUTER SOFTWARE SELECTION AND EVALUATION; PROCESS ENGINEERING; PROFESSIONAL ASPECTS; SOFTWARE AGENTS; TEACHING; TELECONTROL EQUIPMENT;

ARCHITECTURE DESIGNS; DEVELOPMENT PROBLEMS; DEVELOPMENT PROCESSES; EMPIRICAL STUDIES; FUTURE WORK; GRADUATE STUDENTS; HUMAN AGENTS; MIXED METHODS; PROJECT EXPERIENCES; QUALITATIVE ASPECTS; QUALITY SOFTWARE; QUANTITATIVE ANALYSIS; REQUIREMENTS KNOWLEDGE AND EXPERIENCE (RKE); SOFTWARE ARCHITECTING; SOFTWARE ARCHITECTURE (SA); SPECIFIC AREAS; SYSTEM ARCHITECTURES; UNDERGRADUATE (UG);

SOFTWARE ARCHITECTURE;

EID: 47549110929     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2007.12.764     Document Type: Article

References (51)

1. Bachmann, F., Bass, L., Klein, M., 2003a. Moving from quality attribute requirements to architectural decisions. In: Second International Workshop from Software Requirements to Architectures (STRAW '03), Portland, USA, pp. 122-129.
2. Bachmann, F., Bass, L., Klein, M., 2003b. Preliminary Design of ArchE: A Software Architecture Design Assistant. Technical Report, Software Engineering Institute, Carnegie Melon University, CMU/SEI-2003-TR-021 ESC-TR-2003-021.
3. Bass L., Clements P., and Kazman R. Software Architecture in Practice. second edition (2003), Addison-Wesley
4. Berander P. Using students as subjects in requirements prioritization. Proceedings 7th International Conference on Empirical Assessment & Evaluation in Software Engineering (2004), Keele University, Staffordshire, UK 95-102
5. Berg B.L. Qualitative Research Methods for the Social Sciences (2007), Pearson Allen & Bacon, Boston
6. Boehm B. Get ready for agile methods, with care. Computer 35 1 (2002) 64-69
7. Brandozzi, M., Perry, D.E., 2003. From goal-oriented requirements to architectural prescriptions: the preskriptor process. In: Second International Workshop from Software Requirements to Architectures (STRAW '03), Portland, USA, pp. 107-113.
8. Bredemeyer D., and Malan R. The role of the architect. Architecture Resources for Enterprise Advantage (2006), Bredemeyer Consulting
9. Campbell D.T., and Stanley J.C. Experimental and quasi-experimental designs for research. In: Gage N.L. (Ed). Handbook of Research on Teaching (1963), Rand-McNally, Chicago 1-76
10. Carmines E.G., and Zeller R.A. Reliability and Validity Assessment (1991), Sage Publications, Newbury Park
11. Carver, J., Jaccheri, L., Morasca, S., 2003. Issues in using students in empirical studies in software engineering education. In: Proceedings of the ninth International Symposium on Software Metrics (METRICS'03), Sydney, Australia, pp. 239-249.
12. Clements, P., Kazman, R., Klein, M., 2007. Working session: software architecture competence. In: Proceedings of the Working IEEE/IFIP Conference on Software Architecture (WICSA '07), Mumbai, India.
13. Creswell J.W. Research Design: Qualitative, Quantitative, and Mixed Methods Approaches (2003), Sage Publications, Thousand Oaks, CA
14. Curtis, B., Hefley, W.E., Miller, S.A., 2001. People Capability Maturity Model (P-CMM): Version 2.0. Carnegie Mellon Software Engineering Institute technical report, CMU/SEI-2001-MM-001.
15. De Vaus D.A. Analyzing Social Science Data (2002), SAGE Publishing Ltd, London
16. 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
17. Easterbrook, S.M., Yu, E., Aranda, J., Fan, Y., Horkoff, J., Leica, M., Qadir, R.A., 2005. Do viewpoints lead to better conceptual models? An exploratory case study. In: 13th IEEE International Requirements Engineering Conference (RE'05), Paris, France, pp. 199-208.
18. Egyed, A., Grunbacher, P., Medvidovic, N., 2001. Refinement and evolution issues in bridging requirements and architecture - the CBSP approach. In: First International Workshop from Software Requirements to Architectures (STRAW '01), Toronto, Canada.
19. Ferrari, R., Madhavji, N.H., 2006. Requirements-oriented problems while architecting: an empirical study. In: 12th Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ'06), Luxembourg, pp. 81-96.
20. Ferrari, R., Madhavji, N.H., 2007. Impact of Requirements Knowledge and Experience on Software Architecting: An Empirical Study. In: 6th Working IEEE/IFIP Conference on Software Architecture (WICSA '07), Mumbai, India.
21. Hall, B., 2004. Public Interest Anthropology (PIA), University of Pennsylvania. .
22. Hoest 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
23. IEEE SWEBOK, 2004. Guide to the Software Engineering Body of Knowledge: 2004 Version. IEEE and IEEE Computer Society project. .
24. In, H., Kazman, R., Olson, D., 2001. From requirements negotiation to software architectural decisions. In: Second International Workshop from Software Requirements to Architectures (STRAW '01), Toronto, Canada.
25. Kazman, R., Klein, M., Clements, P., 2000. ATAM: Method for Architecture Evaluation. Technical Report, Software Engineering Institute, Carnegie Melon University, CMU/SEI-2000-TR-004 ESC-TR-2000-004.
26. Kotonya G., and Sommerville I. Requirements Engineering - Processes and Techniques (1998), Wiley
27. Liu, WenQian, Easterbrook, S., 2003. Eliciting architectural decisions from requirements using a rule-based framework. In: Second International Workshop from Software Requirements to Architectures (STRAW '03), Portland, USA, pp. 94-99.
28. Liu, D., Mei, H., 2003. Mapping requirements to software architecture by feature-orientation. In: Second International Workshop from Software Requirements to Architectures (STRAW '03), Portland, USA, pp. 69-76.
29. Liu, L., Yu, Eric, 2003. From requirements to architectural design - using goals and scenarios. In: Second International Workshop from Software Requirements to Architectures (STRAW '01), Toronto, Canada.
30. Mason J. Qualitative Researching (1996), SAGE Publishing Ltd, London
31. Miller, J., Madhavji, N., 2007. The architecture-requirements interaction. In: 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 07), Mumbai, India, pp. 20-23.
32. Nord, R.L., Soni, D., 2003. Experience with global analysis: a practical method for analyzing factors that influence software architectures. In: Second International Workshop from Software Requirements to Architectures (STRAW '03), Portland, USA, pp. 34-40.
33. Nuseibeh, B., 2001. Weaving the software development process between requirements and architectures. In: Second International Workshop from Software Requirements to Architectures (STRAW '01), Toronto, Canada.
34. Poort, E.R., De With, P.H.N., 2004. Resolving requirements conflicts through non-functional decomposition. In: Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 04), Oslo, Norway, pp. 145-154.
35. Rapanotti, L., Hall, G., Jackson, M., Nuseibeh, B., 2004. Architecture-driven problem decomposition. In: Proceedings of the 12th IEEE International Requirements Engineering Conference (RE 2004), Kyoto, Japan, pp. 80-89.
36. Runeson, P., 2003. Using students as experiment subjects - an analysis on graduate and freshman student data. In: EASE'03 - Proceedings 7th International Conference on Empirical Assessment & Evaluation in Software Engineering, Keel, UK.
37. Schwanke, R., 2005. GEAR: a good enough architectural requirements process. In: 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 05), Pittsburgh, USA, pp. 57-66.
38. Shaw, M., 2003. Writing good software engineering research papers: minitutorial. In: Proceedings of the 25th International Conference on Software Engineering (ICSE 2003), Portland, USA, Tutorial Session, pp. 726-736.
39. Sheskin D.J. Handbook of Parametric and Non-parametric Statistical Procedures (2004), Chapman and Hall/CRC
40. Software Engineering, 2004. Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering. A Volume of the Computing Curricula Series, August 23, 2004, The Joint Task Force on Computing Curricula, IEEE Computer Society, Association for Computing Machinery.
41. Software Requirements to Architectures Workshop (STRAW), 2001 and 2003.
42. Sommerville I. Software Engineering. eigth ed. (2006), Addison Wesley
43. Thelin, Thomas, 2004. Team-based fault content estimation in the software inspection process. In: 26th International Conference on Software Engineering (ICSE 2004), Edinburgh, Scotland, pp. 263-272.
44. Tichy W.F., Lukowicz, Prechelt L., and Ernst A. Experimental evaluation in computer science: a quantitative study. Journal of Systems and Software January (1995) 1-18
45. Wang, Z., Sherdil, K., Madhavji, N.H., 2005. ACCA: an architecture-centric concern analysis method. In: 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 05), Pittsburgh, USA, pp. 99-108.
46. WebStat, 2000. School of Psychology, New England University. Available from: .
47. (WICSA '07), 2007. Working IEEE/IFIP Conference on Software Architecture, Mumbai, India.
48. Wieringa R.J., and Heerkens J. The methodological soundness of requirements engineering papers: a conceptual framework and two case studies. Requirements Engineering Journal 11 (2006) 295-307
49. Wildt A.R., and Ahtola O.T. Analysis of Covariance. Quantitative Applications in the Social Sciences Series #12 (1978), Sage Publications, Thousand Oaks, CA
50. Wohlin C., Hoest M., and Wesslen A. Experimentation in Software Engineering: An Introduction (2000), Kluwer Academic Publishers, Norwell, MA
51. Zave P. Classification of research efforts in requirements engineering. ACM Computing Surveys 29 4 (1997) 315-321