Harmonizing Improvement Technologies:

A Comparison between CMMI-ACQ and

ISO/IEC 12207:2008

Francisco J. Pino

1,3

, Maria Teresa Baldassarre

, Mario Piattini

Giuseppe Visaggio

and Danilo Caivano

IDIS Research Group, Electronic and Telecommunications Engineering Faculty

University of Cauca, Street 5 # 4 – 70 Popayán, Colombia

RCOST, Department of Informatics

University of Bari, Via E. Orabona 4, 70126, Bari, Italy

Alarcos Research Group – Institute of Information Technologies & Systems

University of Castilla-La Mancha, Paseo de la Universidad, 4, 13071, Ciudad Real, Spain

Abstract. Currently a great number of organizations are acquiring products and

services from suppliers and developing less and less of these products in-house.

The CMMI-ACQ and the ISO/IEC 12207:2008 are process reference model

that addressing issue related to software acquisition. With the aim of to offer

information on how the practices described in these two models are related, and

considering that the comparison is one specific strategy for the harmonization

of models, we have carried out a comparison of these two reference models. We

have taken into account the latest versions of the models. Furthermore, to carry

out this comparison in a way systematic, we defined a process for this purpose.

This work intends to support organizations which are interested in introducing

or improving their practices for acquisition of products and services using these

models.

1 Introduction

Software process improvement is a planned, managed and controlled effort which

aims to enhance the capability of the software development processes of an

organization [1]. It is significant to highlight that in a software process improvement

effort different types of models are involved. These include the process reference

model, the process assessment method and the model that guides the process

improvement [2]. According to [3] the purpose of the process reference models is to

provide the description of the processes (and their entities) that can be applied during

the acquisition, supply, development, operation and maintenance of software. These

models describe best practices which should be taken into account by organizations in

the acquisition, supply, development, operation and maintenance of software.

Now more than ever, many organizations are increasingly becoming interested in

the activities of software acquisition [4]. Currently, a great number of organizations

Pino F., Baldassarre M., Piattini M., Visaggio G. and Caivano D. (2009).

Harmonizing Improvement Technologies: A Comparison between CMMI-ACQ and ISO/IEC 12207:2008.

In Proceedings of the 4th International Conference on Evaluation of Novel Approaches to Software Engineering - Evaluation of Novel Approaches to

Software Engineering, pages 177-188

DOI: 10.5220/0001954301770188

 SciTePress

are acquiring products and services from suppliers and developing less and less of

these products inhouse. These organizations can be customers who need to perform

good practices to guarantee that the product and service purchased satisfy the defined

acceptance criterias. These organizations can also be suppliers that may act as a

customer when acquiring a product and service from another supplier.

Regarding the process reference model related to software acquisition, the

Software Engineering Institute –SEI– has recently developed the CMMI-ACQ [5],

and the International Standarization Organization –ISO– is addressing this issue in the

agreement processes category of ISO 12207:2008 [6]. Each model has got its own

structure, processes and entities of process for describing best practices in its scope of

aplication.

Given the present need to harmonize different improvement technologies [7] to

support organizations which are interested in introducing or improving their practices

for acquisition of products and services, it is important to have information on how

the practices described in these two models are related. In this sense, this paper

presents a comparison of the CMMI-ACQ and ISO/IEC 12207:2008 models.

According to [7] mapping is one of the most widely- used specific strategies for the

harmonization of models. We have taken into account the following considerations

for this comparison: (i) refer to the latest versions of the models, (ii) carry out

comparison at a low level of abstraction , and (iii) guide the comparison through a

well defined method. This work intends to support and guide a software organization

to integrate, manage, and align its activities of software acquisition using these

models.

The paper is structured as follows. The section 2 presents related works, and then

the general considerations for comparison are described. Section 4 presents the

comparison overview and describes the analysis of results. Lastly conclusions and

future work are set out.

2 Related Work

Literature presents some works that involve comparisons and mapping between

different processes models. Among these, those related to CMMI V1.1 and ISO 9001

are:

• In [8] a mapping between two models is described.

• In [9] a new model that integrates the content of these two models is introduced.

• In [10] a way for the transition from ISO 9001 to SW-CMM is defined.

• In [11] a comparison and a correspondence between ISO 9001 and SW-CMM are

shown.

In the same sense, the following studies regarding the integration of specific

assessment frameworks have been conducted:

• An analysis and comparison of ISO/IEC 15504:2004 and CMMI V1.1 for software

process assessment is presented in [12].

• An analysis of compatibility between SPICE and CMM is given in [13].

178

• In [3] the harmonization of CMMI V1.1 and ISO/IEC TR 15504-2:2002 is

presented.

• In [14] and [15] a definition of compatibility structures and comparison between

CMMI and SPICE is described.

The works that deal with the standards ISO/IEC 15504-2:2004 involve ISO/IEC

12207:2002 directly, because this latter standard is suggested by ISO/IEC 15504 as a

process reference model.

As it can be seen from the work presented above, the most used models in mapping

and comparisons are: ISO 9001, ISO/IEC 15504:2004 and CMMI V1.1. However, in

none of these comparisons the latest versions of these models are involved. Moreover,

from the analysis of these studies we have found that the process entities involved in

the comparisons or mappings are of high level abstraction (as examples, objectives,

outcomes or statements).

We have carried out a comparison between the last versions of models: ISO/IEC

12207:2008 [6] and CMMI-ACQ V1.2: 2007 [5]. For the development of our

comparison we have followed an well defined process, which we also used for other

comparisons that we have carried out (ISO 9001 to CMMI-DEV, and ISO 12207 to

CMMI-DEV [16]). We might add that the entities involved in the process of

comparison and subsequent mapping are: (i) activities and tasks for ISO/IEC 12207

and (ii) specific practices for CMMI-ACQ. These process entities are of low level

abstraction in the description of the processes or process areas.

A comparison at this abstraction level provides information about what activities

and tasks outlined in ISO/IEC 12207 give support to specific practices of CMMI-

ACQ. Furthermore, an analysis at this abstraction level can give directions about how

a model previously implemented in the organization (ISO 12207) can meet part of the

requirements to establish a new model (CMMI-ACQ). This could reduce the effort

and costs associated with the implementation of a new model, with reference to a

model already used in the organization.

3 General Considerations

After an analysis of the different related pieces of work mentioned in the previous

section, we have observed a constant relationship between some models of the SEI

and ISO. Table 1 shows a high-level relationship extracted from the structures of

these models and their comparisons.

Table 1. High-level relationship between some ISO and SEI standards.

SEI

CMMI-DEV and CMMI-ACQ

Generic Goals / Generic

Practices

Process Areas

ISO

15504-5

12207

Process

Performance of the process

15504-2

Process

Attribute

Institutionalization of the

capability of the process

179

As it arises from the table, the process areas of CMMI-DEV and CMMI-ACQ

models are closely related to the process reference models described in ISO/IEC

15504-5 [17] and ISO/IEC 12207 [6, 18]. Furthermore, generic goals and practices of

CMMI-DEV and CMMI-ACQ models are closely related to the process attributes

described in the ISO/IEC 15504-2 standard [19].

Based on the relationship offered in Table 1, the comparison between CMMI-ACQ

and ISO 12207:2008 must be carried out at the level of process performance, in other

words this comparison doesn’t involve goals and generic practices.

There follows a description of activities carried out to perform the comparison

between these two models. These activities are related to the process that we have

defined for the comparison of models. The purpose of this process is to provide a

guide with which to perform the comparison and mapping of different models step-

by-step. This process defines two roles: the performers and the reviewers of the

comparison, along with five tasks: (i) understanding models, (ii) designing the

comparison, (iii) carrying out the comparison, (iv) overview of comparison outcomes,

and (v) analyzing the comparison outcomes. This comparison process is part of a

methodology of harmonization and integration which we are currently developing.

3.1 Understanding Models

This task involves: (i) acquiring knowledge about the models to compare and (ii)

analyzing the structure of these models. In this sense, a description of CMMI-ACQ

and ISO/IEC 12207 is described in the next lines.

According to [5] the purpose of CMMI-ACQ is to provide guidance for the

application of CMMI best practices by the acquirer. Best practices in the model focus

on activities for initiating and managing the acquisition of products and services that

meet the needs of the customer. Although suppliers may provide artefacts which are

useful to the processes addressed in CMMI-ACQ, the focus of the model is on the

processes of the acquirer. CMMI-ACQ integrates bodies of knowledge that are

essential for an acquirer. It is a collection of best practices that is generated from the

CMMI Framework, which is the basic structure that organizes CMMI components

and combines them into CMMI constellations and models. Also in the framework is a

