During a discussion with the head of the software infrastructure team about the need for software architecture practices at Temple-Inland Company, the manager responded by noting since the company is not a software development company “there are no real benefits to implementing software development practices in the company”. This is an approach taken by many companies whose software development activity is primarily undertaken to support business activities such as the case with manufacturing or financial companies. This paper examines the process of implementing software architectural practices into an organization. The information contained here should be useful to small startup software companies who might assume that it is too costly to incorporate software architectural practices into their current development process. This paper should also benefit large organizations who primarily view software as solutions for short term immediate support and not in terms longer term strategic goals. Software development teams with projects that suffer from cost overruns, scheduling problems and user dissatisfaction should also find this information useful. / text

ABSTRACT The Capability Maturity Model Integration, (CMMI) has been officially announced in 2002 by the Carnegie Mellon® Software Engineering Institute (SEI). The SEI¡¦s core purpose is to help organizations continuously carry on to improve their flow of software engineering capabilities and to appraise the maturity rank of contractor's organization. CMMI has provided an elastic framework to practice for the software project and to ensure the software quality. Due to CMMI does not limit the method of practice, but only defines the goal which must be achieved. Therefore, the different technique, organization, and work domain all may according to their characteristics to adjust their flow to comply with the CMMI requirement. Meanwhile it has already been generally valued and adopted by both of domestic and foreign companies. At present, there are 24 domestic companies have obtained the CMMI authentication. At the same time, the Government wants to promote the competitiveness of domestic software industry to the global information service market. During CMMI¡¦s promotion, she has aggressively offered all kind of policies and estimates to invest about seventy millions new Taiwan Dollars every year with the expectation to impel 50 third level of authentication in 2007; to achieve 100 third level in 2010 as well as 5 fifth level to encourage the domestic software organization to obtain the CMMI authentication. Obviously the software quality is now one of the key impetus of Taiwan industry and more over the most important development tendency and the critical technology to increase international competitive strength of Taiwan software industry in the future. The software flow improvement is the enterprise to guarantee the quality of their provided service/product. It is an important investment of competitiveness promotion which will involve the interference of the transformation of organization, the resistance of inside and outside staff etc., hence the organization must to have the commitment of policy, the intense attempt and the motive to invest the essential resources to determine the execution of software flow improvement, thus to guarantee the success of the software flow improvement. By analyzing the implemented benefits and the various difficulties of initial stages and common bitter experience in each domain flow of the 24 domestic CMMI certificated companies to make the case study of CMMI implementation to offer the reference templates of domestic enterprises which are now complying with CMMI or those plan to induct CMMI in the future. This research analyzed the substantive benefits of the domestic 24 CMMI certified companies from the six performances, such as customer, finance, the quality, the flow, the organization and the staff after carry out CMMI. We found the mostly positive confirmation after CMMI implemented. Yet comparing the performance of finance and the staff, with approximately 50% thought it revealed less distinguished deviation in either enhancing "the capability of commercial negotiation of project taken¡¨ or decreasing the bustle of team member after CMMI carry out. This article referred to the lesson learn of domestic enterprises which got the CMMI authentication inducting A + technology which was inducting CMMI and the local consultancy companies to collect the 35 usual problems of the 4 aspects of in the staff, the force team, the inside and outside resources, and the environment of organization. Also to procure 18 bitter experiences of domain flow of both maturity second level (ML2) and third level (ML 3) in specific tasks with the common troubles in general practices of A+ technology, as well as the difficulties in particular tasks under execution, then to analyze the change tendency of the various stages of CMMI to accumulate the valuable experience assets of the domestic enterprises to implement CMMI. In this research integrated the motives; the purpose; the flow and invested resources; the key successful factors; the frequent troubles and the solution, including the concrete effectiveness and the future plan of the 3 examples to be the important reference model for those enterprises are to conduct CMMI authentication and to effectively create the systemized software development / maintain flow to promote the project productivity, the competitiveness of organization and software quality. Keywords : CMMI (Capability Maturity Model Integration); The Improvement of Software Flow; Benefit appraisal

