Reconciling Agility and Discipline in COTS Selection Processes

Navarrete, Fredy; Botella, Pere; Franch, Xavier

doi:10.1109/iccbss.2007.29

Cited by 6 publications

(4 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Because there is little existing theory on non-functional method quality, we have conducted our initial work by observing important factors in practices within existing software development methods. Similar general observations have also been made in other specific development domains such as product line development [23] and COTSbased development [14]. However, the observations are usually too high-level to be useful in validating fine-grained practice-level method chunks.…”

Section: Discussionsupporting

confidence: 71%

Situational Method Quality

Zhu

Staples

2007

IFIP — The International Federation for Information Processing

View full text Add to dashboard Cite

Abstract. Some overall method characteristics, such as agility and scalability, have become increasingly important. These characteristics are different from existing method requirements which focus on the functional purposes of individual method chunks and overall methods. Characteristics like agility and scalability are often not embodied in the function of a single method chunk but are instead reflected in constraints over one or more method chunks, connections between method chunks and cross-cutting aspects of the overall method. We propose the concept of method tactics, which are techniques for achieving certain method quality attributes. We identify a list of method tactics focusing on agility and scalability by considering factors that affect these quality attributes. We validate the feasibility of using method tactics by applying them to traditional software development method chunks and deriving practices for agile development. We examine the effectiveness of the tactics by comparing our derived practices with existing practices for agile development. The comparison results show that most of the derived practices are found in existing agile methods. We also identify new practices that may have potential for use in agile methods. The results demonstrate initial support for our proposal for the use of method tactics, and for the extraction or invention of further cross-cutting primitive method tactics for more flexible situational method engineering.

show abstract

Section: Discussionsupporting

confidence: 71%

Situational Method Quality

Zhu

Staples

2007

IFIP — The International Federation for Information Processing

View full text Add to dashboard Cite

show abstract

“…The CMMI-ACQ best practices description (current release 1.02, September 2007) is the successor to the SA-CMM model (although the SA-CMM model is still in use in many organisations). [6] This model is built on the older SA-CMM description, but provides a considerable improvement over this model. It was generated from the CMMI Architecture and Framework, an existing model that describes various aspects of lifecycle development of software [7].…”

Section: Cmmi-acqmentioning

confidence: 99%

Deriving Software Acquisition Process from Maturity Models—An Experience Report

Alfaraj

Qin²

2010

JSEA

View full text Add to dashboard Cite

The establishment of an existing practice scenario was an essential component in providing a basis for further research in the area of COTS software acquisition within the organisation. This report details the identification of means of describing the existing practice of software acquisition within an organisation and identification of models that could be used to present this view. The chosen best practices descriptions for the idealized model were maturity models, including SA-CMM, CMMI-ACQ, and ISO/IEC 12207. This report describes these models briefly and then describes the process of identifying the requirements for idealizing these maturity models into process frameworks that could be identified to actually business process models from a real organisation in order to identify gaps and optimizations within the organisation's realization of the best practices model. It also identified the next steps in identification of the theoretical best practice framework, which will involve translation of the model to YAWL Petri nets and simulation of the process in order to identify potential modelling flaws or issues with framework efficiency. Implications of the currently ongoing research include the identification and correspondence of specific tasks and activities from ITIL and CoBiT frameworks with the generic key process areas of software acquisition frameworks and identification of sufficiently detailed structural framework models for each level in order to identify appropriate frameworks for application even in cases where these frameworks were not explicitly identified by the organisation or the researcher.

show abstract

“…In some recent work [2] we have identified the most relevant processes that appear during COTS selection methods, we have decomposed these processes into tasks, and finally we grouped these tasks into five categories. We summarize the result in this section.…”

Section: The Activity Dimension In the Cots Selection Scopementioning

confidence: 99%

“…COTS-based systems require some specific software activities, and among them COTS components selection play a crucial role [14]. In some previous work [1,2], we studied some of the most widespread COTS selection methods (CARE [3], SCARLET [4], OTSO [5], EPIC Please use the fiJtlowingformat when citing this chapter:…”

Section: Introductionmentioning

confidence: 99%

Defining a Scope for COTS Selection Methods

Navarrete

Botella

Franch

IFIP — The International Federation for Information Processing

Self Cite

View full text Add to dashboard Cite

The specification of a methodology defines a set of procedures and techniques that are associated to a specific domain. As part of this specification, it is advisable to establish a scope that allows identifying the set of roles and activities that should be covered to develop a life-cycle for a specific domain. If such a scope is not clearly defined in a methodology, some problems may arise, e.g., the set of roles in charge of carrying out the processes may lack of coordination, cooperation, and communication during the development of the life-cycle for the domain. In the Commercial Off-The-Shelf (COTS) components selection domain, there are currently different methodologies which define procedures and techniques to select or to license a COTS component from the marketplace. The application of these COTS selection methods results in processes that are different from usual development ones, yielding to new activities and responsibilities that should be defined in a scope which covers the interactions of specialized roles. However it may be observed that these methods do not put emphasis neither on the identification of these roles, nor on their subsequent interactions, nor on their combination to form a selection team. Furthermore, activities differ from one method to another. The contribution of this work is to define a scope for COTS selection processes, identifying and defining the undertaken activities, the roles that take place, their interactions and their responsibilities, and to organize a life-cycle around them. We use a goal-oriented approach, the i* notation, and a framework to model the engineering process, the OPEN Process Framework (OPF), with the purpose of issuing a well-defined work team that can adapt itself to the internal processes of a particular organization.

show abstract

Reconciling Agility and Discipline in COTS Selection Processes

Cited by 6 publications

References 26 publications

Situational Method Quality

Situational Method Quality

Deriving Software Acquisition Process from Maturity Models—An Experience Report

Defining a Scope for COTS Selection Methods

Contact Info

Product

Resources

About