Skip to main content
Fachgebiete
Automobil + Motoren Bauwesen + Immobilien Business IT + Informatik Elektrotechnik + Elektronik Energie + Nachhaltigkeit Finance + Banking Management + Führung Marketing + Vertrieb Maschinenbau + Werkstoffe Versicherung + Risiko
DE
EN
Bücher
Zeitschriften
Themenseiten
Organisationspsychologie Projektmanagement Marketing Smart Manufacturing
Weitere Formate
Podcasts Webinare Technik Webinare Wirtschaft Kongresse Veranstaltungskalender Awards
Jetzt Einzelzugang starten
Zugang für Unternehmen
Referenzkunden
SLX-Digitalkonferenz: Zukunftswerkstatt 2024

Mehr Umsatz mit Top-Kontakten

Am 7. Mai erfahren Sie, wie Vertriebsteams Leadgenerierung, Leadnurturing und Leadstrategien effizient steuern können.
Erweiterte Suche
Anmelden
nach oben

2010 | Buch

Mobile Privacy Requirements on Demand Kapitel lesen Erstes Kapitel lesen

Product-Focused Software Process Improvement

11th International Conference, PROFES 2010, Limerick, Ireland, June 21-23, 2010. Proceedings

herausgegeben von: M. Ali Babar, Matias Vierimaa, Markku Oivo

Verlag: Springer Berlin Heidelberg

Buchreihe : Lecture Notes in Computer Science

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten
insite
SUCHEN

Über dieses Buch

On behalf of the PROFES Organizing Committee we are proud to present the proce- th ings of the 11 International Conference on Product-Focused Software Process Improvement (PROFES 2010), held in Limerick, Ireland. Since the first conference in 1999 the conference has established its place in the software engineering community as a respected conference that brings together participants from academia and industry. The roots of PROFES are in professional software process improvement motivated by product and service quality needs. The conference addresses both the solutions found in practice as well as relevant research results from academia. To ensure that PROFES retains its high quality and focus on the most relevant research issues, the conference has actively maintained close collaboration with industry and subsequently widened its scope to the research areas of collaborative and agile software devel- ment. The main themes of this year’s conference were “Agile and Lean Processes” and “Engineering Service-Oriented Systems. ” These two main themes enabled us to cover the contemporary software devel- ment demands and trends in a comprehensive manner and to tackle the most important current challenges identified by the software industry and software research com- nity––namely, the shift of focus from "products" to "services. ” The technical program featured invited talks, research papers, and experience reports on the most relevant topics related to processes for developing software-intensive services and products. In addition, a number of workshops and tutorials were hosted.

Inhaltsverzeichnis

Frontmatter

Keynote Addresses

Mobile Privacy Requirements on Demand
Abstract
Process and product improvements are noble goals. Structured, document-driven processes have played an important part in the development of some mission critical systems. Likewise, agile and lean development processes are showing increasing promise in competitive, changing environments. The ’software as a service’ paradigm is adding a further challenging dimension to the mix, and is redefining the notion of a software product.
Bashar Nuseibeh
Lean Development - Potentials, Principles and Practices
Abstract
To survive in a fast changing environment, we need to continuously improve productivity, reduce rework, and optimize product strategies. Lean development and lean management offers the right ingredients: Eliminating waste, empowering teams, delivering as fast as possible, seeing the whole. But there is a dark side, as recent industry experiences show. Too lean is mean. Lean often fails due to lack of vision, misalignment and insufficient execution. It is thus crucial for companies to successfully manage change towards lean development. This keynote will introduce to lean principles and practices. It will draw upon experiences from a variety of industries with topics such as lean transition, introducing new tools, improving engineering processes, and setting up a global software organization. A change check is provided so that participantscan address their specific challenges.
Dr. Christof Ebert

Software Quality Assurance I

