基于MDA技术的软件过程改进研究

模型驱动架构（MDA）是OMG提出的基于模型驱动（MD）思想的新的方法学。文中在分析和总结中小型软件企业运用MDA技术进行软件开发的基础上，结合软件过程改进的实践经验，提出了基于MDA技术的中小型软件企业过程改进模型。该模型为中小型企业采用MDA技术进行软件开发提出了相应的过程改进模型。企业还可以根据自身的情况对该模型进行裁剪，以便使该模型更加贴近企业的需要。     

基于面向对象的MDA三级建模技术研究

模型在模型驱动架构(MDA)软件开发生命周期中驱动整个开发过程,建模在MDA中起关键作用,建模是否成功是模型转换的前提,也决定MDA软件开发的成败。通过对当前建模技术的研究分析,根据对系统抽象级别的不同,提出基于MDA的三级建模技术,即计算无关模型(CIM)建模,平台无关模型(PIM)建模,平台相关模型(PSM)建模。详细介绍三个不同抽象级别模型的建模过程,并对它们之间的模型转换加以说明,从整体上描述MDA软件开发的过程,得出一种MDA软件开发方法。     

MDA的设想与实现

模型驱动体系结构(MDA)提出了一种利用模型进行软件开发的方法，它将模型作为软件开发过程的关键，MDA的基本思想是将模型区分为平台独立模型(platform independent model)和平台相关模型(platform specific model)，通过不同抽象层次模型之间的转换完成软件开发过程。介绍了MDA的设想，包括MDA的基本概念，基于MDA的开发过程，讨论了实现MDA所涉及的几个重要问题。     

基于CMM的中小软件企业过程改进实施方案研究

随着软件工程化进程的推进,各种过程改进模型和方法层出不穷。针对如何将软件能力成熟度模型CMM与我国中小型软件组织相融合这一问题,对CMM中的各关键实践进行了裁剪和重定位。结合软件开发的迭代增量模型,将软件开发过程分为先启阶段、精化阶段、构造阶段和产品提交等阶段,并将需求管理、项目规划管理和项目监控等管理活动与软件开发过程相结合,提出了一种基于CMM模型的适合国内中小型企业的过程改进方案,实践证明了此方案的可行性及经济性。     

基于MDA的软件建模方法研究

模型驱动架构(MDA)是一个新的软件开发框架,它溶入了软件工程领域的新思想、新方法和新技术。本文研究了基于MDA的软件建模方法,探讨了模型在整个软件生命周期中起的关键作用,提出了一种从平台无关模型(PIM)到平台相关模型(PSM)的转换方法。     

模型驱动体系结构研究综述

模型驱动体系结构(MDA)是由 OMG 提出的应用模型技术进行软件开发的方法和标准体系,其核心技术是平台无关模型建模和平台特定模型转换。MDA 代表了现代软件开发理论与方法发展的主流趋势,可以预见到它会成为继面向对象技术后软件工程史上的又一个里程碑。本文对 MDA 进行了系统性的阐述,包括 MDA 产生背景、总体构成、模型体系、软件方法、应用与评价以及最新研究与趋势等。     

基于MDA的模型转换研究与应用

模型驱动方法解决了软件开发的效率低、可移植性差等问题,其中的模型转换是开发基于模型驱动构架(MDA)应用工具的关键技术。为此,在模型驱动方法的基础上,提出基于模式的平台无关模型到平台相关模型的模型转换方法,并根据该转换方法确立转换规则,在一个MDA应用系统开发实例中进行验证,实现从平台无关层模型到J2EE平台相关层EJB模型的转换。     

论软件质量保证