CMMI model foundation (CMF) which exists within the CMMI Framework, and it is

a skeleton model that contains each of the components that must be included in every

CMMI model [20].

As regards the CMMI-ACQ’s structure, it contains two main sections in its

description: (i) generic goals and practices, and (ii) process areas. Each process area is

defined in terms of the process entities: purpose, specific goals (required component),

specific practices (expected component). A required component describes what an

organization must achieve to satisfy a process area, and an expected component

describes what an organization may implement to achieve a required component.

On the other hand, according to [6] the purpose of ISO/IEC 12207 standard

(Systems and software engineering - Software life cycle processes) is to provide a

defined set of processes to facilitate communication among acquirers, suppliers and

other stakeholders in the life cycle of a software product.

180

With respect to the ISO/IEC 12207’s structure, the processes are grouped in

process groups, and each process is described in terms of the process entities:

purpose, outcomes, activities and tasks. The purpose and outcomes are a statement of

the goals of the performance of each process. The list of activities and tasks are

performed to achieve the outcomes.

3.2 Designing and Carrying out the Comparison

This task involves: (i) fixing the process entities to be compared, based on the

research needs, (ii) defining the comparison scale, and (iii) fixing the directionality of

the comparison.

This comparison should find activities which ISO/IEC 12207 and CMMI-ACQ

have in common, in order to define goals for a measurement plan using the Multiview

Framework [21]. To apply the Multiview Framework, the comparison should be done

at the level of: (i) the entity-specific practices for CMMI-ACQ and (ii) the entity

activity and tasks for ISO/IEC 12207. These entities describe specific practice or

activities that should be executed to obtain the intended product or service. Carrying

out the comparison using these entities allows identifying common activities found

(from now on called specific activities) in both CMMI-ACQ and ISO/IEC 12207. The

above-mentioned specific activities can not be found using entities as purpose,

outcomes or generic goals.

In order to express the degree of relationship between a Process from ISO/IEC

12207 and a Process area from CMMI-ACQ, we have defined a discrete scale (scale

of comparison). Each of the elements of the scale has been associated with a set of

numeric values which are described in terms of percentage. This scale is made up of

the following elements:

• Strongly related (86% to 100%),

• Largely related (51% to 85%),

• Partially related (16% to 50%),

• Weakly related (1% to 15%), and

• Non-related (0%).

The numeric values can be found by dividing the number of specific practices

(from a Process area of CMMI) that are related to activities (from a process of

ISO/IEC 15504) by the total number of specific practices defined in that Process area.

When a comparison involves process entities of low level abstraction it is relevant

to define the direction of the comparison (see a discusion of this issue in section 4.3).

The direction of this comparison is from ISO/IEC 12207 to CMMI-ACQ.

We have carried out the comparison by means of an iterative and incremental

procedure. It is iterative, because the execution (analyze and determine the

relationship of the process entities of ISO/IEC 12207 and CMMI) of the comparison

is carried out completely on one CMMI process area first, and then on the others in

turn. It is also incremental in the sense that the template comparison (which is the

product) grows and evolves with each iteration until it becomes the definitive one.

The roles were assigned, two people as performers of the comparison and two

reviewers.

181

4 Comparison Overview

Based on the general considerations of the comparison described in the previous

section, the degree of support of the CMMI process areas from the ISO 12007 process

is presented in Table 2.

Table 2. Overview of the comparison between ISO/IEC 12207 and CMMI-ACQ.

Causal Analysis and Resolution (CAR)

Configuration Management (CM)

Decision Analysis and Resolution (DAR)

Integrated Project Management (IPM)

Measurement and Analysis (MA)

Organizational Innovation and Deployment (OID)

Organizational Process Definition (OPD)

Organizational Process Focus (OPF)

Organizational Process Performance (OPP)

Organizational Training (OT)

Project Monitoring and Control (PMC)

Project Planning (PP)

Process and Product Quality Assurance (PPQA)

Quantitative Project Management (QPM)

Requirements Management (REQM)

Risk Management (RSKM)

Agreement Management (AM)

Acquisition Requirements Development (ARD)

Acquisition Technical Management (ATM)

Acquisition Validation (AVAL)

Acquisition Verification (AVER)