A Qualitative Survey of Regression Testing Practices
Abstract
Aim: Regression testing practices in industry have to be better understood, both for the industry itself and for the research community. Method: We conducted a qualitative industry survey by i) running a focus group meeting with 15 industry participants and ii) validating the outcome in an on line questionnaire with 32 respondents. Results: Regression testing needs and practices vary greatly between and within organizations and at different stages of a project. The importance and challenges of automation is clear from the survey. Conclusions: Most of the findings are general testing issues and are not specific to regression testing. Challenges and good practices relate to test automation and testability issues.
Emelie Engström, Per Runeson
Investigating the Temporal Behavior of Defect Detection in Software Inspection and Inspection-Based Testing
Abstract
A major goal of analytical quality assurance (QA) activities, e.g., inspection and testing, is detecting defects in software artifacts to increase product quality and decrease rework effort and cost. Inspection aims at identifying defects early and traditional testing focuses on test case generation and execution late in the development process. Combining inspection and test-case generation to inspection-based testing (UBT-i) can help identifying defects early, increasing testability by systematically capturing requirements and quality attributes, and generating most valuable test cases based on inspection results. This paper reports on a controlled experiment to investigate the temporal behavior of UBR inspection and inspection-based testing regarding defect detection performance, i.e., effectiveness, efficiency, and false positives. Main findings of the study are that there are no significant advantages of UBR and UBT-i regarding defect detection performance and the temporal behavior of defect detection delivered contradictory results in two sessions of the study.
Dietmar Winkler, Stefan Biffl, Kevin Faderl
Analysis of Bug Fixing Processes Using Program Slicing Metrics
Abstract
This paper is a report of a feasibility study into an alternative assessment of software processes at the micro-level. Using the novel approach of applying program slicing metrics to identify bug characteristics, the research studied relationships between bug characteristics and their bug fixing processes. The results suggested that specific characteristics such as cyclomatic complexity may relate to how long it takes to fix a bug. Results serve as a proof of concept and a starting point for this proposed assessment methodology. Future refinement of the metrics and much larger sample data is needed. This research is an initial step in the development of assessment tools to assist with Software Process Improvement.
Raula Gaikovina Kula, Kyohei Fushida, Shinji Kawaguchi, Hajimu Iida

Agile Software Development

Systematic Piloting of Agile Methods in the Large: Two Cases in Embedded Systems Development
Abstract
Deploying agile methods in a large, diverse, geographically distributed setting is a challenging task. In this paper, we propose that systematic piloting is to be used in order to build experience and to overcome the most common challenges of agile deployment, such as resistance to change. We approach this by developing a method for piloting agile. This method is developed based on multiple-case study in a large embedded systems company. Based on two cases, we describe a method that transcends the encountered challenges and can help meld an agile method with a plan-driven organization.
Jeanette Heidenberg, Mari Matinlassi, Minna Pikkarainen, Piia Hirkman, Jari Partanen
Optimized Feature Distribution in Distributed Agile Environments
Abstract
In recent years, agile software development methods have gained increasing popularity. Distributed software development have been becoming a common business reality also. Software development organizations are striving to blend agile development methods like Scrum and distributed development to reap the benefits of both. However, agile and distributed development approaches differ significantly in their key tenets. While agile methods mainly rely on informal processes to facilitate coordination, distributed development typically relies on formal mechanisms. This paper aims at implementing modular design of software products to identify feature clusters that can be implemented co-located to minimize the communication needs between distributed teams. Presented method is evaluated with simulations that demonstrate how this method can produce 1) lower-risk feasible plans, 2) balanced workload on teams, and 3) provide higher quality feature distributions. Finally, the paper analyzes benefits and issues from the use of this method.
Ákos Szőke
Approaches to Agile Adoption in Large Settings: A Comparison of the Results from a Literature Analysis and an Industrial Inventory
Abstract
Nowadays the software industry is applying agile methods widely. However, there appears to be a lack of comprehensive guidelines and strategies addressing agile adoption. In addition, agile methods and practices often have to be tailored to be integrated into existing processes. In this study, agile adoption frameworks and strategies discussed in the literature, especially in the context of agile in the large, are analysed. The findings from the literature are validated by and compared to an industrial inventory. Based on the validation and the comparison, new approaches for agile adoption in large settings have been identified: incremental agile adoption approaches combining both bottom-up and top-down strategies; the important role of identified key practices that enable quick feedback and adaptation in the early adoption stages; and approaches derived from the multidimensional nature of agility. These approaches make possible to overcome the restrictions of conventional agile methods.
Anna Rohunen, Pilar Rodriguez, Pasi Kuvaja, Lech Krzanik, Jouni Markkula

Software Quality Assurance II

Applying DPPI: A Defect Causal Analysis Approach Using Bayesian Networks
Abstract
Defect causal analysis (DCA) provides a means for product-focused software process improvement. A DCA approach, called DPPI (Defect Prevention-based Process Improvement), was assembled based on DCA guidance obtained from systematic reviews and on feedback gathered from experts in the field. According to the systematic reviews, and to our knowledge, DPPI represents the only approach that integrates cause-effect learning mechanisms (by using Bayesian networks) into DCA meetings. In this paper we extend the knowledge regarding the feasibility of using DPPI by the software industry, by describing the experience of applying it end-to-end to a real Web-based software project and providing additional industrial usage considerations. Building and using Bayesian networks in the context of DCA showed promising preliminary results and revealed interesting possibilities.
Marcos Kalinowski, Emilia Mendes, David N. Card, Guilherme H. Travassos
Evaluating Three Approaches to Extracting Fault Data from Software Change Repositories
Abstract
Software products can only be improved if we have a good understanding of the faults they typically contain. Code faults are a significant source of software product problems which we currently do not understand sufficiently. Open source change repositories are potentially a rich and valuable source of fault data for both researchers and practitioners. Such fault data can be used to better understand current product problems so that we can predict and address future product problems. However extracting fault data from change repositories is difficult. In this paper we compare the performance of three approaches to extracting fault data from the change repository of the Barcode Open Source System. Our main findings are that we have most confidence in our manual evaluation of diffs to identify fault fixing changes. We had less confidence in the ability of the two automatic approaches to separate fault fixing from non-fault fixing changes. We conclude that it is very difficult to reliably extract fault fixing data from change repositories, especially using automatic tools and that we need to be cautious when reporting or using such data.
Tracy Hall, David Bowes, Gernot Liebchen, Paul Wernick
Regularities in Learning Defect Predictors
Abstract
Collecting large consistent data sets of real world software projects from a single source is problematic. In this study, we show that bug reports need not necessarily come from the local projects in order to learn defect prediction models. We demonstrate that using imported data from different sites can make it suitable for predicting defects at the local site. In addition to our previous work in commercial software, we now explore open source domain with two versions of an open source anti-virus software (Clam AV) and a subset of bugs in two versions of GNU gcc compiler, to mark the regularities in learning predictors for a different domain. Our conclusion is that there are surprisingly uniform assets of software that can be discovered with simple and repeated patterns in local or imported data using just a handful of examples.
Burak Turhan, Ayse Bener, Tim Menzies

Software Business

Business Value Is Not Only Dollars – Results from Case Study Research on Agile Software Projects
Abstract
Business value is a key concept in agile software development. This paper presents results of a case study on how business value and its creation is perceived in the context of agile projects. Our overall conclusion is that the project participants almost never use an explicit and structured approach to guide the value creation throughout the project. Still, the application of agile methods in the studied cases leads to satisfied clients. An interesting result of the study represents the fact that the agile process of many projects differs significantly from what is described in the agile practitioners’ books as best practices. The key implication for research and practice is that we have an incentive to pursue the study of value creation in agile projects and to complement it by providing guidelines for better client’s involvement, as well as by developing structured methods that will enhance the value-creation in a project.
Zornitza Racheva, Maya Daneva, Klaas Sikkel, Luigi Buglione
Critical Success Factors for Offshore Software Development Outsourcing Vendors: An Empirical Study
Abstract
CONTEXT – Offshore software development outsourcing is a contractual business of high quality software production with significant cost-saving.
OBJECTIVE – The objective of this research paper is to analyse the factors that influence software outsourcing clients in the selection of offshore software outsourcing vendors.
METHOD – We have performed questionnaire surveys with 53 experts. We asked the participants to rank each success factor on a five-point scale to determine the perceived importance of each success factor. Our survey included success factors identified in the previous findings of systematic literature review study.
RESULTS – Our study reveal both cost-saving and appropriate infrastructure as the most influential factors in the selection of outsourcing vendors. Our results also indicate that appropriate infrastructure, cost-saving and efficient project management are common success factors across different groups of practitioners.
CONCLUSIONS – Cost-saving and appropriate infrastructure should be considered as the prime factors in the selection process of software development outsourcing vendors.
Siffat Ullah Khan, Mahmood Niazi, Rashid Ahmad
Impact of Corporate and Organic Growth on Software Development
Abstract
Many small software companies grow in an organic and corporate manner. When growing, they have to make many organizational changes, mature their processes and adapt them to the rapidly growing customer base and product demands. This may be a challenging task bearing in mind the fact that software organizations lack guidelines for how to grow and mature their software processes in the context of business growth. In this paper, we map out one software company’s corporate and organic growth in the course of its historical events and identify its impact on the company’s software production processes and capabilities. We also list benefits, challenges, problems and lessons learned as experienced by the company studied. The paper rounds up with the suggestion for incorporating business growth elements into software process improvement models.
Natalja Nikitina, Mira Kajko-Mattsson

Software Systems

Prioritizing Countermeasures through the Countermeasure Method for Software Security (CM-Sec)
Abstract
Software security is an important quality aspect of a software system. Therefore, it is important to integrate software security touch points throughout the development life-cycle. So far, the focus of touch points in the early phases has been on the identification of threats and attacks. In this paper we propose a novel method focusing on the end product by prioritizing countermeasures. The method provides an extension to attack trees and a process for identification and prioritization of countermeasures. The approach has been applied on an open-source application and showed that countermeasures could be identified. Furthermore, an analysis of the effectiveness and cost-efficiency of the countermeasures could be provided.
Dejan Baca, Kai Petersen
Feedback in Context: Supporting the Evolution of IT-Ecosystems
Abstract
IT ecosystems consist of dynamically interacting subsystems, components, and services containing software. Companies provide parts of IT ecosystems, e.g. for airports, train stations, and shopping malls. Due to the complex interaction of subsystems, overall behaviour cannot be completely anticipated or engineered. IT ecosystems constantly evolve by adapting to new user requirements and to changes in their environment. On-going improvement requires feedback from users. However, feedback is not easy to get. This paper presents an approach facilitating feedback in context. It is gathered by mobile devices like Smartphones. Effective support for evolution needs to cover (1) identifying the component or subsystem a user wants to address, (2) the ability to send feedback at very low effort and cost, and (3) support for interpreting incoming feedback. We present an architecture, a framework, and an application example to put stakeholder feedback into context. Contextualized feedback supports providers in driving the IT ecosystem evolution.
Kurt Schneider, Sebastian Meyer, Maximilian Peters, Felix Schliephacke, Jonas Mörschbach, Lukas Aguirre
Comparing Agile Processes for Agent Oriented Software Engineering
Abstract
Multi-agent Systems are at the moment an important new paradigm in software development. Several methodologies have been proposed for developing systems within this approach. Besides new agile process have been proposed to be used combined with the meta-models of such methodologies. This paper studies how the use of one of those Agent Oriented methodologies following an agile process such as Scrum produces improvements in the time consumed in the development that could shorten the learning time. This may have as outcome the possibility of using smaller groups in development.
Alma M. Gómez-Rodríguez, Juan C. González-Moreno
Standardizing the Software Tag in Japan for Transparency of Development
Abstract
In this paper, we describe the Software Tag which makes software development visible to software purchasers (users). A software tag is a partial set of empirical data about a software development project shared between the purchaser and developer. The purchaser uses the software tag to evaluate the software project, allowing them to recognize the quality level of the processes and products involved. With Japanese government support, we have successfully standardized the software tag named Software Tag Standard 1.0, and have developed various associated tools for tag data collection and visualization. For its initial evaluation, the software tag has been applied to several projects. This paper also presents various activities aimed at promoting the use of the software tag in Japan and the world.
Masateru Tsunoda, Tomoko Matsumura, Hajimu Iida, Kozo Kubo, Shinji Kusumoto, Katsuro Inoue, Ken-ichi Matsumoto

Process Quality I

Discovering Software Process and Product Quality Criteria in Software as a Service
Abstract
SaaS (Software as a Service) has become one of the fastest-growing innovative fields of the IT sector. Yet, as any other software intensive organizations, SaaS providers also need to deliver the service quality they offer. And, although, today exist a multitude of software quality models, so far, a specific adaptation does not exist to the SaaS context. Therefore, we present the results of our research on discovering software process and product quality criteria in the SaaS scenario. We adopted a research methodology, including, domain analysis, stakeholders interviews and literature review to elicit quality criteria and a survey to validate and prioritize the identified criteria. Such a set of identified quality criteria may help service clients to select providers as well as serve as a basis for a mapping relevant software process areas and best practices in order to adapt existing capability/maturity models and standards to this specific domain.
Maiara Heil Cancian, Jean Carlo Rossa Hauck, Christiane Gresse von Wangenheim, Ricardo José Rabelo
A Maturity Model for IT Dependability in Emergency Management
Abstract
In many organisations a gap exists between IT management and emergency managemement. This paper illustrates how process improvement based on a maturity model can be used to help organisations to evaluate and improve the way they include IT dependability information in their emergency management. This paper presents the IDEM3 (IT Dependability in Emergency Management Maturity Model) process improvement framework which focuses especially on the cooperation between IT personnel, emergency managers, and users, to proactively prevent IT dependability problems when the IT systems are most critical in emergency situations. This paper describes the details of the framework, how the framework was developed and its relation to other maturity models in related fields.
Kim Weyns, Martin Höst, Yeni Li Helgesson
Dependency Analysis between CMMI Process Areas
Abstract
SPI and in particular CMMI is being widely use by several organizations to improve their product quality. However, the SMEs are reluctant in adopting it and in particular maturity level 2 of CMMI, because they think that achieving this level is too expensive and do not see a clear benefit on it. Our solution to captivate the interest of SMEs in CMMI is the anticipation of some process areas of maturity level 3 considered as a benefit by the organization and implement those process areas at the same time of maturity level 2 of CMMI. In this paper, we identify the dependencies among all the process areas of CMMI and between all the process areas of each maturity level. Our study was conducted to identify the impact on the dependencies of maturity level 2 when we introduce some process areas of maturity level 3 in the implementation effort.
Paula Monteiro, Ricardo J. Machado, Rick Kazman, Cristina Henriques

Software Measurement