不用实施CMM，不用引进RUP(Rational Llnified Process)，在中小型软件企业如何实施软件过程改进，以提高软件开发质量。这是值得探讨的问题。本文通过在企业内部实施文档模板化、加强技术评审和适当地引进辅助工具三个方面，讨论针对中小型企业的薄弱环节实施质量改进方法，切实降低了项目风险，保证了软件开发质量。本文还着重阐述了如何进行技术评审而不流于形式、走过场以及如何有针对性地引入辅助工具来提高开发和管理工作的效率，对于中小型软件企业在规范公司内部开发过程、提高软件质量和降低项目风险等方面，有一定的借鉴作用。     

基于MDA的联邦开发和执行过程研究

模型驱动体系架构（MDA）是对象管理组织（OMG）2001年7月提出的先进的软件开发方法学,对开发基于HLA的仿真联邦具有很好的借鉴作用;在系统地总结了MDA系统开发原理的基础上,归纳了MDA系统开发的技术优势;将MDA应用于基于HLA仿真系统的开发,初步探讨了基于MDA的联邦开发和执行过程,并描述了该过程模型的顶层视图。     

基于TSP的软件质量控制平台设计与实现

随着社会发展,竞争日益激烈。软件企业纷纷尝试各种途径以增强自身竞争力。小组软件过程（TSP）为一般中小型软件企业规范软件开发和改进过程能力提供了有效而实际的帮助,如何有效地管理一个TSP项目尚待研究。通过对小组软件过程的分析,设计并实现了过程脚本驱动的、基于TSP的软件质量控制平台。允许用户对过程脚本进行裁剪,实现了小组协作开发质量控制的自动化。     

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.     

Successful process implementation

We propose measuring software process improvement (SPI) success through implementation success - the extent to which initiatives lead to actual changes in software engineering practice. First, without implementation success, SPI success is impossible. Second, only when implementation succeeds can we see how SPI initiatives affect software practices. Third, implementation success is easy to assess. Finally, focusing on implementation success is a pragmatic way to steer SPI initiatives toward success. We studied the approach and outcome of 18 different SPI initiatives conducted over a five-year period at the telecom company Ericsson AB, based in Gothenburg, Sweden. Doing so gave us insight into how SPI initiatives can best 1) ensure stakeholder commitment 2) support organizational learning 3) distribute resources over different activities 4) manage customer relations.     

Product Focused Software Process Improvement: Concepts and Experiences from Industry

Management problems in the development of software have been addressed over the last years by a strong focus on the improvement of the development processes. Software process improvement (SPI) activities are characterized by an internal focus on a software development department and its procedures. However, the quality of the product is hardly addressed in software process improvement programs. This paper presents the application of a model for product focused SPI (P-SPI) and describes experiences with this model in practice. The main conclusions are that P-SPI puts products to be developed in a central position in improvement programs, results in fulfilling specific quality goals of a company and project, and industrial experiments show interesting benefits. Applying the approach in industrial projects showed that P-SPI is relatively cheap and gives fast results and high benefits.     

基于Nios Ⅱ的SPI接口实现

Nios Ⅱ是Altera公司的第二代FPGA嵌入式处理器,和其挂接的外围接口相当于一个完整的SOPC系统,AD9517-1ABCPZ是一款时钟芯片,需通过SPI接口配置,让其先于系统的其他部分工作,为系统其它芯片提供时钟。针对SPI接口的实现,目前有很多方法,基于Nios II实现,具有简单灵活、开发周期短、成本低和系统维护方便等优点,可应用于许多中、低速系统设计。实现主要包括硬件设计和软件设计,硬件设计包括基于Nios II的SOPC系统的搭建,SPI-MASTER接口FPGA程序设计;软件设计包括SPI读写函数设计,AD9517-1ABCPZ寄存器配置函数设计。     

Towards a theoretical framework of SPI success factors for small and medium web companies

ContextThe context of this research is software process improvement (SPI) success factors for small and medium Web companies.ObjectiveThe primary objective of this paper is to propose a theoretical framework of SPI success factors for small and medium Web companies.MethodThe theoretical framework presented in this study aggregated the results of three previous research phases by applying principles of theoretical integration and comparative analysis. Those three previous phases were all empirical in nature, and comprise: a systematic review of SPI in small and medium Web companies [1], [2]; a replication study [3] and a grounded theory-based initial exploratory framework of factors in small and medium Web companies [4].ResultsThe theoretical framework includes 18 categories of SPI success factors, 148 properties of these categories and 25 corresponding relationships, which bind these categories together. With the help of these relationships, the categories and properties of SPI success factors can be directly translated into a set of guidelines, which can then be used by the practitioners of small and medium Web companies to improve the current state of SPI in their companies and achieve overall company success.ConclusionThe comprehensive theoretical framework of SPI success factors presented herein provides evidence regarding key factors for predicting SPI success for small and medium Web companies. The framework can be used as a baseline for a successful implementation of SPI initiatives in the mentioned domain.     

Modelling the Likelihood of Software Process Improvement: An Exploratory Study

Software process assessments have become big business worldwide. They can be a powerful tool for initiating and sustaining software process improvement (SPI). However, SPI programs sometimes fail. Moreover there still are very few systematic empirical investigations about the conditions under which SPI initiatives vary in their outcomes. In this paper we present the results of a study of factors that influence the success of SPI. The data come from a sample survey of organizations that have performed assessments based on the capability maturity model for software, and was conducted from 1 to 3 years after the assessments (sufficient time had passed for changes to have taken place). The results consist of a multivariate model of the conditions (e.g., how the improvement efforts are organized and funded) that can explain the successes and failures of SPI efforts. The model is constructed using a classification tree algorithm. It identifies the most important factors that affect the outcome of SPI efforts, and describes how those factors interact with each other to influence success or failure.     

Applying grounded theory to understand software process improvement implementation: a study of Brazilian software organizations

Despite the fact that organizations recognize the importance of implementing software process improvement (SPI) to enhance software development capabilities, recent studies show that many organizations still struggle to successfully implement SPI. These studies demonstrate that most SPI initiatives fail due to their incapacity to overcome social–cultural critical barriers, such as lack of motivation and higher management support. Therefore, the accurate understanding of the context where SPI occurs may facilitate the development of more efficient SPI implementation strategies aiming to overcome those difficulties. The objective of this work was to present a Grounded Theory-based study that investigated SPI implementation initiatives conducted by Brazilian software organizations. The main product of this study is a theoretical framework that tries and explains the phenomenon associated to the success of SPI implementation initiatives. The theoretical framework constituted a set of interrelated SPI domain entities supported by a set of propositions assessed by experienced Brazilian SPI consultants. We expect that such theoretical framework can facilitate SPI implementation by providing better understating of the dependency relationships among critical success factors that may jeopardize SPI initiatives.     

Software Process Improvement Motivators: An Analysis using Multidimensional Scaling

In this paper we present an analysis of software practitioners' motivations for software process improvement (SPI). Our findings are based on an empirical study of SPI in 13 software companies where we conducted focus groups with nearly 200 software practitioners. Our aim is to better understand how companies can maximise practitioner support for SPI. This insight should help SPI managers establish more effective SPI implementation strategies. In this paper we introduce the use of multidimensional scaling (MDS) in SPI research. MDS is a social science data analysis technique designed to generate a rich visual understanding of human issues. By using MDS we found evidence to suggest distinct clusters of punitive and rewarding SPI motivators. Furthermore our analysis also suggests that different clusters of motivations exist for different staff groups.     

Scrum中软件缺陷管理方法的研究与应用

针对某公司互联网产品的开发项目,分析基于Scrum的软件敏捷开发过程,给出其缺陷管理目标,即敏捷地响应缺陷和实时地改进开发过程,设计相应的缺陷管理方法,包括缺陷管理流程模型以及缺陷度量方法。在此基础上,开发缺陷管理工具RQMS并加以应用。应用结果表明,该缺陷管理方法在基于Scrum软件敏捷开发中具有较好的效果。