ITC/USA 2007 Conference Proceedings / The Forty-Third Annual International Telemetering Conference and Technical Exhibition / October 22-25, 2007 / Riviera Hotel & Convention Center, Las Vegas, Nevada / High speed digital recorders have revolutionized the way Major Range and Test Facility Bases collect instrumentation data. One challenge facing these organizations is the need for a validated process for the separation of specific data channels and/or data from multiplexed recordings. Several organizations within Eglin Air Force Base have joined forces to establish the requirements and validate a software process compliant with the IRIG-106 Chapter 10 Digital Recording Standard (which defines allowable media access, data packetization, and error controls mechanics). This paper describes a roadmap to standardizing the process to produce this software process, Data Overwriting and Filtering Application (DOFA).

Le croisement de concepts issus de la gestion des processus métier, des normes et standards qualité et de l'interopérabilité nous a permis de nous intéresser à l'organisation et l'intégration des processus métier d'entreprise, pour proposer une démarche de mise en place d'un référentiel qualité multi-vues.<br />Le but de notre travail est de montrer comment intégrer les processus métier d'une entreprise à l'aide d'un référentiel commun offrant différents points de vue. Cette démarche généralisable est appliquée à l'intégration de deux standards de qualité, ISO 9001v2000 et Capability Maturity Model Integration (CMMI), afin de générer un référentiel qualité multi\--vues permettant une certification relative aux deux normes. Ce référentiel prend en compte les chapitres imposés par ISO et les recommandations de CMMI. Dans le cadre de l'implémentation du référentiel, nous nous sommes intéressés à la définition d'une méthodologie d'estimation des délais et charges des projets informatiques afin de rationaliser ce processus critique pour l'entreprise. La mise en place de ce référentiel qualité s'accompagne de la définition d'une démarche assurant l'interopérabilité des processus définis avec ceux des clients et/ou partenaires.<br />Une méthodologie d'audit projet, un référentiel documentaire et un référentiel des compétences viennent compléter le travail déjà réalisé afin d'assurer l'implémentation et le respect du référentiel qualité.

Submitted by Daniella Sodre (daniella.sodre@ufpe.br) on 2015-03-09T13:01:43Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) TESE Celio Santana.pdf: 3246716 bytes, checksum: fed6ad56ad971be5c5b806d148b9a8c9 (MD5) / Made available in DSpace on 2015-03-09T13:01:43Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) TESE Celio Santana.pdf: 3246716 bytes, checksum: fed6ad56ad971be5c5b806d148b9a8c9 (MD5) Previous issue date: 2012-06-18 / Em 2009 a Associação para Promoção da Excelência do Software Brasileiro (SOFTEX1) publicou uma pesquisa indicando que 96% das empresas de software brasileiras eram pequenas e possuíam até 20 pessoas. Ainda que estas empresas empregassem 55,3% de toda mão de obra da área, elas respondiam por apenas 19% do faturamento do setor e por menos de 1% das exportações de software. A conclusão do diagnóstico aponta que essas empresas precisavam passar por reestruturações em seus processos para aumentar sua competitividade. Algumas dessas empresas buscaram essa melhoria partindo para programas de certificação de qualidade tais como o CMMI e MPS.BR. Este trabalho propõe avaliar a utilização de metodologias ágeis como direcionador de programas de melhoria de processo, com o objetivo de atingir níveis de maturidade em avaliações CMMI nível dois e MPS.BR nível F. Uma contribuição deste trabalho é gerar evidências empíricas sobre a adoção de métodos ágeis como política de melhoria de processo em empresas de vida real no Brasil. Assim, esta pesquisa foi realizada para responder as seguintes questões de pesquisa: QP1 –É possível executar programas de melhoria de processo de software baseados em métodos ágeis com o objetivo de certificação CMMI nível dois e MPS.BR nível F? QP2 – Quais os benefícios observados por estas organizações ao se adotar a melhoria de processo baseada em métodos ágeis? E em longo prazo? QP3 – Como a melhoria de processo ágil está relacionada à melhoria de processo prescritivaadotada pelo CMMI e MPS.BR. Esta tese resume quatro anos de pesquisa em oito pequenas e médias empresas Brasileiras. Os métodos utilizados para a pesquisa foram: (i) estudo de caso baseado em avaliações de 3º pessoa registradas em planilhas para responder a QP1; (ii) surveys e (iii) teoria fundamentada em dados foi utilizada para responder as questões QP2 e QP3.

The aim of this thesis "Analysis of the project management in practice using project maturity models is to assess the project maturity level of a Czech company providing management consulting, technology and outsourcing services for telecommunication, banking and insurance sector across Central Europe region. Theoretical part is focused on selection and analysis of proper methodology. Practical part applies the chosen methodology Portfolio, Programme and Project Management Maturity Model to Cleverlance Enterprise Solutions Inc. Company. Based on results received during project management maturity evaluation, a set of recommendation is proposed in order to increase the project maturity level.

Made available in DSpace on 2016-03-15T19:37:56Z (GMT). No. of bitstreams: 1 KHAOHUN SHIA.pdf: 2242262 bytes, checksum: 97a46586e1ac55fd1097f77a932ad878 (MD5) Previous issue date: 2015-08-25 / In a competitive market of software, companies seek an agile development process with quality. Faced with this challenge, the companies target is a certification to prove the ability to produce a high quality product by following a defined process, for example, Capability Maturity Model Integration for Development (CMMI-DEV). To achieve this goal, the company hires experts to change the existing process, which represents a high cost for small and medium-sized businesses. The assumption in this work is to evaluate the possibility of using an agile methodology which adheres to CMMI-DEV. Feature Driven Development (FDD) was the agile methodology selected to assess their adherence to Project Planning area of CMMI-DEV. The evaluation of specific practices was automated by the multi-agent system with two ontologies. The first of them is the Ontology CMMI/FDD, which defines the concepts and the relationship of FDD with these specific practices. The second is the Ontology of Project Planning Document that defines the concepts used in sections of the Project Planning documents. The mapping between the specific practices and implementation was performed by intelligent mapping agents. The results obtained shown that it is possible to automate the process of evaluation of specific practices by the evidences in sections of the documents, reducing the costs involved in hiring a specialist of CMMI. The evaluation of Intelligent Agents of Specific Practices shown that the FDD partially attends to the specific practices, being necessary to change the two documents elaborated from the FDD Document (Project Plan and List of Functionality) and add three auxiliary documents (Risk Management, Data Management and Training Management) to meet all the specific practices of the Project Planning Area of the CMMI-DEV. / Em um mercado competitivo de desenvolvimento de software, as empresas buscam um processo ágil com qualidade. Diante desse desafio, procuram uma certificação para comprovar a capacidade de produzir com qualidade, seguindo um processo definido, por exemplo, o Capability Maturity Model Integration for Development (CMMI-DEV). Para atingir essa meta, a empresa contrata especialistas para alterar o processo existente, o que representa um alto custo para empresas de pequeno e médio porte. A hipótese neste trabalho é avaliar a possibilidade de utilizar uma metodologia ágil aderente ao CMMI-DEV. O Desenvolvimento Guiado por Funcionalidades (FDD) é a metodologia ágil selecionada para computar a sua aderência em relação à área de Planejamento de Projetos do CMMI-DEV. A avaliação das práticas específicas foi automatizada por um sistema multiagentes com duas ontologias. A primeira delas é a ontologia CMMI/FDD, que define os conceitos e a relação do FDD com essas práticas específicas. A segunda é a ontologia dos Documentos do Planejamento de Projeto, que define os conceitos utilizados nas seções dos documentos do Planejamento de Projeto. O mapeamento entre a prática específica e a implementação nas seções de documentação foi realizado pelos Agentes Inteligentes de Mapeamento. Os resultados obtidos mostram que é possível automatizar o processo de avaliação das práticas específicas, mostrando as evidências nas seções dos documentos, reduzindo os custos envolvidos na contratação de um especialista em CMMI. A avaliação dos Agentes Inteligentes de Práticas Específicas mostra que o FDD atende parcialmente às práticas específicas, sendo necessário alterar os dois documentos elaborados a partir do documento do FDD (Plano de Projeto e Lista de Funcionalidade) e adicionar três documentos auxiliares (Gestão de Risco, Gestão de Dados e Gestão de Treinamento) para satisfazer a todas as práticas específicas da área de Planejamento de Projeto.

