Despite documented best practices and specialized tools, software organizations struggle to deliver quality software that is on time, within budget, and meets customer requirements. Managers seeking improved software project outcomes face two dominant software paradigms which differ in their emphasis on upfront planning, customer collaboration, and product documentation: plan-driven and agile. Rather than promoting one approach over the other, this research advocates improving software management practices by developing the organization’s ambidextrous capability. Ambidextrous organizations have the ability to simultaneously succeed at two seemingly contradictory capabilities (e.g. discipline and agility) which leads to enhanced organizational performance. Overall, this study asks the question: How can an ambidextrous perspective facilitate improvement in software practices? Driven by this question, and based on a two year action research study at a small software firm, TelSoft, the objectives of this research are to: 1. Identify dualities involved in improving software practices 2. Design interventions based on these dualities to improve software practices 3. Explore the process of becoming an ambidextrous software organization The resulting dissertation consists of a summary and four papers that each identify and address particular dualities encountered during software process improvement. The first paper asserts that both process-driven and perception-driven inquiry should be used during assessment of software practices, presents a model that shows how this combination can occur, and demonstrates the use of this model at TelSoft. The second paper explicates two theories for understanding and resolving issues in requirements engineering practice – repeat-ability and response-ability – and argues for the need to negotiate between the two. The third paper identifies a tension between managing legacy and current processes and proposes a model for software process reengineering, a systematic process for leveraging legacy processes created during prior SPI efforts. Finally, the fourth paper applies the theoretical lens of ambidexterity to understand the overall change initiative in terms of the tension between alignment and adaptability. The study used a variety of data sources to diagnose software practices, including semi-structured interviews, software process documents, meeting interactions, and workshop discussions. Subsequently, we established, facilitated, and tracked focused improvement teams in the areas of customer relations, requirements management, quality assurance, project portfolio management, and process management. Furthermore, we created and trained two management teams with responsibility for ongoing management of SPI and project portfolio management respectively. We argue that these activities improved software practices at TelSoft and provided a stronger foundation for continuous improvement. Keywords: Ambidexterity, software process improvement (SPI), action research, requirements engineering assessment, action planning, software process reengineering, software management.

Uma das grandes dificuldades do desenvolvimento de software é adequar, de forma sistemática, os esforços na resolução de problemas e nas melhorias dos processos internos aos objetivos do negócio. O Seis Sigma é uma metodologia estruturada que incrementa a qualidade dos processos e o alinhamento com as estratégias empresariais, proporcionando altos ganhos financeiros para quem o utiliza. Surgido inicialmente na manufatura, o Seis Sigma vem sendo aplicado também noutros setores. No desenvolvimento de software, o seu uso é ainda restrito, mas há indícios de que possa ser utilizado com o mesmo sucesso. O objetivo desta dissertação de mestrado é propor um roteiro específico para a implementação do Seis Sigma nas organizações desenvolvedoras de software. Além do levantamento teórico, foi realizado um estudo de casos múltiplos para analisar as razões da sua adoção, as modalidades de seu uso, os seus benefícios e as suas limitações para os processos de software. Os resultados observados mostram que o Seis Sigma pode ser aplicado total ou parcialmente na melhoria dos processos de software. Além disso, é necessário alguma customização nos processos do Seis Sigma convencional, uma vez que os projetos de melhoria podem estar orientados para novos produtos, novos clientes ou, ainda, que os trabalhos de desenvolvimento fiquem a cargo de novas equipes, que muitas vezes são terceirizadas. O trabalho conclui que o Seis Sigma pode contribuir efetivamente para a melhoria dos processos de software, independentemente da organização objetivar níveis superiores de maturidade. O estudo sugere também um roteiro específico, chamado SW-DMAIC, para a aplicação do Seis Sigma em empresas desenvolvedoras de software. Este roteiro é composto por três etapas: implementação da filosofia do Seis Sigma, reciclagem desta filosofia, quando necessário e execução de projetos específicos. / Aligning sistematically efforts to solve problems and improve the software process with business goals is one of the challenges of software development. Six Sigma is a structured methodology that increases the process quality and aligning with enterprise strategies, providing high financial returns for those who uses it. Firstly applied in manufacturing companies, Six Sigma has been applied in other sectors too. It is not widely used in the software companies yet, but there are already some successful cases. The main objective of this master degree dissertation is to propose a specific roadmap for the Six Sigma application at software companies. Besides the theoretical research, it is accomplished a multiple case study to analyze the adoption reasons, the modalities of the use, the benefits and the limitations of Six Sigma for the software processes. The observed results show that Six Sigma could be applied totally or partially for software process improvement. Therefore it is necessary some tayloring in the Six Sigma processes, because improvement projects could refer for new products or new customers or some of the development work is in charge of new teams, specially when they are a outsoursing. The work has concluded that Six Sigma could contribute indeed to software process improvement, independently the enterprise is going to reach higher level maturity. This study suggests also a specific three-stage-roadmap, called SW-DMAIC, for the Six Sigma application at software companies containing processes for implementation of Six Sigma?s philosophy, recycling this philosophy when it?s necessary and, execution of specific Six Sigma projects.

