Software Architects in Large-Scale Distributed Projects: An Ericsson Case Study

IEEE Software

Volumn 33, Issue 6, 2016, Pages 48-55

  Britto, Ricardo ^a   Šmite, Darja ^a   Damm, Lars Ola ^b  

^a Blekinge Institute of Technology   (Canada)

^b ERICSSON RESEARCH   (Sweden)

Author keywords

global software engineering; large scale software development; software architects; software development; software engineering

Indexed keywords

SOFTWARE ARCHITECTURE; SOFTWARE ENGINEERING;

AGILE DEVELOPMENT; ARCHITECTURAL DECISION; CENTRALIZED APPROACHES; DEVELOPMENT PROJECT; DISTRIBUTED PROJECTS; GLOBAL SOFTWARE ENGINEERING; MONOLITHIC ARCHITECTURE; SOFTWARE ARCHITECTS;

SOFTWARE DESIGN;

EID: 84994469140     PISSN: 07407459     EISSN: None     Source Type: Journal    
DOI: 10.1109/MS.2016.146     Document Type: Article

References (20)

1. P. Kruchten, "The Architects - the Software Architecture Team," Proc. 1st Working IFIP Conf. Software Architecture (WICSA 99), 1999, pp. 565-583.
2. J.F. Hoorn et al., "The Lonesome Architect," J. Systems and Software, vol. 84, no. 9, 2011, pp. 1424-1435.
3. M.B. Romney, "The Software Architect," Comm. ACM, vol. 50, no. 5, 2007, pp. 75-81.
4. M. Fowler, "Who Needs an Architect?," IEEE Software, vol. 20, no. 5, 2003, pp. 11-13.
5. S. Sherman and I. Hadar, "Toward Defining the Role of the Software Architect," Proc. 8th Int'l Workshop Cooperative and Human Aspects of Software Eng. (CHASE 15), 2015, pp. 71-76.
6. P. Kruchten, "What Do Software Architects Really Do?," J. Systems and Software, vol. 81, no. 12, 2008, pp. 2413-2416.
7. A.B. Bondi, "The Software Architect as the Guardian of System Performance and Scalability," Proc. ICSE Workshop Leadership and Management in Software Architecture (LMSA 09), 2009, pp. 28-31.
8. A. Tang et al., "On the Responsibilities of Software Architects and Software Engineers in an Agile Environment: Who Should Do What?," Proc. 4th Int'l Workshop Social Software Eng. (SSE 11), 2011, pp. 11-18.
9. B. Correa, "How Are Architects Made?," IEEE Software, vol. 30, no. 5, 2013, pp. 11-13.
10. P. Clements et al., "The Duties, Skills, and Knowledge of Software Architects," Proc. 6th Working IEEE/IFIP Conf. Software Architecture (WICSA 07), 2007, pp. 20-22.
11. G. Booch, "The Architect's Journey," IEEE Software, vol. 28, no. 3, 2011, pp. 10-11.
12. F. Buschmann, "Value-Focused System Quality," IEEE Software, vol. 27, no. 6, 2010, pp. 84-86.
13. J. Lewis and M. Fowler, "Microservices: A Definition of This New Architectural Term," 25 Mar. 2014; http://martinfowler.com/articles /microservices.html.
14. M.E. Fagan, "Design and Code Inspections to Reduce Errors in Program Development," IBM Systems J., vol. 15, no. 3, 1976, pp. 182-211.
15. C.E. Ebeling, An Introduction to Reliability and Maintainability Engineering, 2nd ed., McGraw-Hill, 2009.
16. G. Hanssen et al., "Software Entropy in Agile Product Evolution," Proc. 43rd Hawaii Int'l Conf. System Sciences (HICSS 10), 2010, pp. 1-10.
17. ISO/IEC 25010:2011 - Systems and Software Engineering - Systems and Software Quality Requirements and Evaluation (SQuaRE) - System and Software Quality Models, Int'l Org. for Standardization, 2011; www.iso.org/iso/catalogue-detail.htm?cs number=35733.
18. J.Y. Bang et al., "How Software Architects Collaborate: Insights from Collaborative Software Design in Practice," Proc. 6th Int'l Workshop Cooperative and Human Aspects of Software Eng. (CHASE 13), 2013, pp. 41-48.
19. A. Balalaie, A. Heydarnoori, and P. Jamshidi, "Microservices Architecture Enables DevOps," IEEE Software, vol. 33, no. 3, 2016, pp. 42-52.
20. H. Mintzberg, Mintzberg on Management: Inside Our Strange World of Organizations, Free Press, 2007.