The problem addressed in this study was the lack of understanding about failures of government leadership in accomplishing complex information technology (IT) projects and the ways such failures can negatively affect organizational performance. The purpose was to query subject matter experts and leaders with the intent to identify methods to reduce complex IT project failure rates in government organizations. This qualitative study drew on the technology acceptance model and the capability maturity model integration framework to evaluate organizations' abilities to manage complex IT projects. The research questions focused on exploring senior managers' experiences, the tacit knowledge of project management methodologies, and IT governance frameworks. The Delphi method was suitable for collecting and analyzing opinions of subject matter experts to help reach group consensus. Qualitative data analysis was used to identify themes, categories, and subcategories for thematic analysis. The result of the study was the identification of critical success factors and leadership attributes to increase the success rate of complex IT projects in federal agencies. This research may be beneficial to federal government program leaders who, as the result of increased insights and knowledge, can more effectively provide online government services using technology-enabled end-users' computing devices in a cost-effective and secure method.

In this research, it was mainly aimed to develop an acceptance model for processes, namely the process acceptance model (PAM). For this purpose, a questionnaire, comprising 3-part and 81-question, was developed to collect quantitative and qualitative data from people having relationships with certain process-focused models and/or standards (CMMI, ISO 15504, ISO 9001, ISO 27001, AQAP-160, AQAP-2110, and/or AS 9100). To revise and refine the questionnaire, expert reviews were ensured, and a pilot study was conducted with 60 usable responses. After reviews, refinements and piloting, the questionnaire was deployed to collect data and in-total 368 usable responses were collected from the people. Here, collected data were screened concerning incorrectly entered data, missing data, outliers and normality, and reliability and validity of the questionnaire were ensured. Partial least squares structural equation modeling (PLS SEM) was applied to develop the PAM. In this context, exploratory and confirmatory factor analyses were applied, and the initial model was estimated and evaluated. The initial model was modified as required by PLS SEM, and confirmatory factor analysis was repeated, and the modified final model was estimated and evaluated. Consequently, the PAM, with 18 factors and their statistically significant relationships, was developed. Furthermore, descriptive statistics and t-tests were applied to discover some interesting, meaningful, and important points to be taken into account regarding the acceptance of processes. Moreover, collected quantitative data were analyzed, and three additional factors were discovered regarding the acceptance of processes. Besides, a checklist to test and/or promote the acceptance of processes was established.

The need for information systems has increased to a point where virtually all business environments require some sort of software to aid in its daily operations. This study will address the need for quality information systems by examining techniques which can potentially aid in producing consistent high-quality information systems. Two techniques in particular, namely Process Maturity Models (PMMs) and Systems Development Methodologies (SDMs) are examined. Process Maturity Models such as the Capability Maturity Model Integration (CMMI) as well as the ISO-9000 standards aid in standardising and improving an organisation’s information systems development processes. These Process Maturity Models often require either the use of certain Systems Development Methodologies or at the very least techniques used within some Systems Development Methodologies. Systems Development Methodologies refer to a set of development processes, tools, techniques etc. which can be used during software development to standardise the entire development process by offering the use of modelling techniques, tools to analyse requirements, illustration of processes etc. These techniques differ from one Systems Development Methodology to the next. This study aims to identify the relationship between Process Maturity Models and Systems Development Methodologies. During the research process a questionnaire was sent out to people within the information technology business environment. The questionnaire contained questions used to determine and measure the usage of Systems Development Methodologies and how projects were affected. The questionnaire was also used to do an informal assessment of each respondent’s Capability Maturity Model level. Furthermore the data retrieved was statistically analysed and the results were interpreted. The results indicate that a relationship exists between the use of SDMs and the success of the respondent’s development processes and developed products. A total of 73% of respondents indicated that they do use SDMs to some extent, the most common being the Systems Development Lifecycle (SDLC). The majority of organizations implementing SDMs have been doing so for three years or more. Results also show that most of the respondents are not certified in some formal Process Maturity Model; however, they do implement some of the processes required by models such as the CMMI. An informal assessment performed indicated that 65% of respondents can be grouped into a perceived CMMI level 2 category. Project outcome was measured and the relationship between PMM implementation as well as SDM use was measured. Results show no statistical evidence which indicates that an organisation’s perceived CMMI level is influenced by SDM use, both vertically and horizontally. Results do, however, indicate that organizations which have been implementing SDMs for a longer period of time are more likely to apply CMMI level 4 activities. Results also indicate that the horizontal use (number of projects/people which implement SDM knowledge) of SDMs have a significant effect on the development process- and the developed product success. Lastly the results indicated that organizations which satisfy more of the CMMI’s level 4 activities experience a higher quality development process which leads to a more successful development process. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2013.