A Business Maturity Model of Software Product Line Engineering

In the recent past, software product line engineering has become one of the most promising practices in software industry with the potential to substantially increase the software development productivity. Software product line engineering approach spans the dimensions of business, architecture, software engineering process and organization. The increasing popularity of software product line engineering in the software industry necessitates a process maturity evaluation methodology. Accordingly, this paper presents a business maturity model of software product line, which is a methodology to evaluate the current maturity of the business dimension of a software product line in an organization. This model examines the coordination between product line engineering and the business aspects of software product line. It evaluates the maturity of the business dimension of software product line as a function of how a set of business practices are aligned with product line engineering in an organization. Using the model presented in this paper, we conducted two case studies and reported the assessment results. This research contributes towards establishing a comprehensive and unified strategy for a process maturity evaluation of software product lines

An Organizational Maturity Model of Software Product Line Engineering

Software product line engineering is an inter-disciplinary concept. It spans the dimensions of business, architecture, process, and the organization. Some of the potential benefits of this approach include cost reduction, improvements in product quality and a decrease in product development time. The increasing popularity of software product line engineering in the software industry necessitates a process maturity evaluation methodology. Accordingly, this paper presents an organizational maturity model of software product line engineering for evaluating the maturity of organizational dimension. The model assumes that organizational theories, behavior, and management play a critical role in the institutionalization of software product line engineering within an organization. Assessment questionnaires and a rating methodology comprise the framework of this model. The objective and design of the questionnaires are to collect information about the software product line engineering process from the dual perspectives of organizational behavior and management. Furthermore, we conducted two case studies and reported the assessment results using the organizational maturity model presented in this paper

An approach to reconcile the agile and CMMI contexts in product line development

Software product line approaches produce reusable platforms and architectures for products set developed by specific companies. These approaches are strategic in nature requiring coordination, discipline, commonality and communication. The Capability Maturity Model (CMM) contains important guidelines for process improvement, and specifies "what" we must have into account to achieve the disciplined processes (among others things). On the other hand, the agile context is playing an increasingly important role in current software engineering practices, specifying "how" the software practices must be addressed to obtain agile processes. In this paper, we carry out a preliminary analysis for reconciling agility and maturity models in software product line domain, taking advantage of both.Postprint (published version

Software Reuse in Agile Development Organizations - A Conceptual Management Tool

The reuse of knowledge is considered a major factor for increasing productivity and quality. In the software industry knowledge is embodied in software assets such as code components, functional designs and test cases. This kind of knowledge reuse is also referred to as software reuse. Although the benefits can be substantial, software reuse has never reached its full potential. Organizations are not aware of the different levels of reuse or do not know how to address reuse issues. This paper proposes a conceptual management tool for supporting software reuse. Furthermore the paper presents the findings of the application of the management tool in an agile development organization

Identification of key process areas in the production on an e-capability maturity model for UK construction organisations

Uptake of e-procurement by construction organisations has been slow (Martin, 2008). Positive e-business achievements in other industries, point towards the potential for the construction industry to accomplish similar results. Since the Modernising Government White paper set targets through best value indicator BV157 for implementation in the public sector, Government has supported many initiatives encouraging e-procurement. These are based on documented efficiency and cost savings (Knudsen, 2003; Minahan and Degan, 2001; McIntosh and Sloan, 2001; Martin, 2008). However, Martin (2003, 2008) demonstrates only a modest increase in the uptake of e-procurement in the UK construction industry. Alshawi et al (2004) identified the significance of possessing a model to sustain the embedment of any business process within an organisation. Saleh and Alshawi (2005) describe a number of model types used to gauge maturity in an organisation. One of these models is the capability maturity model. Paulk et al (1993) released the Software Capability Maturity Model (CMM) in 1991. Since then many CMM’s have evolved. This paper reports on how a CMM based on Drivers and Barriers to e-procurement identified in Eadie et al (2009) can be developed to gauge the maturity of an organisation in relation to e-procurement. This paper presents details of a research project which used factor analysis to produce a set of Key Process Areas (KPA) from the drivers and barriers identified in Eadie et al (2009). These KPAs were then subjected to a mapping process linking them to maturity levels to develop a CMM to analyse the e-procurement capability of construction organisations. The mapping will be reported in a later paper. This termed as e-readiness of organisations will indicate the current state of a construction organisation in terms of its readiness to carry out e-procurement. The paper describes in detail the identification of the KPA’s