Toward defining the role of the software architect

Proceedings - 8th International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE 2015

Volumn , Issue , 2015, Pages 71-76

  Sherman, Sofia ^a   Hadar, Irit ^a  

^a UNIVERSITY OF HAIFA   (Israel)

Author keywords

communication; leadership; mentoring; soft skills; Software architect

Indexed keywords

COMMUNICATION; SOFTWARE ARCHITECTURE;

AGILE DEVELOPMENT METHODS; DEVELOPMENT PROCESS; HIGH-LEVEL DESIGN; LEADERSHIP; MENTORING; ONLINE SURVEYS; SOFT SKILLS; SOFTWARE ARCHITECTS;

SOFTWARE DESIGN;

EID: 84946036221     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/CHASE.2015.17     Document Type: Conference Paper

References (25)

1. M. R. McBride, "The software architect", Communication of the ACM, 2007, 50(5), p. 75-81.
2. B. Berenbach, "The other skills of the software architect", In Proceedings of the first international workshop on Leadership and Management in Software Architecture, 2008, p. 7-12
3. R. Van Ommerling, "Things to do in Denver when you're an architect" http://www.sei.cmu.edu/architecture/ThingsToDoInDenver.htm
4. P. C. Clements, R. Kazman, M. Klein, D. Devesh, S.Reddy, and P. Verma, (2007, January). "The Duties, Skills, and Knowledge of Software Architects", In WICSA, 2007, p. 20.
5. Cockburn, A. "The interaction of social issues and software architecture". Communications of the ACM, 1996, 39(10), p. 40-46
6. S. Sherman and N. Unkelos-Shpigel, "What Do Software Architects Think They (Should) Do?". In Advanced Information Systems Engineering Workshops, 2014, p. 219-225, Springer International Publishing.
7. B. Berenbach and L. Bass, "Leadership and management in software architecture". In Proceedings of the 2009 31st International Conference on Software Engineering: Companion Volume (pp. 474-475). IEEE Computer Society.
8. P. Clements, R. Kazman and M. Klein, "Working session: software architecture competence". In Software Architecture, 2007. WICSA 2007. The Working IEEE/IFIP Conference on (pp. 27-27). IEEE.
9. R. Ferrari, N. H. Madhavji and M. Wilding, "The impact of nontechnical factors on Software Architecture". In Proceedings of the 2009 ICSE Workshop on Leadership and Management in Software Architecture, p. 32-36, IEEE Computer Society.
10. L. Bass and B. Berenbach, "Leadership and management in software architecture", (LMSA 2008): A report on an ICSE workshop. ACM SIGSOFT Software Engineering Notes, 33(4), p. 27-29.
11. P. Kruchten, "What do software architects really do?" Journal of Systems and Software, 2008, 81(12), p. 2413-2416.
12. J. F. Hoorn, R. Farenhorst, P. Lago and H. Van Vliet, "The lonesome architect". Journal of Systems and Software, 2011, 84(9), p. 1424-1435.
13. D. Ameller, C. Ayala, J. Cabot, and X. Franch, "How do software architects consider non-functional requirements: An exploratory study". In Requirements Engineering Conference (RE), 2012, 20th IEEE International, pp. 41-50.
14. B.G. Tabachnick, and L.S. Fidell, Using Multivariate Statistics, Pearson, New Jersey; 2012 .
15. A. Strauss and J. Corbin "Grounded Theory Methodology: An Overview", In N.K Denzin,. and Y.S. Lincoln, (Eds.), Handbook of qualitative research, Thousand Oaks: Sage. 1994.
16. L. Xu, H. Ziv, D. Richardson and Z. Liu, "Towards modeling non-functional requirements in software architecture". In Early Aspects, 2005.
17. M. Glinz, "On non-functional requirements", In Requirements Engineering Conference, 2007. RE'07. 15th IEEE International, p. 21-26.
18. L. Bass, P. Clements and R. Kazman, "Software Architecture in Practice". 3rd ed., Addison-Wesley Professional, 2013.
19. L. Zhu and I. Gorton, "Uml profiles for design decisions and non-functional requirements", In Proceedings of the Second Workshop on Sharing and Reusing Architectural Knowledge Architecture, Rationale, and Design intent , 2007, p. 8, IEEE Computer Society.
20. D. Cook, "Architecture Evaluation and Review Practices", 2007. http://msdn.microsoft.com/en-us/library/bb896741.aspx. Accessed, February 2010.
21. M. A. Babar, L. Zhuand and R. Jeffery, "A Framework for Classifying and Comparing Software Architecture Evaluation Methods". Australian Software Engineering Conference, 2004, pp. 309-318.
22. S. Sherman, I. Hadar, E. Hadar, and J. J. Harrison Jr, "The Overall Value of Architecture Review in a Large Scale Software Organization", In Advanced Information Systems Engineering Workshops, 2011, p. 302-307.
23. B. Selic, "Agile Documentation Anyone?" IEEE Software, 2009, 26( 6), pp.11 - 12.
24. T.C. Lethbridge, S.E. Sim, and J. Singer, "Studying Software Engineers: Data Collection Techniques for Software Field Studies", Empirical Software Engineering, 2005, 10( 3), p. 311-341.
25. M. A. Babar and I. Gorton, "Software Architecture Review: The State of Practice". IEEE Computer, 2009, 42(7), p. 26-32