Architectural descriptions as boundary objects in system and design work

  • Authors:
  • Lars Pareto;Peter Eriksson;Staffan Ehnebom

  • Affiliations:
  • Chalmers, University of Gothenburg, Gothenburg, Sweden;Ericsson AB, Gothenburg, Sweden;Ericsson AB, Gothenburg, Sweden

  • Venue:
  • MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
  • Year:
  • 2010

Quantified Score

Hi-index 0.00

Visualization

Abstract

Lean and Agile processes have resolved longstanding problems in engineering communication by replacing document based communication with face-to-face collaboration, but do not yet scale to very large and heterogeneous projects. This paper proposes a compatible extension to lean and agile processes that addresses this limitation. The core idea is to adopt the view of documentation as boundary objects: shared artefacts that maintain integrity across a project's intersecting social worlds. The paper presents a case study, in which interviews with system engineers and designers were analysed to obtain requirements on an architectural description serving as boundary objects in a telecommunications project. The main result is a list of 18 empirically grounded, elementary requirements, worth considering when implementing lean and agile processes in the large.