Do Architectural Knowledge Product Measures Make a Difference in GSD?
Author:
- Viktor ClercVCViktor Clerc
- 1 July 2009
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 382-387
Abstract
Architectural knowledge (i.e., architectural decisions and underlying rationale) is pivotal in grasping the level of quality of software architectures and the software products that implement these architectures. When the software products are developed in a global software development context, architectural knowledge becomes of even greater importance because it is needed to overcome challenges associated with global software development. We have performed research on a series of software product assessments to identify what key elements that constitute architectural knowledge are actually used in software products. In addition, we have determined whether a difference exists in the use of the key elements in products that were developed using GSD versus products developed using local, single site development. Our results do not show a significant difference between these two groups, but do point at a lack of both view-based architecture descriptions and of the description of solution fragments in products developed using GSD.Keywords
This publication has 15 references indexed in Scilit:
- The GRIFFIN Collaborative Virtual Community for Architectural Knowledge Management2010
- The Usefulness of Architectural Knowledge Management Practices in GSD2009
- In search of `architectural knowledge'2008
- Global Software Development: Are Architectural Rules the Answer?2007
- The Architect’s Mindset2007
- Can distributed software development be agile?Communications of the ACM, 2006
- IntroductionCommunications of the ACM, 2006
- Global Software Development Challenges: A Case Study on Temporal, Geographical and Socio-Cultural Distance2006
- Global Software Development Handbook2006
- Building Up and Reasoning About Architectural Knowledge2006