Melhoria de processo de software (SPI) é uma prática de engenharia de software motivada pela necessidade de aumentar a qualidade e a produtividade no desenvolvimento de software. Um fato amplamente reconhecido é que a qualidade do produto de software pode ser, em grande parte, determinada pela qualidade do processo utilizado para desenvolvê-lo e mantê-lo. A avaliação do processo de software ajuda as organizações de software a amadurecerem seus processos, identificando problemas críticos para estabelecer prioridades de melhoria. Essa avaliação pode ser feita por meio da comparação do estado dos processos da organização em relação a um modelo de referência que estabeleça estágios de melhoria. Uma avaliação geralmente se baseia em um modelo de processo de software que fornece um roteiro para melhorias. Este trabalho tem como objetivo estabelecer uma abordagem que: (i) define um conjunto de modelos de abstração (metamodelos) de modelos de maturidade de processo de software para apoiar uma metodologia de avaliação/melhoria de processo de software com o objetivo de certificação; e (ii) permite avaliar os processos de uma organização em comparação com um modelo de maturidade por meio de transformações desses metamodelos. A abordagem é instanciada por meio de um estudo de caso utilizando os modelos MPS.Br e CMMI para exemplificar sua aplicação. Como resultado, é apresentado um comparativo entre as limitações encontradas nas metodologias encontradas na literatura e como a abordagem sugere superá-las. / Software process improvement (SPI) is a software engineering practice motivated by the need to increase the quality and productivity in software development. A fact widely recognized is that the quality of the software product can be largely determined by the quality of the process used to develop and maintain it. The assessment of software process helps software organizations to improve themselves, identifying their critical problems to establish priorities for improvement. This assessment can take place by comparing the state of the organization on their software processes to a reference model that shows stages of improvement in scales. An assessment is usually based on a software process model that provides a roadmap for improvement. This work aims to establish an approach that: (i) defines a set of abstraction models (metamodels) of software process maturity models to support an assessment/improvement methodology aiming software process certification; and (ii) evaluates the organization processes in comparison with the maturity models through transformations of those metamodels. The approach is instantiated through a case study using the MPS.Br and CMMI models to illustrate its application. As a result, a comparison between the limitations found in the methodologies identified in the literature and how the approach suggested overcome them is presented.

Die erweiterte CSP-CASL Syntax wird dazu verwendet, sowohl positive als auch negative Testfälle zu generieren. Auf diese Weise wird sichergestellt, dass erwartetes und unerwünschtes Verhalten in den Testfäallen enthalten ist. Ferner werden Testterminologien für die CSP-CASL Spezifikation beschrieben, welche Softwareverfeinerungen und Erweiterungen untersuchen. Anschliessend wird die formale Definition von Softwareeigenschaften verwendet, um die Wiederverwendbarkeit von Testbestandteilen zu überprüfen. Diese Definitionen beschreiben die grundlegenden Eigenschaften im vorgeschlagenen Produkt und Prozessqualitäts- Framework. Ferner wird die Möglichkeit untersucht, die vorgeschlagenen Formalismus für die Entwicklung eines CMMI Prozesskonformen Frameworks zu verwenden. Dabei werden die Kernaspekte des CMMI Prozessmodells berücksichtigt. Das CMMI Compliance Bewertungssystem wurde entwickelt, um den Grad der Konformit ät der eingesetzten Softwareentwicklungsmethoden mit formalen Methoden zu bewerten. Ein generischer Algorithmus wird vorgeschlagen, um das Compliance Level der CMMI Prozessfelder und ihrer Komponenten zu ermitteln. Das Framework wird durch ein Tool unterstützt. Dieses Tool erlaubt es, die theoretischen Aspekte der vorgeschlagenen Theoreme praktisch zu unterstützen. Die Verwendbarkeit des vorgeschlagenen Frameworks wird an einem Anwendungsbeispiel aus der Medizintechnik gezeigt. Im Rahmen dieser Arbeit wird das Verständnis der Anwendung von formalen Methoden auf das Organisatorische Prozessmodell CMMI erweitert. Das komplette Framework wird repräsentiert durch die formale Spezifikationssprache CSP- CASL sowie der Prozessmodell CMMI. Ähnliche Ergebnisse können auch mit anderen formalen Methoden und Prozessverbesserungsmodellen erzielt werden. Diese Forschungsarbeit dagegen bildet einen Startpunkt für eine Prozessmodellkonformit ät mit einen auf formalen Methoden basierenden Softwaresystems sowie deren Entwicklung und Wartung. / The proposed formalisms and the other properties of formal methods are used to propose a framework of CMMI process model compliance. The core aspects of the CMMI process model are the process areas. A process area is a collection of best practices in a selected area. The CMMI compliance grading scheme is developed to evaluate the level of compliance with formal method based software development. A compliance algorithm is proposed to evaluate the process model through the evaluation of its components. The CMMI process areas are evaluated with a proposed algorithm. The compliance evaluation result is presented in the thesis. The complete framework is supported with a developed tool. This tool allows us to practically support our theoretical concepts. As a proof of concept, we explore our proposed framework for a medical instrument development and maintenance. In this thesis, the understanding of formal methods applicability is extended to the organizational process model, CMMI. The complete framework is presented for a formal specification language, CSP-CASL and process model, CMMI. However, similar result can be achieved with other formal methods for the compliance of other process models. This research is a starting point of process model compliance with formal methods. This has significant potential to automate the achievement of process and product quality goals of software systems.

Melhoria de processo de software (SPI) é uma prática de engenharia de software motivada pela necessidade de aumentar a qualidade e a produtividade no desenvolvimento de software. Um fato amplamente reconhecido é que a qualidade do produto de software pode ser, em grande parte, determinada pela qualidade do processo utilizado para desenvolvê-lo e mantê-lo. A avaliação do processo de software ajuda as organizações de software a amadurecerem seus processos, identificando problemas críticos para estabelecer prioridades de melhoria. Essa avaliação pode ser feita por meio da comparação do estado dos processos da organização em relação a um modelo de referência que estabeleça estágios de melhoria. Uma avaliação geralmente se baseia em um modelo de processo de software que fornece um roteiro para melhorias. Este trabalho tem como objetivo estabelecer uma abordagem que: (i) define um conjunto de modelos de abstração (metamodelos) de modelos de maturidade de processo de software para apoiar uma metodologia de avaliação/melhoria de processo de software com o objetivo de certificação; e (ii) permite avaliar os processos de uma organização em comparação com um modelo de maturidade por meio de transformações desses metamodelos. A abordagem é instanciada por meio de um estudo de caso utilizando os modelos MPS.Br e CMMI para exemplificar sua aplicação. Como resultado, é apresentado um comparativo entre as limitações encontradas nas metodologias encontradas na literatura e como a abordagem sugere superá-las. / Software process improvement (SPI) is a software engineering practice motivated by the need to increase the quality and productivity in software development. A fact widely recognized is that the quality of the software product can be largely determined by the quality of the process used to develop and maintain it. The assessment of software process helps software organizations to improve themselves, identifying their critical problems to establish priorities for improvement. This assessment can take place by comparing the state of the organization on their software processes to a reference model that shows stages of improvement in scales. An assessment is usually based on a software process model that provides a roadmap for improvement. This work aims to establish an approach that: (i) defines a set of abstraction models (metamodels) of software process maturity models to support an assessment/improvement methodology aiming software process certification; and (ii) evaluates the organization processes in comparison with the maturity models through transformations of those metamodels. The approach is instantiated through a case study using the MPS.Br and CMMI models to illustrate its application. As a result, a comparison between the limitations found in the methodologies identified in the literature and how the approach suggested overcome them is presented.

The goal of master thesis "CMMI Certification for Software Development in Agile Environment" is CMMI quality model research with focus on software development in agile environment in the Siemens company. In the beginning CMMI model and Scrum methodics are introduced. The core of this thesis is focused on the current state analysis. Output of the analysis is a list of potential areas that are currently not compatible with quality model requirements. These areas are to be improved for the company to achieve the desired CMMI certification level. Possible improvements are introduced to the consultant. During the implementation part a web application is realized helping to remove most of the identified imperfections. Application benefit is objectively evaluated by an internal audit. The work includes discussion of possible further application development and quality model standard evolution in this company.

由於台灣的軟體廠商多屬中小企業，因此在軟體開發專案過程中，常受限於 時程、成本上的壓力，無法遵循標準的軟體開發流程，也無法將專案經驗累積成 為公司的知識庫。CMMI 是目前國際上被高度認同的軟體開發流程模式，對提升 軟體發展能力及改善軟體品質相當有助益，可協助組織達到降低成本、掌控開發 時程與確保品質等目標，因此本研究將以滿足CMMI 專案規劃的標準為目標，設 計專案管理的資料模型。 本研究將規劃合乎CMMI的企業專案管理資料模式，使其有系統地記錄專案在 規劃時期所產出的一些資料及文件。當進行新的專案時，藉由參考先前專案的文 件或數據，可使專案在初步估計的過程中更加的順利，透過累積專案經驗也可增 加整體專案成功的機率。 以下為本文各章節的簡介，在第一章中，將確定研究的背景、動機、及目的， 據此進行第二章的文獻探討，分析CMMI與PMBOK對專案管理各自規範的實務作 法。接著在第四章中，先將PMBOK專案規劃流程轉為資料模型，再以CMMI專案規 劃的觀點來檢驗，分析是否滿足其實務的作法。第五章將分析個案公司專案文件 與訪談的結果，最後，在第六章將對個案公司提出建議，並提出改良後的資料模 型。

The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.

The topic of the thesis is to analyze processes of the IT company developing tailored solution delivered as a project. Based on analyze the recommendation for more effective processes will be provided. Analyze of processes comply with CMMI standard with use of a PST (PIID and SCAMPI Tool) tool from Dr. Ralf Kneuper. The work describes CMMI standard and its use in process evaluation, an example is shown by using the PST tool in evaluation of processes particular IT company. There are proposed recommendations for improvement and process changes according the results of the process evaluation at the end of work. The part of work is introduction of the PST tool with Czech translation of selected process areas corresponding to the maturity level of processes that the analysis is focused.

The diploma thesis examines the influence of established quality management system to improve processes and to further improve the performance of selected company VHL Ltd. Related analyzes and their results are considered as the main goals of the thesis. The first theoretical part of the thesis compares current approaches to quality management and explains basic terms. Introduction to the practical part is the characteristic of the chosen company. Next step is analysis of the impact of the system's implementation and comparison to the precertification state. Analysis uses CMMI model for measuring the maturity of processes. The results of the analysis are used to additional process improvement based on potential improvement. Identified constraints, which are limiting higher business performance, will be subject of the design solution to overcome them. The greatest benefits of the thesis is practical application of the technique for increasing business performance and determining whether quality management system using ISO 9001 will improve the processes.

在軟體開發的過程中，有效的需求管理能促成高品質的軟體及管理。在CMMI中與需求管理有關的議題包括需求發展(Requirements Development)流程領域-屬於CMMI成熟度第三級，提供一些目標、執行方法(practices)和相關資訊作為指引，協助開發團隊發展顧客需求和產品需求。另一個相關議題-需求管理(Requirements Management) 流程領域，屬於CMMI成熟度第二級，可用於幫助需求管理的規劃與控制，建立追蹤機制，以及評估改變衝擊。 本篇論文以達成CMMI中需求發展和需求管理流程領域目標為前提，利用概念形成(Concept Formulation)和系統展示(System Representation)研究方法，並調適RUP中的需求工作流程(workflow)，最後發展出一個整合的需求管理架構-稱為IREQM(Integrated Requirements Management)，用於處理需求面的問題。本研究亦根據IREQM架構進行實作，發展出一套可協助軟體需求發展與管理的支援系統。最後，我們利用自我評鑑表，評估IREQM及依據IREQM實作的雛型系統與CMMI目標和執行方法相符的程度。 / Effective requirements management can help the software development process to ensure a high-quality software development and management process. In CMMI, the process area RD (Requirements Development) provides a set of goals, practices, and related features to develop customer and product requirements, and the process area REQM (Requirements Management) is to help establishing and appraising the quality of requirements management. Both issues are covered by the generic requirement management concerns. This study is conducted by the Concept Formulation and System Representation method to develop a systematic process to deal with the requirements issues in the software development process, in order to meet the RD and REQM goals in CMMI. The study proposes an integrated requirement management framework, called IREQM, tailored from the requirements workflow in RUP. A CMMI support system, to implement IREQM is established to facilitate the REQM and RD activities during the software development process. Finally, a self-appraisal checklist is used to evaluate the compliance of the IREQM framework and its implementation to the CMMI model.

Magistriniame darbe nagrinėjami CMMI for Development 1.2 ir ISO/IEC 15504 procesų gebėjimo ir brandos modeliai, sudaromas modelių bazinių elementų tarpusavio sąryšio nustatymo algoritmas, sudaromi bazinių elementų sąryšiai. Darbas taip pat apima ir ISO/IEC 15504 pirmo, antro ir trečio brandos lygių nustatymą pagal 2008 metų rudenį į standartą įtrauktą pakopinį programų kūrimo proceso vertinimo modelį. Gaunamas unikalus ir niekur nepublikuotas rezultatas – CMMI for Development 1.2 ir ISO/IEC 15504 brandos lygių palyginimas, kuris pasako organizacijos brandos įvertinimą pagal ISO/IEC 15504, kai yra žinomas (yra duotas) organizacijos brandos įvertinimas pagal CMMI arba nurodo, kokį tolimesnį programų kūrimo proceso vertinimo kelią pasirinkti, jei trūksta duomenų įvertinti ISO/IEC 15504 brandos lygį. / In Master paper there has been taken analysis of CMMI for Developement and ISO/IEC 15504 capability and maturity models, an algorithm of mapping basic elements of the models has been made, mapping of the basic elements of the models has been carried out. Paper also includes evaluation of ISO/IEC 15504 maturity levels(first, second and third) according to the new part of the ISO standard which have been added in the autumn of 2008. The result which has been obtained is unique and never published - the mapping of CMMI for Development 1.2 and ISO/IEC 15504 maturity levels. That mapping can either tell the organization maturity level in terms of ISO/IEC 15504 when maturity of the same organization in CMMI terms is known or suggest what way to choose to assess the organization maturity in case there are not enough data to tell the organization‘s maturity level in terms of ISO/IEC 15504.