中小软件企业软件过程管理与改进策略

针对我国中小软件企业的软件过程现状,从改进对象、过程模型、开发个体、自评估、辅助工具等方面提出了几点策略,并提出了中小软件企业软件过程管理与评估系统的简要设计思路,旨在为我国中小软件企业的软件过程管理与改进工作提供建议。     

质量管理在软件开发中的应用

随着软件行业高速的发展,软件开发的超期和超预算都成为软件行业中的重要问题。为了有效地管理软件开发,一些公司增设了质量管理岗位。在软件开发过程中及时地管理和反馈项目信息,把所有重要问题都控制在项目初期,节约大量的人力、物力和财力。     

软件过程改进应“以人为本”

目前,许多软件企业都实施了CMM/CMMI的软件质量管理体系,但质量改进的效果并不明显。分析了以人为本的内涵以及软件质量的特点,和人在软件过程改进过程中重要作用,强调在软件过程改进中,只有坚持以人为本,才能切实提高软件质量。从关心人、尊重人和发展人的角度,从多个方面对如何实施以人为本的软件过程改进进行了探讨。这些策略和方法可以作为软件企业实施软件过程改进的补充。     

插件化软件开发方法初探

随着信息技术的发展,传统的软件开发方法已经不能适应用户不断变化的需求,大量的软件开发企业需要一种灵活的、能够基于一套产品代码进行扩展的软件开发方法来满足用户的需求,以达到用最少的人力资源争取最大的市场份额。本文比较了目前主流的几种软件扩展开发方法,分析了各种开发方法的优缺点,并提出了一种新的软件开发方法——插件化软件开发方法;给出了插件化开发方法的定义和使用方法,同时分析了此方法的优缺点,并提出了建议的使用场景。     

Software quality practices — an empirical study

Concern about the quality of software is widespread. Reliable data about current practice are hard to get as no one likes to admit that they are producing poor software. In a recent survey, Wilson has taken an approach to obtaining data about the practice of software quality assurance among companies in Australia. The same technique has been used here to investigate practice among companies in Europe and America. The survey ams to investigate quality systems used by the organizations, and the application of these systems by software fevelopers. In this paper they are compared with the Australian experience and the results of the survey shown. The company's demographic data and overall response pattern from this survey are compared with Wilson's. Patterns in software quality assurance programs of organizations are suggested by comparing the management's perspective with that of the developers. The most popular software development techniques identified by the developers are prioritized in the order of their popularity by using a weighting scheme and their implications are discussed.     

中小软件企业项目风险管理过程的分析与研究

从我国中小软件企业的软件项目管理现状出发,在分析CMMI和其他当前流行的风险管理模型的基础上,提出中小软件企业软件项目风险管理过程的设计思路,为我国中小软件企业的项目风险管理过程提供建议和参考。     

A View of Software Development Environments Based on Activity Theory

We view software development as a collaborative activity that is typically supported by a software development environment. Since these environments can significantly influence the collaborative nature of a software development project, it is important to analyze and evaluate their capabilities with respect to collaboration. In this paper, we present an analysis and evaluation of the collaborative capabilities of software development environments using an activity theory perspective.The discipline of software engineering (SE) emerged to study and develop artifacts to mediate the collective development of large software systems. While many advances have been made in the past three decades of SE's existence, the historical origins of the discipline are present in that techniques and tools to support the collaborative aspects of large-scale software development are still lacking. One factor is a common ``production-oriented' philosophy that emphasizes the mechanistic and individualistic aspects of software development over the collaborative aspects thereby ignoring the rich set of human-human interactions that are possible over the course of a software development project.We believe that the issues and ideas surrounding activity theory may be useful in improving support for collaboration in software engineering techniques and tools. As such, we make use of the activity theory to analyze and evaluate process-centered software development environments (PCSDEs).     

财经院校软件工程专业建设的探索

相对于我国的软件产业的快速发展,软件工程专业教育发展相对滞后。在许多软件专业学生找不到工作的同时,软件企业却找不到合适的人才。本文提出了在财经院校建设软件工程专业的一些探索,主要为解决学生动手实践能力,从而解决就业问题等提供一些思路。     

Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis

In this paper we discuss our study of the problems 12 software companies experienced in software development. In total we present qualitative data collected from 45 focus groups that involved over 200 software staff. We look at how different practitioner groups respond to software process improvement problems. We show our classification and analysis of this data using correspondence analysis. Correspondence analysis is a graphical data representation method new to software development research. The aim of the work we present is to develop a more holistic understanding of the problems practitioners are experiencing in their attempts to improve their software processes. Our main finding is that there is an association between a company's capability maturity and patterns of reported problems. Organizational problems are more associated with high maturity companies than with low maturity companies. Low maturity companies are closely linked to problems relating directly to projects such as documentation, timescales, tools and technology. Our findings also confirm differences in practitioner group problems. Senior managers cite problems with goals, culture and politics. Project managers are concerned with timescales, change management, budgets and estimates. Developers are experiencing problems with requirements, testing, documentation, communication, tools and technology. These associations are displayed graphically through correspondence analysis maps.     

Software quality programmes: a snapshot of theory versus reality

We analyse the software quality programmes of two major UK companies whose software development departments, we feel, are typical of many hundreds in the UK. The analysis is based on an almost exhaustive survey of relevant practitioners at these companies (123 out of a possible 149 individuals) using questionnaires and interviews. We discovered significant differences between senior managers' perceptions and the reality of what quality practices took place. In particular, use of reviews and inspections, which are widely believed to be an extremely cost-effective QA procedure, was very limited even when safety critical software was being developed. On the other hand there was widespread use of development and coding standards whose value is questionable. We also discovered significant differences between practitioners' and managers' views of what the company quality goals really were. While no generalizable conclusions can be drawn from the results of just two companies, the observations do confirm the informal results arising from the more extensive nationwide survey of which this particular study forms a part.     

软件过程集成框架的实践与思考

软件实践表明产品开发的过程和产品品质有产非常密切的联系,因此很多软件企业都把提高软件开发过程作为提高软件品质的重要手段。现有的过程模型中CMM/CMMI是很多企业采用的一个框架,CMMI模型非常复杂(描述性文档就有超过1000页),因此很需要有一种软件来支持软件过程的改进。本文给出了一个软件过程改进集成框架SPIF,较为详细地叙述了SPIF中项目计划与进度监控的实现。SPIF对CMM/CMMI有着良好的支持,经过几个软件公司的实践表明SPIF实现了软件过程可视化、管理效率化,可以对软件企业实施CMM/CMMI过程改进有着很好的促进作用。     

Managing Problems for Global Software Production – Experience and Lessons

With the increase in size and complexity of current software projects, many large companies have established global software production lines over the world to develop and deliver software products with collaborative software development processes involving multiple teams located at different sites. Supporting global software production needs an effective software-engineering environment to meet the special requirements of the collaborative software development process, diverse management methods and engineering practice. WWW technology provides powerful means to set up an enterprise-oriented software engineering environment for global software production due to its advantages in networking, global access, internationalization, and communication. Although there are many articles addressing the methods and experience in building web-based applications systems and tools, very few papers discuss the real-world problems and solutions in the development and deployment of web-based software tools to support a collaborative software development process for global software production. This paper discusses the real world issues, and reports our experience and lessons in building and deploying a web-based problem information management system (PIMS) to support global software development processes at Fujitsu. It focuses on the real issues and needs of current collaborative development process involving multiple teams, and highlights the benefits and impact of the PIMS on global software production. Moreover, it discusses our technical solutions and trade-offs in the development of PIMS, and shares our experience and lessons. Furthermore, it introduces a new data-centered conceptual process model to support diverse collaborative processes for project and problem management in global software production. Finally, the paper shares our key successes and weaknesses, and reports our experience and lessons in the deployment of the system.     

Knowledge Management in Medium-Sized Software Consulting Companies

This thesis investigates how Intranet-based knowledge management tools are used for various strategies in medium-sized software consultancy companies. It consists of three main parts: A survey of empirical work on knowledge management in software engineering, a multicase study of four medium-sized companies, and finally a thorough study on tool usage in two companies.     

创新型软件人才培养模式探索

从软件人才培养目标出发,结合西南科技大学软件人才培养实践,从建立软件人才培养体系、改革教学模式、构建开放的实践环境、科研深化教学、产学研联合办学等方面对软件创新人才培养模式进行深入探索。     

软件众包参与度影响因素分析及预测模型

随着"众包"这种商业模式的快速发展, 越来越多的互联网公司选择以"众包"的形式发布软件任务. 然而, 软件任务因其高门槛、高复杂度、长周期等特性, 面临着严重的低参与度问题. 本文结合全球最大的软件众包平台TopCoder的数据, 对软件众包任务的参与度进行研究. 首先, 使用多元回归分析了影响软件众包参与度的因素; 接着, 综合数据挖掘领域的多种分类预测算法, 探讨软件众包参与度的预测模型. 希望通过本实证研究, 为发包方、众包平台降低软件众包的低参与风险提供参考.     

Risks to Effective Knowledge Sharing in Agile Software Teams: A Model for Assessing and Mitigating Risks

We present an empirically grounded and theoretically informed model for the assessment and mitigation of risks to effective knowledge sharing in agile development. The model is anchored in empirical insights from four agile projects across two software companies and in extant research on risk‐strategy analysis and knowledge sharing in software development. We develop the model as part of the long‐standing tradition of presenting risk management models dedicated to specific issues in software development and confirm its practical usefulness in one of the software companies studied. The model offers concepts and processes to assess a project's knowledge sharing risk profile and articulate an overall resolution strategy plan to mitigate the risks. The results highlight how different knowledge sharing risk management profiles can lead to different project performance outcomes. We conclude with a discussion of research opportunities that the results offer software development scholarship. © 2016 John Wiley & Sons Ltd     

SPI Models: What Characteristics are Required for Small Software Development Companies?

There is a need for small indigenous software companies to improve their software process. Consequently, much has been written highlighting the deficiencies in the more popular Software Process Improvement (SPI) models where the small company is concerned. However, there has been little discussion about the characteristics that should be included in SPI models to make them useful for the small company. In this paper, the author proposes an SPI model for use in small software development companies. The eight characteristics that were required to exist in the model are examined and reasons for their successful inclusion presented.     

基于软件工程思想的数码防伪公共服务系统的设计与开发

针对通常数码防伪系统所存在的问题，结合软件工程的基本思想和方法，分析数码防伪公共服务系统的设计与开发过程．并利用风险管理的理论对试系统的开发过程进行控制和管理。新数码防伪系统能为各产品厂商或企业提供服务接口，提供多种查询方式，并可搜集、汇总并统计市场反馈信息。实践表明。将软件工程的思想方法与数码防伪公共服务系统的设计与实际开发相结合．降低了系统的开发难度，提高了系统的可靠性与可维护性．较好地满足了企业的信用防伪需求。     

Ordering Fault-Prone Software Modules

Software developers apply various techniques early in development to improve software reliability, such as extra reviews, additional testing, and strategic assignment of personnel. Due to limited resources and time, it is often not practical to enhance the reliability of all modules. Our goal is to target reliability enhancement activities to those modules that would otherwise have problems later. Prior research has shown that a software quality model based on software product and process metrics can predict which modules are likely to have faults.A module-order model is a quantitative software quality model that is used to predict the rank-order of modules according to a quality factor, such as the number of faults. The contribution of this paper is definition of module-order models and a method for their evaluation and use. Two empirical case studies of full-scale industrial software systems provide empirical evidence of the usefulness of module-order models for targeting reliability enhancement.     

第三方软件项目咨询的作用与实践

通过对中小软件企业在项目过程中存在的问题分析,提出了引入第三方软件项目咨询的解决方案。以具体软件项目咨询实践为例,结合软件工程与项目管理方法论,论述了软件项目咨询为提高中小软件企业的项目实效所发挥的作用。