基于模型的无人机平台管理系统自动测试研究

为实现某无人机平台管理系统的功能逻辑测试,开发了一套通用化的测试设备和测试用例编辑工具;通过总结被控系统的静态及动态特征,用编辑工具生成的测试用例模拟了各系统,建立了系统模型;测试过程中,测试设备的激励信号按条件或时序自动发送,测试用例与平台管理系统完全自主交互,实现了平台管理系统功能逻辑的自动测试;该自动测试方法可以将现有的多个测试用例组合,方便地编辑复杂自动测试用例;通过复杂的测试用例实现了多通道并行自动测试、多被控系统的全任务流程自动测试;该自动测试方法减轻了测试人员负担,使得测试效率提高了4倍,节省了约80%的测试时间。     

一个工作流定义工具的设计及实现

该文介绍了一个适合于软件企业定义其项目开发流程的,基于图形方式的工作流定义工具的设计及实现。该工具是根据软件企业达到CMM三级标准的要求和对软件开发过程进行管理的一般思想来考虑的。     

面向IC—CAD软件开发过程的集成化环境支持系统

本文介绍了一种支持IC—CAD软件开发环境支持系统的数学模型,以及基于该模型的ICSDE(IC Software Development Enviroment)系统。ICSDE环境集成了各种IC—CAD软件开发过程中的工具,以三维空间模型方式来描述和管理IC—CAD软件开发过程中的各种信息流程,为软件的可靠性、可维护性提供了保证。由于引入了工程化的管理模式,使软件的可复用性得以规范化的实施,并使IC—CAD软件的开发严格依照软件工程的设计思想进行,且对其产生的数据文件实现系统自动管理及调配,以期达到用户观点、设计风格、设计概念和工具等的同一,开拓了软件可继承性的前景。     

基于P13000平台的软件缺陷管理系统的应用实践

软件缺陷管理是提高软件质量和软件开发效率的重要技术途径之一。通过对现有缺陷管理工具的比较,依据CMMI模型并基于P13000平台,设计和实现了缺陷管理系统。该系统采用了浏览器的B／S架构,实现了缺陷跟踪的流程,对缺陷状态的变化进行控制,并具有查询、统计分析等功能,集合了多数缺陷管理工具的优点。实际应用表明该系统有效地提高了软件的质量和开发效率。     

浅谈软件配置管理的流程设计与实施

软件配置管理是一套规范、高效的软件开发管理方法,它能提供工作空间管理、并行开发支持、过程管理、权限控制、变更管理等一系列的管理能力,是提高软件质量的重要手段。软件配置管理可以帮助开发团队对软件开发过程进行有效的变更控制,它有机地把其它支持活动结合起来,形成一个整体,相互促进,相互影响,有力地保证了质量体系的实施。本文主要对软件配置管理的流程设计与实施进行探讨,并结合具体案例,分析了进行软件配置管理的实施策略。     

基于UML的流程管理引擎系统需求分析

电子商务的发展促进了计算机化的流程管理系统的发展。流程管理引擎系统(PNES)是流程管理系统的支持引擎。本文简要介绍了UML和Use Casee的特点，以及使用Use Case对PMES系统进行有效的需求分析，并由用例驱动整个开发过程。     

一种C++单元测试支持工具的研究与设计

单元测试是针对单个功能模块的测试,能尽早发现缺陷,降低滞后纠错的高成本。当今面向对象软件开发强调迭代和增量式的开发方法,单元测试为其提供了质量保证支持。在单元测试实践的基础上提出了一种单元测试支持工具的设计方法,该工具提供了一个灵活有效的单元测试框架和基于该框架的测试用例管理和优化方法。     

分布式协作建模仿真环境中的工作流管理设计

工作流管理是分布式协作建模仿真环境的核心内容之一,主要功能是分配与管理开发任务、协调开发人员之间的工作,对于保证开发工作的有序进行和提高工作效率具有重要意义。分析了流程的组成结构、流程驱动、数据传递、用户交互等工作流管理的关键技术问题。扩展和完善了OMG工作流管理模型,设计并实现了一种通用工作流管理系统。设计采用面向对象的技术,具有良好的可扩展性;支持柔性的流程结构;支持串行、并行、反馈三种流程结构以及它们的任意组合;支持层级不限的子流程;具备图形化的流程管理界面。     

基于JBPM与JPDL的工作流管理系统的研究与设计

阐明了工作流及工作流管理系统的概念.对JBPM进行深入的研究,包括工作流引擎JBPM的概述、流程定义语言、工作流开发步骤、工作流持久化数据库映射、事务管理、记录日志以及流程设计器等.并根据工作流引擎JBPM和JPDL方面的实践经验,在其基础上建立基于JBPM架构的工作流管理系统,以达到更好地实现流程管理,简化流程系统的设计与开发的目的.从而降低程序代码之间的耦合度,节约软件开发成本,提高软件开发的效率,提高系统的复用性、扩展性和可维护性.     

软件工程在火电厂燃料管理系统中的应用

针对火电厂燃料管理系统（RLMIS）应用软件开发中存在的问题，简述了软件工程的系统开发流程，指出如何将软件工程的思想应用到RLMIS系统应用软件的开发中，用软件工程的方法指导软件开发，井给出了相应的结构模型。该系统开发采用了螺旋模型，使原型系统最终解决目标系统，形成用户所需要的系统。结合软件工程开发出的RLMIS在实际运行时明显优于一般的管理系统，能够更好进行人机交互。软件体系结构的规范方法，大大提高了系统的工作效率。     

One World,Two Realities: Perception Differences between Software Developers and Testers

Strong working relations between software developers and testers are critical to the efficient and effective development of high-quality software. Smooth collaboration must occur as testers find problems and developers fix problems in the software. Prior studies based on anecdotal data have suggested that developers and testers have different personalities, approaches to work, etc., and these differences may have negative impacts on software project outcomes such as software quality and job satisfaction. This study examines the results of a nationwide survey undertaken to empirically examine and to improve our understanding of the pertinent areas where developers and testers differ. Results support that significant differences exist in perceptions between developers and testers. We conclude that these differences must be considered in order to improve software development efficiency and effectiveness.     

Software release management for component‐based software

Software release management is the process through which software is made available to and obtained by its users. Until now, this process has been relatively straightforward. However, the emergence of component‐based software is complicating software release management. Increasingly, software is constructed via the assembly of pre‐existing, independently produced, and independently released components. Both developers and users of such software are affected by these complications. Developers need to accurately document the complex and changing dependencies among the components constituting the software. Users must be involved in locating, retrieving, and assembling components in order to appropriately bring the software into their particular environment. In this paper, we introduce the problem of release management for component‐based software and discuss SRM, a prototype software release management tool we have developed that supports both developers and users in the software release management process. Copyright © 2002 John Wiley & Sons, Ltd.     

MMM: a Web-based system for sharing statistical computing modules

This prototype method management system (MMM), implemented with Web technologies, supports distributed authoring and execution of computational software modules among an interdisciplinary group of developers and users. Heterogeneous data formats, programming languages, and computing platforms pose various challenges whenever researchers are sharing and combining software modules, especially when the collaboration occurs across different traditions of scientific computing. To meet these challenges, we designed and implemented MMM. MMM is a collection of middleware services to support the interaction between software users and developers, and to facilitate the sharing of software modules across heterogeneous networks. The system design follows the World Wide Web paradigm: developers (providers) install their modules on the network in a way that allows users (consumers) to access and execute them. A prototype is available on the Web     

Collaborative conceptual design: A large software project case study

During software development, the activities of requirements analysis, functional specification, and architectural design all require a team of developers to converge on a common vision of what they are developing. There have been remarkably few studies of conceptual design during real projects. In this paper, we describe a detailed field study of a large industrial software project. We observed the development team's conceptual design activities for three months with follow-up observations and discussions over the following eight months. In this paper, we emphasize the organization of the project and how patterns of collaboration affected the team's convergence on a common vision. Three observations stand out: First, convergence on a common vision was not only painfully slow but was punctuated by several reorientations of direction; second, the design process seemed to be inherently forgetful, involving repeated resurfacing of previously discussed issues; finally, a conflict of values persisted between team members responsible for system development and those responsible for overseeing the development process. These findings have clear implications for collaborative support tools and process interventions.     

一种基于PSM的CMMI过程度量模型

软件过程技术为开发人员提供一个标准的软件开发规范,使得软件开发生产率得以提高。在众多过程技术中SEI推出的软件能力成熟度集成模型(CMMI)过程评估改进框架被广泛地接受和使用。该文阐述了CMMI评估度量框架在实施时所存在的不足,提出了一种针对CMMI并结合PSM理论的软件过程定义度量模型PSM4CMMI,分析了该模型各个组件的作用,介绍了如何利用该模型实现SPMAS系统。     