Um crescente número de empresas produtoras de software tem adotado um modelo organizacional de Fábrica de Software (FS), que facilita a terceirização por intermédio da segmentação das atividades e adoção de um sistema de produção mais flexível, dinâmico e controlado. Uma FS pode atender a múltiplas demandas de natureza e escopos distintos com o intuito de prover as necessidades específicas de cada cliente. Em face da diversidade e complexidade deste contexto, uma das questões principais a resolver é como mapear todos os processos envolvidos, identificando claramente o que, quem e, sobretudo como cada trabalho deve ser executado e controlado, visando o alinhamento dos processos à estrutura organizacional e conceitual de FS com foco nos processos de integração, alinhamento e reuso. Este estudo tem como objetivo mapear, definir, reestruturar e estabelecer processos de Fábrica de Software, conduzidos pelo método de pesquisaação em uma organização produtora de software do setor público, considerando seu contexto operacional, técnico e cultura organizacional. O desenvolvimento, execução, acompanhamento e resultados são descritos pelos ciclos da pesquisa-ação envolvendo o estudo de estruturas organizacionais, metodologias de desenvolvimento de sistemas, e mudanças organizacionais. Para isso foram definidas uma Estrutura Organizacional de Referência de FS, uma Arquitetura de Definição de Processos para FS e uma Metodologia de Desenvolvimento de Sistemas e Integração com foco organizacional, concebidos e desenvolvidos com base na literatura, experiência profissional e pesquisa empírica, que serviram como guia de condução da pesquisa-ação, culminando na associação do estudo empírico com o estudo teórico. As contribuições empíricas e teóricas geradas referem-se à melhoria dos processos organizacionais e operacionais de uma empresa de TI do setor público com base nos conceitos de FS. / A growing number of software producing companies have adopted an organizational model of Software Factory (SF), which facilitates outsourcing by segmenting activities and by adopting a more flexible, dynamic and controlled production system. A SF can serve the multiple demands of different nature and scopes with the purpose of providing each customers specific needs. Because of the diversity and complexity of this context, one of the main issues to be solved is how to map all the processes involved, clearly identifying what, who and mainly how each work must be executed and controlled, aiming at aligning the processes to the organizational and conceptual structure of SF focusing on the integration, aligning and reuse processes. The purpose of this study is mapping, defining, restructuring and establishing the Software Factory process, conducted by the action research method in a software producing organization of the public sector, considering its operational, technical and organizational culture context. The development, execution, follow-up and results are described by the action research cycles involving the study of organizational structures, system development methodologies and organizational changes. For this, a Reference Organizational Structure of SF, and Processes Definition Architecture for SF and a Integration System Development Methodology with organizational focus were defined, conceived and developed based on the literature, professional experience and empirical research, which served as a guiding line of the action research, peaking at the association of the empirical study with the theoretical study. The generated empirical and theoretical contributions refer to the improvement of the organizational and operational processes based on the SF concepts.

