Statistical Analysis of Process Monitoring Data for Software Process Improvement and Its Application

Software projects influenced by many human factors generate various risks. In order to develop highly quality software, it is important to respond to these risks reasonably and promptly. In addition, it is not easy for project managers to deal with these risks completely. Therefore, it is essential to manage the process quality by promoting activities of process monitoring and design quality assessment. In this paper, we discuss statistical data analysis for actual project management activities in process monitoring and design quality assessment, and analyze the effects for these software process improvement quantitatively by applying the methods of multivariate analysis. Then, we show how process factors affect the management measures of QCD (Quality, Cost, Delivery) by applying the multiple regression analyses to observed process monitoring data. Further, we quantitatively evaluate the effect by performing design quality assessment based on the principal component analysis and the factor analysis. As a result of analysis, we show that the design quality assessment activities are so effective for software process improvement. Further, based on the result of quantitative project assessment, we discuss the usefulness of process monitoring progress assessment by using a software reliability growth model. This result may enable us to give a useful quantitative measure of product release determination.

Empirical Research on Critical Success Factors of Agile Software Process Improvement

In this paper, we discuss agile software process improvement in P company with their description of process management in current level and analysis of problems, design the P Company success factors model in organizational culture, systems, products, customers, markets, leadership, technology and other key dimensions, which is verified through questionnaire in P company. In the end, we apply knowledge creation theory to analyze the open source software community with successful application of the typical agile software method, propose ten principles of knowledge creation in open source software community: Self-organizing, Code sharing, Adaptation, Usability, Sustention, Talent, Interaction, Collaboration, Happiness, and Democracy.

Research on Knowledge Transfer Influencing Factors in Software Process Improvement

Knowledge transfer model of software process improvement (SPI) and the conceptual framework of influencing factors are established. The model includes five elements which are knowledge of transfer, sources of knowledge, recipients of knowledge, relationship of transfer parties, and the environment of transfer. The conceptual framework includes ten key factors which are ambiguity, systematism, transfer willingness, capacity of impartation, capacity of absorption, incen-tive mechanism, culture, technical support, trust and knowledge distance. The research hypothesis is put forward. Em-pirical study concludes that the trust relationship among SPI staffs has the greatest influence on knowledge transfer, and organizational incentive mechanism can produce positive effect to knowledge transfer of SPI. Finally, some sug-gestions are put forward to improve the knowledge transfer of SPI: establishing a rational incentive mechanism, exe-cuting some necessary training to transfer parties and using software benchmarking.

Research on Explicit and Tacit Knowledge Interaction in Software Process Improvement Project

This research develops a knowledge model for Software Process Improvement (SPI) project based on knowledge creation theory and its twenty-four measurement items, and proposes two hypothesizes about the interaction of explicit knowledge and tacit knowledge in SPI. Eleven factors are extracted through statistical analysis. Three knowledge-creation practices for capturing tacit knowledge contribute greatly to SPI, which are communication among members, crossover collaboration in practical work and pair programming. Two knowledge-creation practices for capturing explicit knowledge have significant positive impact on SPI, which are integrating project document and on-the-job training. Ultimately, suggestions for improvement are put forward, that is, encouraging communication among staff and integrating documents in real time, and future research is also illustrated.

A parallel-pipelining software process model

Software process is a framework for effective and timely delivery of software system. The framework plays a crucial role for software success. However, the development of large-scale software still faces the crisis of high risks, low quality, high costs and long cycle time. This paper proposed a three-phase parallel-pipelining software process model for improving speed and productivity, and reducing software costs and risks without sacrificing software quality. In this model, two strategies were presented. One strategy, based on subsystem-cost priority, was used to prevent software development cost wasting and to reduce software complexity as well; the other strategy, used for balancing subsystem complexity, was designed to reduce the software complexity in the later development stages. Moreover, the proposed function-detailed and workload-simplified subsystem pipelining software process model presents much higher parallelity than the concurrent incremental model. Finally, the component-based product line technology not only ensures software quality and further reduces cycle time, software costs, and software risks but also sufficiently and rationally utilizes previous software product resources and enhances the competition ability of software development organizations.

Implementing a Personal Software Process (PSPSM) Course: A Case Study

In order to remain competitive in software industry, software engineers need to continuously improve their proficiency. Personal Software Process (PSPSM) provides a strong concept which helps software engineers inspecting and improving themselves. Yet, when being applied on an undergraduate computer engineering course, several complex mathematical calculations from PSP official exercises could encumber the performance of students who do not possess adequate mathematics background. This paper reports a result of implementing PSP course for undergraduate computer engineering students in Chiang Mai University, Thailand.

China's Software Industry Aiming at a Higher Standard

The current status of the China's software industry is introduced, including the great potential opportunities and many problems across the path to success. The main measures are discussed to keep abreast of the time needs and fuse with the whole family of global IT industry.

一个基于Web的软件过程改进框架SPIF的实现

软件过程的理论日趋成熟 ,而基于软件过程改进模型的面向中小软件组织的应用程序却很少 ,因而造成一种情形 ,即管理者知道应该进行软件过程的改进 ,也知道有很多可以参考的规范与模型 ,但是 ,真正开始的时候 ,却不知道该如何着手。本文介绍一个基于Web的软件过程改进框架 ,试图给出一个解决问题的途径。该系统集成一组管理工具与相关知识库 ,用一种灵活的方式帮助组织确定适合自己的软件过程模型 ,从而以一种相对简洁方便的方式实现对软件过程的管理与改进。

实绩价值管理成熟度模型及其支持工具SPIF

EVM是一种能够帮助软件组织降低项目风险、提高开发效率、减少项目开支的行之有效的软件过程改进方法,EVM^3是一个提高软件组织使用EVM管理项目能力的模型。本文介绍了EVM^3的基本概念、与CMMI的关系,以及一个支持EVM^3进行软件过程改进的工具SPIF。

计量科学管理及其在软件应用中的专业性

计量科学是一门重要的工程学科,涵盖了测量、标准化、校准以及质量控制等方面的知识和技术。在今天的工业和科研领域,计量科学管理变得至关重要,因为它有助于确保产品和数据的准确性、可追溯性和可重复性。本论文旨在深入探讨计量科学管理的基本原则,并介绍了在这一领域中广泛使用的软件工具,以帮助计量工程师更好地管理测量和质量控制过程。

Smart Development Process Enactment Based on Context Sensitive Sequence Prediction

Actual software development processes define the different steps developers have to perform during a development project. Usually these development steps are not described independently from each other—a more or less formal flow of development step is an essential part of the development process definition. In practice, we observe that often the process definitions are hardly used and very seldom “lived”. One reason is that the predefined general process flow does not reflect the specific constraints of the individual project. For that reasons we claim to get rid of the process flow definition as part of the development process. Instead we describe in this paper an approach to smartly assist developers in software process execution. The approach observes the developer’s actions and predicts his next development step based on the project process history. Therefore we apply machine learning resp. sequence learning approaches based on a general rule based process model and its semantics. Finally we show two evaluations of the presented approach: The data of the first is derived from a synthetic scenario. The second evaluation is based on real project data of an industrial enterprise.

产品型软件企业实施量化模型质量改进探析

在资源有限的情况下如何维持高质量软件产品交付是产品型软件企业面临的一大难题。以软件过程量化改进理论为基础,探讨如何调配资源进行质量过程改进。在某产品型软件企业中运用鱼骨图分析影响质量的关键因素,建立量化回归预测模型进行改进。提升测试人员专业及行业经验,在公司内部尽可能配置与软件应用环境相同的服务器和硬件外设,降低环境差异度,在有限的资源下进行测试人员平均经验和环境差异度的平衡,确保质量目标的达成。

人工智能对传统信息处理软件的影响与改进

人工智能的进步在自然语言的处理、语义理解、自适应与持续学习等方面为传统软件带来了创新的机会,赋予其更高的数据处理能力、适应性、自动化与智能决策。然而,这些技术进步也带来了挑战和问题,特别是在数据安全与隐私、技术依赖风险以及新型的人机交互问题等方面。因此,在享受人工智能所带来的便利之时,更需要深入地考虑其可能引发的问题,确保在技术进步中不忽略个体和社会的核心利益。

软件成熟度模型(CMM)发展综述

CMM是软件过程管理和控制的系统方法 ,它为软件过程改进提供了指南 ,为软件过程能力评估提供了依据。阐述了CMM的产生和发展的原因 ,对CMM的理论基础、核心思想和主要内容作了介绍 ;同时对CMM存在的问题作了概述 ,介绍了两个相关的解决方案。最后提出了CMM亟待解决的问题。

敏捷软件过程的研究

敏捷软件过程可能成为最适应软件开发全球化、个性化、快速化、高质量新格局的先进开发模式 ,它能够帮助软件企业快速响应市场赢得竞争 .针对这一趋势 ,系统分析软件开发的敏捷性需求 ,总结出敏捷软件过程的 5种典型特征 ,如并行、轻载、基于时间、正好策略、基于组件等 .然后设计了 FL EX语言 ,从 3个不同抽象层次上形式化定义了敏捷软件过程的功能模型、合作模型、资源模型和产品模型 .基于过程模型 ,同时提出了 9种静态分析和动态模拟技术 ,支持软件过程面向敏捷性的优化 .

中小型企业软件过程改善方法研究

软件过程改善是各个企业建立适合自身软件生产线和促进软件工业化生产的必由之路。软件过程理论和技术的研究与应用始终存在一定的差距,在国内外成功应用并受益于这些软件经验与技术的企业多数是国防企业和大型的商业企业,中小型企业具有不同于大型企业的企业特征,这些特征有些有利于软件工程技术的应用与实施,而有些又限制了软件工程技术的应用与实施。软件过程改善的关键是量体裁衣,以理论和模型为指导,充分结合企业特征,进行适合企业特色的软件过程改善。该文在分析中小型软件企业的企业文化、企业规模、软件生产的创新能力、动态变化能力、技术革新能力等特征的基础上,提出在对中小型软件企业进行过程改善时应突出几个方面,一是过程改善应充分利用开发组的丰富创造能力为解决过程改善问题提出方案,在确立过程改善目标时应尽可能多地涉及各种层次的项目组人员,同时采取划分过程改善任务单元的方法,不破坏软件开发过程的连续性;二是过程改善得到的结果应不限制团体的创造性,对过程改善结果的应用应针对具体项目相关的问题,而非建立一般性的软件过程规范。三是过程改善是应着重企业关心的目标,不一定完全依从CMM。在进行过程改善时,应实施“项目分析”关键子域,“项目分析”是以过程度量为核心的,分析?

一种基于PDCA的软件过程控制与改进模型

CMM/CMMI(capabilitymaturitymodel/CMMintegration)自1999年开始为中国软件企业所接受并逐步得以推广,但目前中国实施CMM/CMMI的企业还不多,有些企业实施效果并不理想.通过调查软件企业在实施CMM/CMMI过程中存在的问题,并对发现的问题及其负面影响进行分析,提出了基于PDCA(plan-do-check-action)的软件过程控制与改进模型,开发了SoftPM软件质量管理平台.该平台的广泛应用表明,该模型对提高CMM/CMMI的企业软件过程的效率和改善实施效果很有帮助.

软件配置管理在软件开发平台中的应用

介绍了软件组织设计及实施软件配置管理的方案,讨论了软件配置管理的基本概念,提出了一种基于CMMI实施配置管理的流程,重点讨论了配置标识、版本控制、变更控制等实践活动.然后,提出了一种集成软件配置管理功能的软件开发平台.通过在现有开发平台中引入文档管理,代码管理等模块,对软件的开发过程进行监督与控制,使软件开发过程满足CMMI二级的配置管理规范,实现了提高开发质量和效率的目的.

有效改善软件过程方法研究

改善软件过程是软件生产和发展软件产业的必由之路 .结合目前软件过程工程领域研究现状 ,研究分析两种软件过程改善的方法 :自顶向下和自底向上 .自顶向下的方法以 CMM模型框架为基础 ,结合其 5层结构指导企业软件过程的改善 ;自底向上的方法根据企业及其具体软件项目的特点 ,采取“理解”-“评估”-“打包”的软件过程改善过程 ,“理解”过程目的是建立软件过程基线 ,“评估”过程是引进过程变更并评估过程变更造成的影响 ,“打包”过程是评估成功过程变更得到的经验并形成新的过程规范 .最后从软件过程改善目标、软件过程基线、软件过程变更评价。

软件过程改进中项目计划与跟踪的实例研究

项目的计划与跟踪是软件过程管理与改进活动中应该首先着手的方面。成熟的软件开发组织能够通过有效的软件项目计划与跟踪实现对项目的策划与监控。文章立足小组软件过程,以实际项目为背景,着重介绍了以项目计划和跟踪为主的软件过程改进实施活动。在此基础上,分析了相关项目的计划与跟踪数据,研究总结了实施中遇到的问题和经验,并提出了进一步完善的措施及相关支持工具的研制。