Organizing for software product line engineering

Software product line engineering is the discipline of engineering a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way. The organizational characteristics required to successfully carry out software product line engineering will vary according to an organization's needs. However in general competitive advantage in software product line engineering lies in an organization's capacity to learn and adapt its products accordingly. This paper presents the conditions for a learning organization from management theory and argues that these conditions must prevail for software product line engineering to succeed.

[1]  Peter M. Senge,et al.  Laws of the Fifth Discipline , 1990 .

[2]  C. Argyris.  Single-loop and double-loop models in research on decision making. , 1976 .

[3]  Linda M. Northrop,et al.  Adopting and Institutionalizing a Product Line Culture , 2002, SPLC.

[4]  John Storey,et al.  Human Resource Management: A Strategic Introduction , 1998 .

[5]  Paul Clements,et al.  Software product lines - practices and patterns , 2001, SEI series in software engineering.

[6]  O. Arshad,et al.  Measuring software reuse , 2002, IEEE Students Conference, ISCON '02. Proceedings..

[7]  Jan Bosch,et al.  Design and use of software architectures - adopting and evolving a product-line approach , 2000 .

[8]  David J. Miller,et al.  Configurations of strategy and structure: Towards a synthesis , 1986 .

[9]  Ali Mili,et al.  An integrated cost model for software reuse , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[10]  Henry Mintzberg.  Patterns in Strategy Formation , 1978, International Studies of Management & Organization.

[11]  Ali Mili,et al.  Toward an Engineering Discipline of Software Reuse , 1999, IEEE Softw..

[12]  Linda M. Northrop.  SEI's Software Product Line Tenets , 2002, IEEE Softw..

[13]  M.L. Griss,et al.  Software reuse architecture, process, and organization for business success , 1997, Proceedings of the Eighth Israeli Conference on Computer Systems and Software Engineering.

[14]  Alan Mumford,et al.  INDIVIDUAL AND ORGANIZATIONAL LEARNING – THE PURSUIT OF CHANGE , 1991 .

[15]  Steffen Thiel,et al.  Systematic Integration of Variability into Product Line Architecture Design , 2002, SPLC.

[16]  J. Burgoyne,et al.  The Learning Company , 1989 .

[17]  Hermann Kaindl,et al.  Reusing single system requirements from application family requirements , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[18]  P. Senge.  The fifth discipline : the art and practice of the learning organization/ Peter M. Senge , 1991 .

[19]  Juha Savolainen,et al.  Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line , 2002, SPLC.

[20]  David M. Weiss,et al.  Software Product-Line Engineering: A Family-Based Software Development Process , 1999 .

[21]  Hassan Gomaa,et al.  Reusable software requirements and architectures for families of systems , 1995, J. Syst. Softw..