Solicitation and Supplier Agreement Development (SSAD

cquisition process

SLP L

Supply process

Life Cycle Model Management Process

LWWPP

Infrastructure Mana

ement Process

Pro

ect Portfolio Mana

ement Process

Human Resource Mana

ement Process

WPSW

Quality Management Process

Project Planning Process

WLP

Project Assessment and Control Process

WLPW

Decision Mana

ement Process

Risk Mana

ement Process

WW S

Confi

uration Mana

ement Process

Information Management Process

Measurement Process

Stakeholder Requirements Definition Process

stem Requirements Anal

sis Process

stem Architectural Desi

n Process

Implementation Process

System Integration Process

System Qualification Testing Process

Software Installation Process

Software Acceptance Support Process

Software Operation Process

Software Maintenance Process

Software Disposal Process

Software Implementation Process

Software Requirements Anal

sis Process

Software Architectural Desi

n Process

Software Detailed Desi

n Process

Software Construction Process

Software Integration Process

Software Qualification Testing Process

Software Documentation Mana

ement Process

Software Confi

uration Mana

ement Process

Software Qualit

Assurance Process

Software Verification Process

Software Validation Process

Software Review Process

PS PP

Software Audit Process

Software Problem Resolution Process

Domain Engineering Process

Reuse Asset Management Process

Reuse Program Management Process

Direction of the comparison: From ISO/IEC 12207 to CMMI-ACQ

Process entities for the comparison:

• For ISO/IEC 12207: Activities and tasks of the standard's processes.

• For CMMI: specific practices.

Research question:

• What activities and tasks of ISO/IEC 12207 can offer support to specific

practices

of CMMI?

• What ISO/IEC 12207's activities and tasks are strongly related with the support to

CMMI's specific practices?

Comparison goal: To determine which activities and tasks of ISO/IEC 12207 have

close relationship with some specific practice of CMMI. The goal is know which is

the degree of fulfilment of the specific practices of CMMI based on the activities

and tasks described in ISO/IEC 12207.

Scale of comparison:

• S - Strongly related (86% to 100%)

• L - Largely related (51% to 85%)

• P - Partially related (16% to 50%)

• W - Weakly related (1% to 15%)

• - Non-related (0%)

CMMI-ACQ

Agreement processes

(2 processes)

CMMI-ACQ

(6 New Process

areas)

CMMI Framework

(16 Process areas)

ISO/IEC 12207

System context processSoftware specific process

Software reuse

processes

(3 processes)

Project processes

(7 processes)

Technical processes

(11 processes)

Software Support

Processes

(8 processes)

Organizational Project-

Enabling Processes

(5 processes)

Software

Implementation

Processes

(7 processes)

We shall now go on to present a discussion and consideration of several issues

arisen during this work this work, such as: an analysis of the specific issues of

acquisition in both models and the lessons learned.

182

4.1 The Acquisition in both Models

The purpose of CMMI-ACQ is to provide guidance for the application of CMMI best

practices by the acquirer [5]. This model shows a viewpoint from the side of the

acquirer, so the focus of the model is on the processes of the acquirer. Supplier

activities are not addressed in this model. It was very important to keep this

perspective constantly in mind.

CMMI-ACQ contains 22 process areas. Of those, 16 are CMMI Model Foundation

(CMF) process areas. Six process areas focus on practices which are specific to

acquisition of both products and services, addressing:

• Agreement management (AM)

• Acquisition requirements development (ARD)

• Acquisition technical management (ATM)

• Acquisition validation (AVAL)

• Acquisition verification (AVER), and

• Solicitation and supplier agreement development (SSAD).

An analysis about the Agreement process group (labelled number 6.1 in the

standard) has been carried out. This process group defines the activities necessary to

establish an agreement between two organizations, and it defines two processes:

Acquisition and Supply. The purpose of the Acquisition Process is to obtain the

product and/or service that satisfies/satisfy the need expressed by the acquirer. The

purpose of the Supply Process is to provide a product or service to the acquirer that

meets the agreed requirements [6].

On analyzing the description of the Supply Process, a viewpoint from the supplier

is observed. This perspective is opposite to that described by the CMMI-ACQ. Taking

into account this consideration, it is observed that the Process Supply is not related to

the six process areas which focus on practices specific to acquisition as described by

CMMI-ACQ.

Based on the comparison carried out and the description of the Acquisition process

from ISO/IEC 12207 standard, a relationship between these processes is shown in

Fig. 1. The goal is to offer an overview to the acquirer of which processes are

involved in the acquisition.

4.2 Detail View for Acquisition

Table 3 shows a summary of the comparison carried out between the six specific

process areas of CMMI-AQC for the acquisition and the processes related to the

Agreement processes of ISO 12207. The degree of relationship presented between

process areas and process is only described in the direction from ISO 12207 to

CMMI. In others word, how the activities of processes of ISO 12207 support the

fulfilment of the specific practices of CMMI-ACQ. In Table 4 an example of a

detailed comparison between activities and tasks of a process from ISO/IEC 12207

and the Agreement Management process area from CMMI-ACQ is shown.

183

6.1.1 Acquisition

Process

7.2.4 Software

Verification Process

7.2.5 Software

Validation Process

6.4.2 System

Requirements Analysis

Process

7.2.7 Software Audit

Process

7.2.6 Software

Review Process

6.4.1 Stakeholders

Requirement Definition

Process

7.2.2 Software

Configuration

Management Process

7.2.8 Software

Problem Resolution

Process

Process of support

Process directly connected

6.1.1 Acquisition

Process

7.2.4 Software

Verification Process

7.2.5 Software

Validation Process

6.4.2 System

Requirements Analysis

Process

7.2.7 Software Audit

Process

7.2.6 Software

Review Process

6.4.1 Stakeholders

Requirement Definition

Process

7.2.2 Software

Configuration

Management Process

7.2.8 Software

Problem Resolution

Process

Process of support

Process directly connected

Fig. 1. Relationships among processes of ISO/IEC 12207 for Acquisition.

Table 3. Detailed view of the relationship for acquisition of ISO/IEC 12207 and CMMI-ACQ.

CMMI-ACQ

AM ARD ATM SSAD AVAL AVER

ISO

12207

Acquisition process

S 100% L 63% P 20% L 56%

Software Review Process

P 20% P 38%

Software Audit Process

P 25% P 20%

Stakeholder Req. Definition Process

P 50% W 11%

System Req. Analysis Process

P 25%

Validation Process

L 80%

Verification Process

P 50%

Degree of relation GENERAL

S 100% L 75% P 20% L 66% L 80% S 88%

Table 4. Detailed comparison between activities and tasks of Acquisition process of ISO 12207

and specific practices of Agreement management of CMMI-ACQ.

AGREEMENT MANAGEMENT - AM (Specific practices)

SP 1.1 Execute

the Supplier

Agreement.

SP 1.2 Monitor

Selected

Supplier Process

SP 1.3 Accept

the Acquired

Product

SP 1.4 Manage

Supplier

Invoices

6.1.1 Acquisition process (Activities)

6.1.1.3.1 Acquisition

preparation.

6.1.1.3.2 Acquisition

advertisement.

6.1.1.3.3 Supplier

selection.

6.1.1.3.4 Contract

agreement.

6.1.1.3.5 Agreement

monitoring.

Task 6.1.1.3.5.1 Task 6.1.1.3.5.1

6.1.1.3.6 Acquirer

acceptance.

Task 6.1.1.3.6.2

6.1.1.3.7 Closure. Task 6.1.1.3.7.1

Degree of relation (Direction ISO 12207 to CMMI)

100% (Fulfilment 4 of 4 Specific Practices)

184

For each process of ISO/IEC 12207 and process areas of CMMI-ACQ that have

some relationship, we have defined a detailed chart like Table 4.

In summary, there are 39 specific practices in 6 process areas (Agreement

management - AM, Acquisition requirements development - ARD, Acquisition

technical management - ATM, Acquisition validation - AVAL, Acquisition

verification - AVER and Solicitation and supplier agreement development - SSAD) of

CMMI-ACQ, of which 28 specific practices are related to one or more tasks or

activities of ISO 12207. So the degree of general relationship is 72% (28/39).

The specific practices that are not supported by the activities from ISO 12207 are:

• Acquisition requirements development - ARD, SP 2.2 Allocate Contractual

Requirements.

• Acquisition requirements development - ARD, SP 3.3 Analyze Requirements to

Achieve Balance

• Acquisition technical management - ATM, SP 1.1 Select Technical Solutions for

Analysis

• Acquisition technical management - ATM, SP 1.2 Analyze Selected Technical

Solutions

• Acquisition technical management - ATM, SP 2.1 Select Interfaces to Manage

• Acquisition technical management - ATM, SP 2.2 Manage Selected Interfaces

• Solicitation and supplier agreement development - SSAD, SP 1.1 Identify Potential

Suppliers

• Solicitation and supplier agreement development - SSAD, SP 2.2 Establish

Negotiation Plans

• Solicitation and supplier agreement development - SSAD, SP 3.1 Establish an

Understanding of the Agreement

• Acquisition validation - AVAL, SP 1.2 Establish the Validation Environment

• Acquisition verification - AVER, SP 1.2 Establish the Verification Environment

4.3 Lessons Learned

In a comparison at low level abstraction, the degree of relation, between a Process

from ISO/IEC 12207 and a Process area from CMMI-ACQ, depends on the direction

of the relationship. In others words, this relationship is not bi-directional. For

instance, Table 4 shows the next degree of relationship:

• Direction from ISO 12207 to CMMI: The degree of relation is 100% (S)

(Fulfilment 4 of 4 Specific Practices). As shown in the chart: 3 activities of this

process of ISO 12207 meet 4 specific practices of the 4 that this process area of

CMMI-ACQ has defined.

• Direction from CMMI to ISO 12007: The degree of relation is 43% (P) (Fulfilment

of 3 out of 7 Activities). As shown in chart 4, specific practices of this process area

meet 3 activities of the 7 that this process of ISO 12207 has defined.

With the early detailed comparisons between a process and a process area, an

analysis of the degrees of relationship in the comparison was conducted. According to

this analysis, we conclude that this degree is not always possible to establish in both

directions. In some cases, in a given direction it loses meaning. An example is shown

185

in Table 5. In this table it does not make sense to establish a degree of relationship in

the direction from CMMI to ISO 12007, because it is not correct to say that the

Software Audit Process has 100% of fulfilment if only the specific practices SP 1.3 of

ATM process area have been carried out. In these cases this row is labelled as Not

Applicable.

Table 5. Degree of relationship “Not Applicable” between activities from ISO 12207 and

specific practices from CMMI-ACQ.

ATM

(Specific practices)

SP 1.1 Select Technical Solutions for Analysis

SP 1.2 Analyze Selected Technical Solutions

SP 1.3 Conduct Technical Reviews

SP 2.1 Select Interfaces to Manage

SP 2.2 Manage Selected Interfaces

Degree of relation (Direction CMMI to ISO 12207)

Not Applicable

7.2.7

Software

Audit

Process

(Activities)

7.2.7.3.1 Process implementation.

7.2.7.3.2 Software audit.

Degree of relation (Direction ISO 12207-CMMI)

20% (Fulfilment 1 of 5 Specific Practices

)

Regarding to the comparison process, to follow an iterative and incremental

procedure to perform the comparison brought some advantages, for example:

• The performing of the comparison starts with a process area, to reduce the

complexity and scope of each iteration.

• Each iteration of comparison is short and provides feedback for the next iteration.

• There is an integration of the results of each iteration into the comparison final

report.

• With the design of the comparison the iterations can be carried out both

independently and in parallel.

• The complexity of each iteration is easier to manage.

5 Conclusions

In this work we have presented a comparison between two reference models: CMMI-

ACQ and ISO/IEC 12207:2008. To carry out this comparison in a way systematic, we

186

defined a process for this purpose. To follow this process has helped us to organize

and manage the work performed for comparison, with the aim of reduce the two types

of error in the comparisons described by Yoo in [9]. For increase the reliability of

results, this process proposes using pair review by the performers of the comparison

in the task carrying out the comparison, furthermore the reviewer of the comparison

validates the result and it resolves the divergences of the performers.

Taking into account the activities and tasks described by the processes of ISO/IEC

12207 for Acquisition and their relationship with six process areas focus on practices

which are specific to acquisition of CMMI-ACQ, we can observed that there is a

suitable support level to the process areas: Agreement Management, Acquisition

Verification, Acquisition Validation, Acquisition Requirements Development and

even to the process area of Solicitation and Supplier Agreement Development.

However it is low the support level to the Acquisition Technical Management.

We will use specific activities for the definition of goals for a measurement plan in

a software enterprise following the Multiview Framework. On the other hand,

currently we are working in the definition of a methodology to offer to companies a

strategy to harmonization and integration of process entities described by different

reference models. The comparison process described in this paper is a component of

this methodology of harmonization and integration.

Acknowledgements

This work has been funded by the projects: INGENIO (PAC08-0154-9262, JCCM of

Spain), ESFINGE (TIN2006-15175-C05-05, MEC of Spain). By the first author to the

research fellowships granted by JCCM and funded by European Regional

Development Fund (ERDF).

References

1. Krasner, H., Accumulating the Body of Evidence for the Payoff of Software Process

Improvement, in Software Process Improvement, R.B. Hunter and R.H. Thayer, Editors.

2001, Wiley-IEEE Computer Society. p. 519-540.

2. Pino, F., F. Garcia, and M. Piattini, Software Process Improvement in Small and Medium

Software Enterprises: A Systematic Review. Software Quality Journal, 2008. 16(2): p. 237-

261.

3. Rout, T. and A. Tuffley, Harmonizing ISO/IEC 15504 and CMMI. Software Process:

Improvement and Practice, 2007. 12(4): p. 361-371.

4. Weber, C., E.E.R. De Araújo, D. Scalet, E.L.P. De Andrade, A.R.C. Da Rocha, and M.A.

Montoni. MPS model-based software acquisition process improvement in Brazil. in

QUATIC 2007 - 6th International Conference on the Quality of Information and

Communications Technology. 2007. Lisboa, Portugal. p. 110-119.

5. SEI, CMMI for Acquisition, Version 1.2. Technical Report CMU/SEI-2007-TR-017. 2007,

Software Engineering Institute (SEI): Pittsburgh.

6. ISO, ISO/IEC 12207:2008 Systems and software engineering - Software life cycle

processes. 2008, International Organization for Standardization: Geneva.

187

7. SEI, Process Improvement in Multimodel Environments (PrIME Project). 2008.

8. Mutafelija, B. and H. Stromber, ISO 9001:2000 - CMMI V1.1 Mappings. 2003, Software

Engineering Institute - SEI. p. 1-31.

9. Yoo, C., J. Yoon, B. Lee, C. Lee, J. Lee, S. Hyun, and C. Wu, A unified model for the

implementation of both ISO 9001:2000 and CMMI by ISO-certified organizations. Journal

of Systems and Software, 2006. 79(7): p. 954-961.

10. Jalote, P., CMM in Practice: Processes for Executing Software Projects, in Infosys. 1999,

Addison-Wesley.

11. Paulk, M.C., A Comparison of ISO 9001 and the capability maturity model for software

(CMU/SEI-94-TR-12). 1994, Software Engineering Institute.

12. Wangenheim, C.G.v. and M. Thiry, Analysing the Integration of ISO/IEC 15504 and

CMMI-SE/SW Technical Report LPQS001.05E. 2005, Universidade do Vale do Itajaí -

UNIVALI: Sao José/SC, Brazil. p. 28.

13. Rout, T. SPICE and the CMM: is the CMM compatible with ISO/IEC 15504? in AquIS.

1998. Venecia, Italy. p. 12.

14. Lepasaar, M., T. Mäkinen, and T. Varkoi. Structural comparison of SPICE and continuos

CMMI. in SPICE 2002. 2002. Venicia, Italia. p. 223-234.

15. Foegen, M. and J. Richter, CMM, CMMI and ISO 15504 (SPICE), IT Maturity Services.

2003. p. 52.

16. Pino, F., M.T. Baldassarre, M. Piattini, and G. Visaggio. Relationship between maturity

levels of ISO/IEC 15504-7 and CMMI-DEV v1.2. in Software Process Improvement and

Capability dEtermination Conference (SPICE 2009). 2009. Turku, Finland. p. in press.

17. ISO, ISO/IEC 15504-5:2006(E). Information technology - Process assessment - Part 5: An

exemplar Process Assessment Model. 2006, International Organization for Standardization:

Geneva.

18. ISO, ISO/IEC 12207:2002. Information technology - Software life cycle processes. 2002,

International Organization for Standardization: Geneva.

19. ISO, ISO/IEC 15504-2:2003/Cor.1:2004(E). Information technology - Process assessment

- Part 2: Performing an assessment. 2004, International Organization for Standardization:

Geneva.

20. SEI, Introduction to the Architecture of the CMMI® Framework. TECHNICAL NOTE

CMU/SEI-2007-TN-009. 2007, Software Engineering Institute (SEI): Pittsburgh.

21. Ardimento, P., M.T. Baldassarre, D. Caivano, and G. Visaggio. Multiview framework for

goal oriented measurement plan design. in Fifth International Conference on Product

Focused Software Process Improvement—PROFES 2004. 2004. Nara, Japan. p. 159-173.

188