敏捷开发过程与CMMI实施融合研究

介绍敏捷开发过程的基本特征,比较敏捷开发与传统项目管理之间的差别,提出敏捷开发过程与CMMI实施的融合策略。     

敏捷开发平台的设计

敏捷开发平台是支持敏捷过程的软件开发平台,敏捷开发平台通过生成Java代码和读取存放在数据库中的配置数据,实现系统的可配置.这个平台包括一系列敏捷开发工具,敏捷组件、敏捷表单、敏捷查询等;同时,敏捷开发平台还实现了一套敏捷工作流系统和敏捷数据交换平台.敏捷开发平台对数据库的设计做了一些标准规范,有利于数据资源的有效利用.敏捷开发平台实现了系统设计标准化,能够支持在大型信息化项目中采用敏捷开发过程.     

敏捷型需求工程实践探索,拥抱变化

作为软件工程最重要的子领域之一,需求工程在自20世纪80年代以来就一直是相关方向的研究热点之一。近年来随着敏捷开发的越来越流行,对传统的需求工程方法也做出了巨大的挑战。敏捷开发以快速响应变化为特点与优势,与此相应地,如何制定新的需求工程策略以适合敏捷过程,拥抱变化,成为了敏捷开发实践所不容回避的一个话题。本文对敏捷开发的过程进行了深入分析,提出了一套较可行的敏捷型需求工程实践方法,希望为中小型团队实践敏捷开发提供一些参考与建议。     

基于Scrum敏捷开发的软件实训设计

针对采用传统过程控制的软件实训类课程中开发文档与编码脱节,学生无法深入理解和应用分析与设计理念等问题,介绍敏捷开发过程的基本思想以及Scrum敏捷开发过程引入软件实训教学中的现状,阐述新的基于Scrum敏捷开发过程的软件实训教学方案以及一套完整的软件实训案例,并总结分析该教学设计方案的有效性。     

基于敏捷思想的iOS平台软件的设计与实现

软件的开发过程与最初的计划保持一致已经不再是当今软件开发的主要目标了,如何应对客户对于需求的不断变化,快速地交付高质量的软件并做到让客户满意,已经成为了一个软件开发公司能否在当今竞争激烈的软件行业中得以生存的关键。文中在对统一软件过程以及敏捷方法的优势和局限性研究与分析的基础上,利用敏捷思想对统一过程进行适当裁剪并利用统一思想对敏捷开发进行合理扩充,提出了一种基于统一过程和敏捷方法的软件开发过程,成功地将敏捷过程应用到iOS智能手机操作系统开发这一实际的项目中。实践证明,敏捷开发方法在应对需求频繁变化和提高软件开发效率方面均起到了很好的效果。     

维护开发中敏捷方法的应用

该文主要介绍了敏捷软件开发的几种主要方法以及在维护性开发中的实际应用,并与传统重型开发法进行了对比,表明敏捷软件开发方法在软件开发中的一些先进之处及存在的一些问题;同时介绍了软件的维护及维护性开发的重要意义,在此基础上提出将敏捷方法用于软件的维护性开发中,对该应用的可行性和具体的实现过程给出了分析,并给出开发过程的实例说明,证明了该方法的有效性,说明敏捷方法在软件维护性开发中的应用具有非常强的实际应用研究价值。     

试议软件敏捷项目中的需求开发

软件产品开发中,需求管理是决定成败的前提和关键。在敏捷开发模型中,传统软件开发过程中的需求开发和管理实践,会因为不能很好适应快速交付等敏捷原则,反而会对开发过程造成困惑和障碍。根据实际项目操作经验,参考敏捷开发模型,提出需求开发的迭代开发方法。     

戴明循环在敏捷软件质量管理中的应用方法研究

敏捷软件过程凭借对变更的适应能力被越来越多的软件企业采用,同时敏捷开发对软件质量管理也提出很大挑战。针对敏捷开发过程在软件质量保证中的特点,以实际项目为例提出一种基于戴明循环的软件测试过程。这种测试过程对软件测试流程实行自反馈方式的改进,提高了软件测试的有效性,降低了资源开销,使软件测试过程能够适应敏捷开发需要。     

敏捷时代助力软件企业创业

围绕软件企业创业背景,使用敏捷开发过程与方法,从以人为本的软件开发团队、我们的客户、需求分析、文档编制的重要性、敏捷开发的缺点5个方面加以分析和阐述。     

极限编程中的质量控制

极限编程是近年来非常流行的敏捷软件开发方法,与其它敏捷软件开发方法一样,强调软件开发过程的自适应性和以人优先的价值观1 ,这与传统的重量级软件开发方法强调对开发过程的控制相反.那么,敏捷软件开发方法能否开发出高质量的软件产品呢?本文探讨在极限编程中如何进行软件质量控制,使其既能保持"敏捷"的特点,又能作为一种成熟的软件开发过程,为客户提供高质量的软件产品.     

Understanding agile software development practices using shared mental models theory

ContextAgile software development is an alternative software development methodology that originated from practice to encourage collaboration between developers and users, to leverage rapid development cycles, and to respond to changes in a dynamic environment. Although agile practices are widely used in organizations, academics call for more theoretical research to understand the value of agile software development methodologies.ObjectiveThis study uses shared mental models theory as a lens to examine practices from agile software methodologies to understand how agile practices enable software development teams to work together to complete tasks and work together effectively as a team.MethodA conceptual analysis of specific agile practices was conducted using the lens of shared mental models theory. Three agile practices from Xtreme Programming and Scrum are examined in detail, system metaphor, stand-up meeting, and on-site customer, using shared mental models theory.ResultsExamining agile practices using shared mental models theory elucidates how agile practices improve collaboration during the software development process. The results explain how agile practices contribute toward a shared understanding and enhanced collaboration within the software development team.ConclusionsThis conceptual analysis demonstrates the value of agile practices in developing shared mental models (i.e. shared understanding) among developers and customers in software development teams. Some agile practices are useful in developing a shared understanding about the tasks to be completed, while other agile practices create shared mental models about team processes and team interactions. To elicit the desired outcomes of agile software development methods, software development teams should consider whether or not agile practices are used in a manner that enhances the team’s shared understanding. Using three specific agile practices as examples, this research demonstrates how theory, such as shared mental models theory, can enhance our understanding regarding how agile practices are useful in enhancing collaboration in the workplace.     

“Leagile” software development: An experience report analysis of the application of lean approaches in agile software development

In recent years there has been a noticeable shift in attention from those who use agile software development toward lean software development, often labelled as a shift “from agile to lean”. However, the reality may not be as simple or linear as this label implies. To provide a better understanding of lean software development approaches and how they are applied in agile software development, we have examined 30 experience reports published in past agile software conferences in which experiences of applying lean approaches in agile software development were reported. The analysis identified six types of lean application. The results of our study show that lean can be applied in agile processes in different manners for different purposes. Lean concepts, principles and practices are most often used for continuous agile process improvement, with the most recent introduction being the kanban approach, introducing a continuous, flow-based substitute to time-boxed agile processes.     

传统软件开发团队如何转型为敏捷开发团队

通过在一个团队中推行敏捷开发流程,探讨团队如何根据自身的情况选取相应的敏捷开发方法以及团队由原有的开发方法转为使用敏捷开发方法的初期用何种方法才能有效的使团队接受敏捷,并阐述使用这些方法的原因。     

敏捷组织的复杂适应性及其行为模式研究

从CAS理论出发,分析了敏捷软件开发方法的复杂适应性,指出敏捷开发组织是一个复杂适应性系统,并建立敏捷开发组织的个体与环境关系的回声模型以及主体行为模式的刺激-反应模型,为敏捷软件开发方法的运行机制和持续改进提供理论依据。     

Strengths and barriers behind the successful agile deployment—insights from the three software intensive companies in Finland

The number of success stories being reported concerning agile software development has led to an increase in interest among industries and research communities. The purpose of this paper is to identify strengths and barriers for ‘successful agile deployment’ in the software companies. This knowledge can benefit software companies planning their current strategy for agile deployment. Analysis of 57 developers, architects, project managers, customers, quality managers, and line and product managers in three case companies identifies 71 strengths and 169 barriers of agile deployment. The analysis revealed the importance of management providing the necessary goals and support for agile development. It also indicated the significance of defining a tailored process model and giving developers the freedom to improve their own agile development process continuously during agile deployment. The identified barriers, strengths and recommendations can be used as a checklist for planning and/or monitoring the effectiveness of agile deployment in software companies. By identifying the barriers and strengths of agile deployment, the paper deepens understanding of this highly relevant but relatively under-researched phenomenon and contributes to the literature on agile deployment and software process improvement.     

嵌入式系统开发中敏捷方法的应用研究综述

伴随着计算机技术的迅速发展,嵌入式系统软件的应用领域得以不断拓宽,这使得嵌入式系统开发面临着日益严峻的质量、成本以及项目周期等方面的压力.另一方面,敏捷方法已在传统的软件项目当中得到越来越多的应用.很多研究都表明,敏捷方法在适应需求变更、提升生产效率和最终产品的质量方面都发挥出显著的作用.因此,在嵌入式系统软件开发中应用敏捷方法,自然也得到研究者和实践者的日益关注.应用系统评价(systematicreview)方法,试图尽可能系统地了解嵌入式系统开发过程中敏捷方法的应用状况和研究进展.通过对敏捷宣言提出以来12年间49篇相关文献的概况和分析,试图回答如下3 个问题：1) 在不同类型的嵌入式系统开发中,敏捷方法的总体应用情况如何? 2) 敏捷方法或实践是如何解决各类嵌入式软件开发中的挑战的? 3) 敏捷方法(实践)该如何通过扩展和改进,以更好地适应嵌入式系统开发?研究表明,尽管应用程度存在一定的差异,但敏捷方法已在不同类型的嵌入式开发中得到了应用.传统的敏捷方法也需要进行多种改变,以适应这些不同类型的嵌入式开发项目的特征.     

Applying agile methods to aircraft embedded software: an experimental analysis

This paper discusses the applicability of agile methods to aircraft embedded software development. It presents the main results of an experiment that combines agile practices from Scrum with model‐based development and distributed development. The experiment consists of the development of an aircraft cockpit display system divided in five distributed teams. Three features are analysed and quantified, using the output artefacts of each team: the artefacts' quality, the adherence to agile methods, and the adherence to standard DO‐178C. The main conclusion of the experiment is that there is a high correlation between the adherence to agile methods and the artefacts' quality, motivating the use of agile methods in aircraft industry. Also, the experiment evinced that agile methods does not specifically address the integration of distributed teams and the hardware/software integration. This lacuna affects the artefacts' quality. The results of the experiment emphasize the importance of concentrating future work in the proposal of specific agile practices for these activities. Copyright © 2017 John Wiley & Sons, Ltd.