A maioria das micro e pequenas empresas (MPEs) de desenvolvimento de software brasileiras são voltadas para o desenvolvimento de software on-demand. Normalmente, essas MPEs têm dificuldades em formalizar um processo de software padrão. O presente trabalho de pesquisa tem por objetivo apresentar uma proposta de integração de modelos/normas de capacidade de processo com modelos de ciclo de vida de software, em um contexto de gestão de processos de negócio. Como resultado, obteve-se o modelo de gestão do processo de venda e desenvolvimento de software on-demand para MPEs (ProcSoftVD - Gestão), composto pelo método de melhoria de processo de software (ProcSoftVD - Melhoria) e pelo modelo de processo de venda e desenvolvimento de software on-demand para MPEs (ProcSoftVD). O método de melhoria de processo de software foi criado a partir de abordagens existentes e complementares, voltadas às MPEs. O ProcSoftVD foi originado com base no framework unified process, possibilitando a visualização do processo em duas perspectivas - fases e áreas de conhecimento, e nos modelos/normas de capacidade de processo CMMI-DEV e ISO/IEC 15504-5, elaborado em um processo iterativo e evolutivo de pesquisa-ação com a participação de duas MPEs. Um diferencial dessa proposta é a consideração de atividades de comercialização do software junto ao processo de desenvolvimento de software, o que auxilia na delimitação do escopo do projeto de desenvolvimento de software para um acordo contratual. Outro diferencial é o detalhamento das atividades do processo por meio de tarefas, sugestão de papéis desempenhados pelos responsáveis das atividades e disponibilização de templates com exemplos para cada um dos artefatos elaborados na execução da atividade. / The majority of the software development micro and small companies are turned to the development of on-demand software. Usually, for these small companies the formalization of a standard process for software development is very difficult. For that reason the goal of this research is to propose an integration of capability processes models/standards within software life cycle models, in a perspective of business process management. The main result of this research is a management model of selling and on-demand software development process, which embraces the software process improvement method and the selling and on-demand software development process model. The software process improvement method was build from complementary and existents tailored approaches for micro and small companies. The selling and on-demand software development process model was created based on the models/standards of process capability CMMI-DEV and ISO/IEC 15504-5 and on the unified process framework, allowing the process view from two perspectives - phases and knowledge areas. The model was elaborated in an iterative and evolutionary action-research process carried out within two micro and small companies. The originality of this proposal is the consideration of software sale activities jointly with software development process, assisting the scope delimitation of a software development project for contractual agreement. Other aspect of this research which makes it distinctive is the detail of the process activities by mean of tasks, suggestions of people roles for each activities and provision of templates with examples for each artifact created during the activities.

Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Software process definition requires choosing the process elements that appropriately fulfil the tailoring requirements, such as to prevent risks or to satisfy quality goals. The selection of appropriate process elements is usually done manually, making this process complex, time-consuming and error-prone. Our main objective is to define a systematic approach to tailor software process and a tool support to simplify and to support the tailoring process, improving the selection process of reusable process elements. A systematic approach was developed to tailor the software process based on software architectures and process lines. The approach selects the most appropriate elements of processes according to the tailoring requirements. A web tool was developed to support the use of the proposed approach. Aiming to illustrate the approach proposed in this paper, an case study and an experiment were conducted. The case study describe projects with different characteristics and consequently are different generated tailoring processes. With experiment can be noted that the Software Process Line helped mainly in the sequencing process, optimizing resources and improving management process. The use of architecture provided the retrieval of a set of activities that have been prioritized according to the characterization of the project, defining required and optional elements and the accretion of tailoring requirements. Facilitating thus the adequacy of the process used for different contexts of projects. We concluded that the approach aids process engineer to make decisions for selecting a set of process elements suitable to the tailoring requirements and to the project context. / Definição de processos de software requer escolher os elementos de processo que apropriadamente satisfazem os requisitos de adaptação, tais como a prevenção de riscos ou para satisfazer as metas de qualidade. A seleção dos elementos de processos adequados é geralmente feita manualmente, tornando este processo complexo, demorado e sujeito a erros. O principal objetivo é definir uma abordagem sistemática para adequar o processo de software e uma ferramenta de apoio para simplificar e apoiar o processo de adaptação, melhorar a seleção dos elementos de processos reutilizáveis. Foi desenvolvido uma abordagem sistemática para adequar o processo de software com base em arquiteturas de processo de software e linhas. A abordagem seleciona os elementos de processos mais adequados de acordo com os requisitos de adaptação. Uma ferramenta web foi desenvolvida para suportar o uso da abordagem proposta. Visando exemplificar a abordagem proposta neste trabalho, foram realizados um estudo de caso e um experimento. O estudo de caso descreve projetos com diferentes características, e, consequentemente são gerados diferentes processos adaptados. Com o experimento pode-se notar que as Linha de Processos de Software auxiliaram principalmente no sequenciamento do processo, otimizando os recursos e melhorando o gerenciamento do processo. A utilização da arquitetura proporcionou a recuperação de um conjunto de atividades que foram priorizadas de acordo com a caracterização do projeto, definindo elementos obrigatórios e opcionais e o acréscimo de requisitos de adaptação. Facilitando, desta forma, a adequação do processo utilizado para diferentes contextos de projetos. Conclui-se que a abordagem auxilia o engenheiro de processos a tomar decisões na seleção do conjunto de elementos de processos mais adequados as exigências de adaptação e contexto do projeto.

International Telemetering Conference Proceedings / October 23-26, 2000 / Town & Country Hotel and Conference Center, San Diego, California / The Capability Maturity Model (CMM) developed by the Software Engineering Institute is widely promoted as a method to help decrease the volume of error riddled and late software projects. Because of the projected benefits, the 96th Communications Group/SC (SC) at Eglin Air Force Base began an intensive software process improvement effort in late 1997. This effort was rewarded in September 1999 when the group achieved a CMM Level 2 software rating on its first attempt. As of December 1999, 68% of assessed organizations remained at Level 1 on their first or second assessment. The SC success was not only obtained on its first attempt, but also 11 months ahead of the industry standard. The Level 2 rating was accomplished in the volatile environment needed to support the test and evaluation mission. This environment includes frequent requirement changes, short notice modifications, and externally driven schedules. One reason this milestone was possible is close and direct involvement by management. This paper will present additional factors to implementing a successful software process improvement effort.

隨著資訊技術的崛起與發展，無論是政府、企業組織乃至於個人對於資訊系統的依賴愈大，軟體的功能變的愈多，整體的複雜度也日漸提高，相對於軟體品質也就越受重視。對企業而言，軟體是昂貴的物品，但開發的過程卻又很難預測時間與成本。所以如何進行軟體流程管理，進而提昇軟體品質，也就成為學者所熱衷的研究議題。美國國防部遂委託卡內基美隆大學軟體工程學院進行一項研究，用以提供成熟的軟體組織之指引架構（能力成熟度模式，Capability Maturity Model），自1991年推出後，歷經多次增修，為統合其他各式標準再推出CMMI(Capability Maturity Model-Integrated,能力成熟度整合模式)。 本研究延續李有仁（2004）之研究，針對台灣地區的資訊部門之能力成熟度，透過歷史資料的分析，找出長期被追蹤之組織，進行深入研究與探討。在本研究裡，除對CMM至CMMI的演進做闡述外，也整理了國內外數年對軟體流程管理之研究。此外透過本研究，研究者可以觀察到對台灣地區中的資訊部門進行長期追蹤，有哪些組織是逐步的改善；有哪些組織在過程中反而退步了。再針對兩類型之公司進行歷史問卷資料與訪談資料的整理分析，發現成長的公司與退步的公司，其最主要的差異實務層面在於組織架構、技術管理、文件、資源與人力訓練。因為組織是企業的根本，也就是企業的體質，一個企業如果在體質上出了問題，後續訓練的投入也就無以為繼，於是整體的表現就會不佳。研究結果提供給欲投入軟體流程管理之公司及相關研究者參考。 / In the wake of information technology（IT）, the government or business and even the individuals rely heavily on the information system. The more functions of software, the more complexity it has. The research about how to improve software quality through software process management has long been a hot topic. The U.S. Department of Defense commissioned Software Engineering Institute (SEI) at Carnegie Mellon University to develop a standard framework for software organization called Capability Maturity Model. Since it was announced in 1991 and revised many times, SEI released Capability Maturity Model Integrated that integrates other standards. This research extends Li’s 2004 study and examines the capability in MIS departments of Taiwanese top 1000 businesses. It discusses the evolution of CMM and CMMI, and reviews the literature about software process management. This research discovers improved and retrogressive organizations of software process management in Taiwan. It utilizes two sources of data, one is the historical questionnaire data and the other is the interview materials. It discovers that the most significant difference practices are in organizational structure, technology management, document, resource and training. Organization is the base of business, without the base, all the other work is meaningless.

Consumers demand new and innovative personal computing devices every 2 years when their cellular phone service contracts are renewed. Yet, a 2 year development cycle for the concurrent development of both hardware and software is nearly impossible. As more components and features are added to the devices, maintaining this 2 year cycle with current tools will become commensurately harder. This dissertation delves into the feasibility of simplifying the development of such systems by employing heterogeneous systems on a chip in conjunction with a retargetable compiler such as the hybrid computer retargetable compiler (Hy-C). An example of a simple architecture description of sufficient detail for use with a retargetable compiler like Hy-C is provided. As a software engineer with 30 years of experience, I have witnessed numerous system failures. A plethora of software development paradigms and tools have been employed to prevent software errors, but none have been completely successful. Much discussion centers on software development in the military contracting market, as that is my background. The dissertation reviews those tools, as well as some existing retargetable compilers, in an attempt to determine how those errors occurred and how a system like Hy-C could assist in reducing future software errors. In the end, the potential for a simple retargetable solution like Hy-C is shown to be very simple, yet powerful enough to provide a very capable product in a very fast-growing market.