Detecting Coordination Problems in Collaborative Software Development Environments

Software development is rarely an individual effort and generally involves teams of developers collaborating to generate good reliable code. Among the software code there exist technical dependencies that arise from software components using services from other components. The different ways of assigning the design, development, and testing of these software modules to people can cause various coordination problems among them. We claim that the collaboration of the developers, designers and testers must be related to and governed by the technical task structure. These collaboration practices are handled in what we call Socio-Technical Patterns.

The TESNA project (Technical Social Network Analysis) we report on in this paper addresses this issue. We propose a method and a tool that a project manager can use in order to detect the socio-technical coordination problems. We test the method and tool in a case study of a small and innovative software product company.     

The value of a certified quality management system: the perception of internal developers

There is growing interest among internal information technology (IT) departments in implementing a certified quality management system (QMS). This paper examines the forces that have influenced organizations that supply development services to adopt QMS models and explores the relevance of these forces to internal IT developers. The perceptions of internal developers regarding the value of QMS in addressing these forces were studied using a multiple case study involving four organizations. The results suggest that while the reasons given by external developers concern mainly the marketing advantages of adopting a QMS, internal developers envisage the major advantage to be an improvement in the development process.     

Onboard：以数据驱动的敏捷软件开发协同工具

Scrum是一种兼顾计划性与灵活性的敏捷开发过程,能让软件开发团队具有快速工作和响应变化的能力.软件开发生命周期中每一个环节都会产生大量的数据,如果能记录下这些数据进行分析,并通过可视化等手段展示和反馈,则能进一步促进团队管理、项目管理,提高开发效率.现有的软件开发管理工具中,项目管理和代码管理往往是相互独立的,这导致了数据的分散和未充分利用.为推广以Scrum为核心、以数据为驱动的敏捷软件开发过程,开发了一款基于云服务的Onboard敏捷软件开发协同工具, 利用代码提交和任务的关联,创造性地将敏捷过程管理、源代码管理和项目管理有机地整合到一起,支持端到端的软件全生命周期管理,从而能记录下软件开发过程中产生的所有数据并提取有价值的信息,为中小软件开发团提供一站式的敏捷开发管理与协同服务.1)介绍了Onboard的设计理念;2)围绕着“如何利用软件开发过程中产生的数据更好地支持敏捷开发过程”和“如何评估团队成员贡献度”两大课题,全面介绍了数据可视化和数据分析在Onboard敏捷软件开发协同工具中的应用,并针对一系列相关问题提出了解决方案;3)对值得进一步研究的问题进行了展望.     

Processes versus people: How should agile software development maturity be defined?

Maturity in software development is currently defined by models such as CMMI-DEV and ISO/IEC 15504, which emphasize the need to manage, establish, measure and optimize processes. Teams that develop software using these models are guided by defined, detailed processes. However, an increasing number of teams have been implementing agile software development methods that focus on people rather than processes. What, then, is maturity for these agile teams that focus less on detailed, defined processes? This is the question we sought to answer in this study. To this end, we asked agile practitioners about their perception of the maturity level of a number of practices and how they defined maturity in agile software development. We used cluster analysis to analyze quantitative data and triangulated the results with content analysis of the qualitative data. We then proposed a new definition for agile software development maturity. The findings show that practitioners do not see maturity in agile software development as process definition or quantitative management capabilities. Rather, agile maturity means fostering more subjective capabilities, such as collaboration, communication, commitment, care, sharing and self-organization.     

面向开源生态的软件数据挖掘技术研究综述

全球开源软件生态中孕育的大众化软件生产模式正快速形成一种新型的软件生产力,在软件开发和应用各个环节发挥了巨大作用.大众化软件生产的数据规模日趋庞大、协同范围不断扩展、管理模式高度精简,这些全球化特征使其在软件复用、协同开发、知识管理等环节面临诸多挑战,迫切需要新的理论指导和工具支持.本文首先界定了大众化软件生产活动的分布范围、基本过程和数据形态,然后从软件复用、协同开发、知识管理三个核心环节对开源社区数据挖掘技术的研究工作进行了归类与分析,最后总结了该领域研究工作存在的问题和未来发展趋势.