Productivity Reanalysis for Unbalanced Datasets with Mixed-Effects Models
Abstract
Data analysis is a major and important activity in software engineering research. For example, productivity analysis and evaluation of new technologies almost always conduct statistical analysis on collected data. Software data are usually unbalanced because they are collected from actual projects, not from formal experiments, and therefore their population is biased. Fixed-effects models have often been used for data analysis though they are for balanced datasets. This misuse causes analysis to be insufficient and conclusion to be wrong. The past study[1] proposed an iterative procedure to treat unbalanced datasets for productivity analysis. However, this procedure was sometimes failed to identify partially-confounded factors and its estimated effects were not easy to interpret. This study examined mixed-effects models for productivity analysis. Mixed-effects models can work the same for unbalanced datasets as for balanced datasets. Furthermore its application is straightforward and estimated effects are easy to interpret. Experiments with four datasets showed advantages of the mixed-effects models clearly.
Sousuke Amasaki
SAS: A Tool for the GQM+Strategies Grid Derivation Process
Abstract
GQM+Strategies is an approach designed to help the software industry develop measurement programs that are aligned with business goals. The resulting structure, which aligns metrics (GQM goals) and business goals, is called a grid. Usefulness (quality) of the grids depends on how well the environment is characterized by the grid elements. Our research objective was to construct a tool which would support and improve the context/assumption definition and strategy selection activities of the grid derivation process. The constructive research work took place between two pilot applications of the GQM+Strategies approach. The first one identified key requirements, while the second one was used to test the tool. For the validation we used a questionnaire to assess practitioners’ feedback regarding usefulness of the tool. We augmented the GQM+Strategies toolbox with the SAS tool. The principles used to design the tool complement the grid derivation process and practices. Two industrial pilot applications of GQM+Strategies demonstrated the usefulness of the SAS tool.
Vladimir Mandić, Markku Oivo
Understanding the Influential Factors to Development Effort in Chinese Software Industry
Abstract
A good understanding of the influential factors to software development effort and further precise effort estimate are undoubtedly crucial to any cost-effective and controllable software development projects. In most effort estimation researches, a large dataset is always a necessary basis of estimation modeling, model calibration and method validation. Among them, different attributes and characteristics of project data will to a large extent affect the applicable scope of particular research result. This research aims to identify the factors that significantly influence development effort, and to investigate how the influence works in Chinese software industry. In this study, six factors and their relationships to development effort are analyzed, prioritized and discussed based upon the dataset recording 999 projects from 140 software organizations in China. In terms of our analysis and findings, some suggestions for effort estimation and control are extracted to assist software practitioners in coping with various types of software projects.
Mei He, He Zhang, Ye Yang, Qing Wang, Mingshu Li

Process Quality II

Lean Management of Software Processes and Factories Using Business Process Modeling Techniques
Abstract
The software industry is moving towards a software factory business model, usually involving several centres collaborating on company contracts. The expected benefits of using specialized teams at lower cost locations are increased productivity and reduced costs. The tasks of project and process management have as a consequence become more complex. Managing such large structures requires more collaboration in development processes to enable rapid reaction to project needs, and support for the variety of technologies, methods, and levels of quality required by the different projects. This situation demands new practices and management support tools. This paper presents Zentipede, a tool for software process management. Its focus is on lightening, or even automating, management tasks by using Business Process Management (BPM) techniques. The tool does not force any particular practice on a company, but encourages it to model the practices which will finally be automated. Also, it supports process-to-product traceability.
Javier Berrocal, José García-Alonso, Juan Manuel Murillo
Improving Efficiency of Change Impact Assessment Using Graphical Requirement Specifications: An Experiment
Abstract
Objective: Graphical requirements representation is often considered needed to advance model-driven development. Dedicated modelling languages include formalisms for graphically representing requirements, and together with new methods for structuring requirements, graphical modelling promises improvements such as more efficient change management. This paper examines whether the use of a graphical notation of a requirements affects the task of assessing the impact of a proposed change to a requirements specification.
Method: The efficiency of using a graphical requirements representation was examined through an experiment – using 18 student subjects. Time, perceived confidence and accuracy were measured as dependent variables.
Result: The results showed that using a graphical representation decreased the time required and increased the perceived confidence, but the accuracy decreased. However, the statistical analysis of the results showed that only the difference in time was significant. Furthermore, there was a large difference in variance within the dependent variables between the groups.
Niklas Mellegård, Miroslaw Staron
Vague Project Start Makes Project Success of Outsourced Software Development Projects Uncertain
Abstract
A definition of a project success includes at least three criteria: 1) meeting planning goals, 2) customer benefits, and 3) supplier benefits. This study aims to point out the importance of the definition of the project start, the project start date, and what work should be included in the project effort in order to ensure the supplier’s benefits. The ambiguity of the project start risks the profitability of the project and therefore makes project success at least from supplier’s point of view uncertain. Moreover, vague project start makes it more difficult to compare project management metrics, such as duration and effort, between projects. There is no clear definition for the project start either in literature or practice. Based on interviews, the definitions are provided for project start, project start date, and project start-up effort included in the project.
Paula Savolainen

Software Process Improvement

The Rosetta Stone Methodology – A Benefits Driven Approach to Software Process Improvement
Abstract
In response to the lack of a business-focused approach to software process improvement (SPI), the Rosetta Stone objective-driven SPI Methodology (RSM) has been developed which allows organizations to undertake SPI based on business-driven objectives using proven SPI methodologies. To demonstrate usefulness and practicality, the Rosetta Stone IGSI-ISM to CMMI Instance mapping (RS-ICMMI) is developed using a generic set of business objectives which are mapped to the CMMI (Staged) model using a modified version of GQM. This methodology and the RS-ICMMI instance have been validated by experts.
Fionbarr McLoughlin, Ita Richardson
Defining and Monitoring Strategically Aligned Software Improvement Goals
Abstract
Software engineers are always aiming at improving software processes and products. However, the adoption of these improvements on software organizations must be aligned to their strategic goals. Otherwise, these improvements may not improve the organization. However, to guarantee this alignment can be complex, since improvement initiatives would have to be planned and monitored considering aspects starting from strategic level and going all the way to the organization daily operations. Thus, this work presents an approach to define and monitor software improvement goals, which are decompositions of strategic goals and are related to software products or processes. Our approach comprises strategic, tactical and operational planning activities, always aiming at strategic alignment. As important tools to monitor the goals defined, software measurement and statistical process control are also considered. An infrastructure to monitor the goals is described, and also an experience of use of the approach at a Brazilian software development organization.
Andrea Oliveira Soares Barreto, Ana Regina Rocha
A Strategy for Painless Harmonization of Quality Standards: A Real Case
Abstract
Globalization, is pushing companies towards continuous improvement. Quality frameworks addressing SPI practices are classifiable in ones describing: “what” should be done (ISO9001,CMMI); “how” it should be done (Six Sigma, GQM). When organizations adopt improvement initiatives, many models may be implied, each leveraging best practices for addressing improvement challenges. This may generate confusion, extra effort and cost, as well as increase the risk of inefficiencies and redundancies. So, it is important to harmonize quality frameworks, i.e. identify intersections and overlapping parts and create a multi-model improvement solution. Our aim is to propose a Harmonization Process supporting organizations interested in introducing/improving SPI practices. We present: a what/what combination of ISO9001 and CMMI-DEVv.1.2 models in the direction from ISO-CMMI; and detail the what/how perspective by showing how GQM is used to define operational goals that address ISO9001 statements, reusable in CMMI appraisals. The harmonization process has been applied to a SME certified ISO9001:2000.
Maria Teresa Baldassarre, Danilo Caivano, Francisco J. Pino, Mario Piattini, Giuseppe Visaggio
Backmatter
Metadaten
Titel
Product-Focused Software Process Improvement
herausgegeben von
M. Ali Babar
Matias Vierimaa
Markku Oivo
Copyright-Jahr
2010
Verlag
Springer Berlin Heidelberg
Electronic ISBN
978-3-642-13792-1
Print ISBN
978-3-642-13791-4
DOI
https://doi.org/10.1007/978-3-642-13792-1

Premium Partner

    Bildnachweise