Background. It is significant to constantly change and improve the software process to thrive in the software market with rapidly changing requirement and situation. However, very small entities(VSEs) have difficulties to adopt software process improvement that have played an important role in software market, because they usually have some unique characteristics, such as informal and fewer documents, tight budget, and less human resources. Therefore, we believe it is necessary to study factors that are crucial to successful conducting SPI, to help inexperienced VSEs with limited resource implement SPI with reasonable cost. Objectives. The overall aim of our research is to analyse critical success factors about successfully conduct software process improvement for Very Small Entities. The objectives are based on the aim as following: 1) Identifying the special characteristics of VSEs which related to conducting SPI, 2) Identifying the state-of-the-art critical success factors when VSEs conducting SPI both in literature and practice: verifying and prioritizing the factors, and 3) Investigating the strategies that VSEs can take in order to successfully implement SPI. Methods. In order to investigate the critical factors and barriers need to focus and avoid during the improvement, we implemented a systematic literature review as the first phase. Then a survey questionnaire as the second phase to validate the results gained from the systematic literature review through consulting industrial software engineers. Results. The final result includes 80 success factors which have been mentioned at least once in the primary studies, a few characteristics of VSEs and strategies for SPI in VSEs. Among the 80 factors, we chose 29 factors as CSFs that were mentioned more than three times, then selected the first 15 CSFs as survey questions material. Through the survey, we gathered the evaluation of all factors from two areas and some suggestion or opinion of SPI in VSEs, explained the 29 CSFs and two ranking tables about top factors from the SLR and the survey, discussed 14 CSFs from both ranking tables, then provided specific strategies for each of the common 8 factors. Conclusions. For helping VSEs that intend to conduct SPI with limited resources, we answered our research questions through SLR and Survey, found 29 state-of-the-art success factors of SPI in VSEs, ranked 15 of them and provided a description, discussion, and strategies. Selected and prioritised success factors would be supportive for VSEs to ration their budget. Furthermore, we hope we can inspire VSEs who are having trouble to implement SPI by providing strategies.

Diversos setores da economia tem alto grau de dependência de sistemas computacionais: telecomunicação, financeiro, infraestrutura, industrial dentre outros. Desta forma, a qualidade do software contido nestes sistemas é um ítem importante para o bom desempenho destes setores. A arquitetura de software é considerada fator determinante para a qualidade de software. Este trabalho estuda a maneira pela qual a arquitetura de software determina a qualidade do software produzido e as possibilidades de se obter os atributos de qualidade desejados através da especificação de uma arquitetura de software apropriada. O método de pesquisa se fundamenta na revisão da literatura e quatro abordagens para a especificação da arquitetura de software são consideradas: clássica, orientada a objetos, orientada a atributos e orientada a busca. A abordagem orientada a busca é um campo de estudo relativamente recente e os avanços realizados são reportados dentro da área de conhecimento denominada de Search Based Software Engineering. Esta área de conhecimento utiliza técnicas metaheurísticas para achar boas soluções para os problemas encontrados na Engenharia de Software. Uma das técnicas meta-heurísticas mais utilizadas, o algorítmo genético, é usada em uma aplicação cujo processo de design segue a abordagem orientada a busca. / Many sectors of economy depend highly on computing systems: telecommunication, finance, infrastructure, industrial, and others. Thus, the quality of software in these systems is an important item to achieve good performance in these sectors. The software architecture is considered one of the main factors that shape the software quality. This work studies the way software architecture determines the software quality and the possibilities to obtain the desired software quality attributes through specifying appropriate software architecture. The research method is based upon literature review and four approaches to software architecture design process are considered: classic, object oriented, attribute oriented and search oriented. The search oriented approach to software architecture design process is a relatively new field of study and advances are reported in a knowledge area called Search Based Software Engineering. This knowledge area uses metaheuristics techniques to find good solutions to problems found in software engineering. One of the metaheuristic technique most frequently used, the genetic algorithm, is used in an application that follows the search based approach.