The Community for Technology Leaders
RSS Icon
Issue No.11 - Nov. (2013 vol.46)
pp: 34-39
Jan Bosch , Chalmers University of Technology, Sweden
Increased system complexity has historically been treated as an inevitable consequence of architecture evolution over time. The three-layer product model offers an innovative framework for managing system growth that encourages greater efficiency, nimbler responsiveness, and more opportunities for innovation during all stages of the software development life cycle.
Software development, Complexity theory, Computer architecture, Computational modeling,software product management, software evolution, commoditization, software R&D, software life cycle, software architecture complexity, refactoring
Jan Bosch, "Achieving Simplicity with the Three-Layer Product Model", Computer, vol.46, no. 11, pp. 34-39, Nov. 2013, doi:10.1109/MC.2013.295
1. D.L. Parnas, “Software Aging,” Proc. 16th Int'l Conf. Software Eng. (ICSE 16), IEEE CS, 1994, pp. 279-287.
2. D.E. Perry and A.L. Wolf, “Foundations for the Study of Software Architecture,” ACM SIGSOFT Software Eng. Notes, vol. 17, no. 4, 1992, pp. 40-52.
3. J. Bosch, “From Software Product Lines to Software Ecosystems,” Proc. 13th Int'l Software Product Line Conf. (SPLC 09), ACM, 2009, pp. 111-119.
4. P. Bengtsson et al., “Architecture-Level Modifiability Analysis (ALMA),” J. Systems and Software, vol. 69 nos. 1-2, 2004, pp. 129-147.
5. J. Bosch, Design and Use of Software Architectures: Adopting and Evolving a Product Line Approach, Pearson Educational/Addison-Wesley, 2000.
6. K. M. Eisenhardt, “Building Theories from Case Study Research,” Academy of Management Rev., vol. 14, no. 4, 1989, pp. 532-550.
7. P. Reason and H. Bradbury-Huan eds., , SAGE Handbook of Action Research, 2nd ed., Sage, 2007.
8. M. Fowler et al., Refactoring: Improving the Design of Existing Code, Addison-Wesley, 1999.
111 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool