Reference models developed for software process improvement (SPI) provide guidelines about what to do while assessing and improving the processes, but they do not answer the questions of how. There have been a number of studies that try to find effective and strategic implementation models or to identify factors that affect the SPI success. However, these studies do not provide answers to questions about the effect of these factors on SPI program duration or accelerated SPI studies. This study aims to investigate the factors that affect CMMI-based SPI duration. It consists of two phases: in the first phase, factors that influence SPI success are identified and hypotheses related to these factors are formulated based on the case studies published in the literature. In the second phase of the study, hypotheses are revised based on the results of the qualitative research conducted in seven companies, six of which have obtained CMMI-Level 3 certification as a consequence of their SPI effort. The study has shown that management commitment and involvement as well as process documentation have had a significant shortening effect on CMMI-based SPI duration, within the context of the studied cases. Software process improvement / CMMI / Success factors / Duration factors. Enter specific words or phrases that are listed in thesis.

Internet applications have been extended to various aspects of everyday life and offer services of high reliability and security. In the Academia, Internet applications offer useful tools for the remote creation of simulation models and real-time conduction of control experiments. The aim of this study was the design of a reliable, safe and secure software system for real time operation of a remote aero gas turbine, with the use of standard Internet technology at very low cost. The gas turbine used in this application was an AMT Netherlands Olympus micro gas turbine. The project presented three prototypes: operation from an adjacent computer station, operation within the Local Area Netwok (LAN) of Cranfield University and finally, remotely through the Internet. The gas turbine is a safety critical component, thus the project was driven by risk assessment at all the stages of the software process, which adhered to the Spiral Model. Elements of safety critical systems design were applied, with risk assessment present in every round of the software process. For the implementation, various software tools were used, with the majority to be open source API’s. LabVIEW with compatible hardware from National Instruments was used to interface the gas turbine with an adjacent computer work station. The main interaction has been established between the computer and the ECU of the engine, with additional instrumentation installed, wherever required. The Internet user interface web page implements AJAX technology in order to facilitate asynchronous update of the individual fields that present the indications of the operating gas turbine. The parameters of the gas turbine were acquired with high accuracy, with most attention given to the most critical indications, exhaust gas temperature (EGT) and rotational speed (RPM). These are provided to a designed real-time monitoring application, which automatically triggers actions when necessary. The acceptance validation was accomplished with a formal validation method – Model Checking. The final web application was inspired by the RESTful architecture and allows the user to operate the remote gas turbine through a standard browser, without requiring any additional downloading or local data processing. The web application was designed with provisions for generic applications. It can be configured to function with multiple different gas turbines and also integrated with external performance simulation or diagnostics Internet platforms. Also, an analytical proposal is presented, to integrate this application with the TURBOMATCH WebEngine web application, for gas turbine performance simulation, developed by Cranfield University.

Developing a large software system involves many complicated, varied, and inter-dependent tasks, and these tasks are typically implemented using a combination of defined processes, semi-automated tools, and ad hoc practices. Stakeholders in the development process --- including software developers, managers, and customers --- often want to be able to track the actual practices being employed within a project. For example, a customer may wish to be sure that the process is ISO 9000 compliant, a manager may wish to track the amount of testing that has been done in the current iteration, and a developer may wish to determine who has recently been working on a subsystem that has had several major bugs appear in it. However, extracting the software development processes from an existing project is expensive if one must rely upon manual inspection of artifacts and interviews of developers and their managers. Previously, researchers have suggested the live observation and instrumentation of a project to allow for more measurement, but this is costly, invasive, and also requires a live running project. In this work, we propose an approach that we call software process recovery that is based on after-the-fact analysis of various kinds of software development artifacts. We use a variety of supervised and unsupervised techniques from machine learning, topic analysis, natural language processing, and statistics on software repositories such as version control systems, bug trackers, and mailing list archives. We show how we can combine all of these methods to recover process signals that we map back to software development processes such as the Unified Process. The Unified Process has been visualized using a time-line view that shows effort per parallel discipline occurring across time. This visualization is called the Unified Process diagram. We use this diagram as inspiration to produce Recovered Unified Process Views (RUPV) that are a concrete version of this theoretical Unified Process diagram. We then validate these methods using case studies of multiple open source software systems.

Programinė įranga, skirta brandaus programų kūrimo proceso gerinimui ir vertinimui atlikti, kuriama pagal tam skirtus modelius. Populiariausi palaikomi modeliai yra CMMI arba ISO/IEC 15504 (SPICE). Kuriant CMMI modelį buvo panaudota ISO/IEC 15504 standarto patirtis. CMMI modelis turi ir pakopinį ir tolydinį vaizdavimą, todėl yra suderinamas su modeliu ISO/IEC 15504. Brandaus programų kūrimo proceso vertinimas vadovaujantis abiem minėtais modeliais turėtų užtikrinti didesnę vertinimo kokybę. Šiuo tikslu yra kuriamas įrankis, kurio pagalba sukauptus duomenis bus galima pritaikyti vertinimams pagal abu modelius. / Software development teams are confronted with difficulties such as incorrect planned financial and time resources, low product quality and disappointed client. To solve those problems there are methodic and tools to improve software process capability. Tools for software process capability maturity assessment and support are implemented by particular models. Basic supported models are CMMI and ISO/IEC 15504 (SPICE). CMMI model is based on ISO/IEC 15504 standard. CMMI and ISO/IEC 15504 models are compatible. Software process capability maturity assessment quality should increase by using both models together. Consequently was decided to develop a tool supporting two models – CMMI and ISO/IEC 15504.

Siekiant pagerinti kuriamų programinių produktų kokybę, IT įmonės taiko skirtingus proceso modelius. Populiariausi iš jų gebėjimo brandos modelis (CMMI) ir ISO 15504. Šie modeliai nusako, kas (kokie procesai) turi būti vykdoma brandžioje organizacijoje, tačiau neatsako į klausimą: kaip tai turi būti daroma. Komandinis programų kūrimo procesas (TSP) pateikia strategiją, kartu su procedūrų rinkiniu, skirtą disciplinuotų programų kūrimo metodų naudojimui komandos lygyje. Pagrindinė su TSP susijusi problema – oficialios dokumentacijos trūkumas. Pirmas darbo tikslas yra rekonstruoti TSP metodiką. Antras tikslas yra sukurti TSP diegimo metodiką. Pirmoje darbo dalyje yra aprašyta bendra TSP struktūra, TSP ryšys su asmeniniu programų kūrimo procesu (PSP) ir brandos modeliu CMMI. Antroje dalyje yra pateiktas rekonstruotas TSP modelis ir TSP diegimo metodika apibrėžtam projekto komandos tipui. / IT organizations use different models to guide their software process improvement efforts. The most popular are the Capability Maturity Model Integration for Software (CMMI-SW) and ISO 15504. Still these organizations often struggle with implementation details. Both the CMMI-SW and ISO 15504 describe what an organization at a high level of process maturity should be doing, but do not says how it should be implemented. The Team Software Process (TSP) provides a framework as well as a set of processes, procedures, guidelines, and tools for project teams to use in the mature software development process. The main problem of the Team Software Process is the lack of official documentation. So the first goal of this master thesis is to reconstruct TSP methodology. The second goal is to produce TSP implementation guide. This master thesis contains the main structure of the TSP, it’s relation with the Personal Software Process (PSP) ant the Capability Maturity Model (CMMI), reconstructed TSP model and TSP implementation guide for defined project team type.

En este trabajo de tesis se describirá una técnica de modelado centrado en mockups, introduciéndola primero con MockupDD Web. Luego de haber ejemplificado el desarrollo centrado en mockups para metodologías MDWE, se describirá un marco general para el modelado sobre mockups (lo que se referenciará como metodología MockupDD general) y una instanciación particular de esta metodología además de la ya presentada para la Web. Las principales contribuciones de la metodología MockupDD y sus especializaciones son: (1) Mejorar el workflow en cascada de las metodologías MDD tradicionales (en especial, aquellas MDWE) para permitir acortar las iteraciones y permitir a usuarios finales y clientes involucrados interactuar más rápidamente son el software generado, agilizando el proceso. (2) Mejorar la productividad en el modelado de aplicaciones a través de la técnica de modelado de aplicaciones sobre mockups reduciendo sus errores y tiempo requerido, como se mostrará luego en las secciones de validación (3) Introducir a clientes y usuarios finales en el proceso de desarrollo, utilizando artefactos de especificación de requerimientos de fácil comprensión para los mismos en lugar de conceptos de modelado comprensibles sólo para desarrolladores. En este contexto se utilizarán mockups y diferentes técnicas de anotación y especificación de requerimientos formales sobre los mismos. (4) La implementación de un lenguaje de modelado sobre mockups con diferentes vistas, satisfaciendo al mismo tiempo la necesidad de comprensión de requerimientos por parte de los usuarios finales y las capacidades técnicas requeridas por los desarrolladores. (5) Con ayuda de esta versatilidad del lenguaje y del uso de mockups (los cuales son comprensibles en su totalidad por usuarios finales), proveer un método de modelado más trazable desde el punto de vista de los requerimientos.

This study investigates software development process improvement approaches. In particular, the static process evaluation methodology proposed by S. G&uuml / ceglioglu is applied on the requirements analysis and validation process applied in Project X in MYCOMPANY and an improved process is proposed. That methodology is an extension of the ISO/IEC 9126 approach for software quality assessment, and is based on evaluating a set of well-defined metrics on the static model of software development processes. The improved process proposed for Project X is evaluated using G&uuml / ceglioglu&rsquo / s methodology. The applied and improved process measurement results compared to determine if the improved process is successful or not.

This thesis focuses on measurement based software process improvement, especially improvement of requirements change management process. The literature on software measurement is investigated, software process improvement methodologies are studied and requirements change management metrics are examined. Requirements change management process at a private company working in the defense industry is observed and metrics obtained from various tools have been aggregated. Moreover, an improvement proposal, which also simplifies collecting metrics, is presented for the requirements change management process. A tool is developed for evaluating the performance of the improvement proposal using event driven simulation method.

A construção de um software envolve alto grau de risco e exige do gerente muito planejamento para atender as estimativas orçamentárias e cumprir os prazos estipulados. No contexto dos processos de software, são escassos os recursos tecnológicos que permitam extrair conhecimento dos processos modelados nos PSEEs e apontem quais fatores provocam os maiores impactos no resultado final, fornecendo novas perspectivas para melhorar a gerência. Para suprir estas carências, é possível utilizar a simulação na obtenção de informações sobre as atividades do processo e a análise da sensibilidade na identificação das variáveis que influenciam de forma mais significativa nos resultados. Neste sentido, este trabalho propõe um modelo de simulador, integrado a uma ferramenta de apoio à gerência de projetos centrados em processos, que utiliza os dados da base do PSEE, oferece recursos para manipular os dados do processo de forma determinística ou estocástica (simulação), permite testar vários cenários e possibilita a análise de quais variáveis impactam de forma mais significativa no resultado final (análise da sensibilidade), antes de iniciar a execução das atividades. O desenvolvimento do modelo de simulador foi fundamentado nos conhecimentos adquiridos com a revisão sistemática dos trabalhos publicados sobre simulação nos últimos anos e também na avaliação comparativa dos recursos tecnológicos oferecidos pelas ferramentas identificadas nas publicações selecionadas na revisão. Os resultados obtidos com a implementação do modelo proposto, utilizando as informações de um estudo de caso real, modelado no WebAPSEE, forneceram informações que indicam melhorias em relação ao custo e ao tempo de desenvolvimento do processo em estudo, assim como a identificação da variável de maior sensibilidade, permitindo otimizar a execução destas atividades. / The construction of a software involves high degree of risk and requires of the manager a lot of planning to attend the budget estimates and meet deadlines. In the context of software processes, there are limited technological resources that allow the extract of knowledge of the processes modeled in PSEEs and indicate what factors cause the greatest impact on the final result, providing new opportunities to improve management. To overcome these deficiencies, is possible to use simulation to obtain information about the activities of the process and sensitivity analysis to identify the variables that most significantly influence the results. Thus, this work proposes a simulation model, integrated to a tool that support project management centered processes, which uses data from the base of the PSEE, offers resources to handle the process data in a deterministic or stochastic way (simulation), allows the testing of various scenarios and enables the analysis of which variables most significantly impact the final result (sensitivity analysis), before starting the execution of activities. The simulation model development was based on the knowledge gained with a systematic review of the papers on simulation in recent years and a comparative evaluation of technological resources offered by the tools identified in the selected papers in the review. The results obtained with the implementation of the proposed model, using the information in a real case study, modeled on WebAPSEE, provided information that indicates improvements in relation to the cost and time development of the process under study, as well as the identification of the variable with the greatest sensitivity, allowing to optimize the performance of these activities.

p. 1 - 119 / Submitted by Santiago Fabio (fabio.ssantiago@hotmail.com) on 2013-01-16T21:07:26Z No. of bitstreams: 1 ddddddd88.pdf: 358295 bytes, checksum: 08b0fc127bbc330b70652af8ce82b292 (MD5) / Made available in DSpace on 2013-01-16T21:07:26Z (GMT). No. of bitstreams: 1 ddddddd88.pdf: 358295 bytes, checksum: 08b0fc127bbc330b70652af8ce82b292 (MD5) Previous issue date: 2009 / Diante de diversos estudos que relacionam a qualidade do software à qualidade do processo que o gera e da crescente pressão do mercado de TIC (Tecnologia da Informação e Comunicação) pela criação de produtos qualidade com prazos e custos cada vez menores, as empresas produtoras de software passaram a investir na utilização de processos no desenvolvimento de softwares. Diversos padrões e modelos de qualidade foram criados e difundidos com foco na definição de processos, dentre eles os modelos de maturidade da capacidade CMM (Capability Maturity Model) e CMMI (Capability Maturity Model Integration), criados pelo SEI (Software Engineering Institute), que tiveram uma grande aceitação mundial. Em face desta realidade, a SUNAC/SDR (Superintendência de Negócio, Administração Tributária e Comércio Exterior/Salvador), regional do SERPRO (Serviço Federal de Processamento de Dados), conquistou em 2003 o nível dois do CMM e desde então trabalha no aperfeiçoamento do processo de desenvolvimento de software para atingir níveis superiores do modelo CMMI. A presente pesquisa explicita a percepção dos profissionais da SUNAC/SDR, que trabalharam nesta unidade no intervalo de ]2003 - 2008], sobre como a utilização dos modelos CMM / CMMI afeta a qualidade dos produtos gerados ao longo do ciclo de vida de desenvolvimento de software. Verificou-se que os profissionais perceberam a importância de utilizar um processo de desenvolvimento para a melhoria dos produtos gerados. Além disso, perceberam que houve melhoria nos produtos desenvolvidos por eles e também no produto final entregue ao cliente após a implantação do processo. / Salvador