首页 | 本学科首页   官方微博 | 高级检索  
相似文献
 共查询到19条相似文献,搜索用时 130 毫秒
1.
敏捷型软件开发方法与极限编程概述   总被引:9,自引:1,他引:9  
李航 《计算机工程与设计》2003,24(10):116-118,121
在当前需求快速变动的背景下,传统的软件工程方法显得难以适应。近年来出现了一类新的轻量级的软件开发方法,它们被统称为敏捷型软件开发方法。介绍了敏捷型软件开发方法的背景、原则和特点,将其与传统软件工程方法作了比较;还重点介绍了当前国外流行的敏捷型软件开发方法:XP(eXtreme Programming——极限编程)的开发流程和实践准则。  相似文献   

2.
敏捷开发是近十年来兴起的软件开发模式,2012年11月第七届中国敏捷软件开发大会在北京、深圳、上海三地举办,为国内外敏捷实践者提供了开放的交流平台。从软件开发生命周期的角度分析比较了敏捷方法与传统方法的优劣,并提出敏捷方法在实践中的改进建议。  相似文献   

3.
随着计算机相关设备的不断普及与软件开发技术的完善,软件设计与开发逐渐趋于个性化、多元化,对软件开发的质量与效率也提出了新的要求。然而,传统的瀑布式开发方式较为笨重难以满足社会发展需求,亟须一种更加便捷灵活的开发方式。21世纪初期,敏捷思想作为一种轻量级的软件开发思想逐渐被软件开发人员所认可和接受,逐渐应用于软件开发与设计中。因此,该文基于敏捷思想的基本概念与内涵等探究敏捷思想在软件开发中的应用。  相似文献   

4.
徐琳  陈荔  杨丽 《计算机系统应用》2011,20(6):85-88,20
6 Sigma是过程量化与控制、过程改进的有力工具和有效方法,针对敏捷软件开发方法现阶段在质量管理和过程控制上可能存在的问题,分析了6Sigma在敏捷软件开发方法中应用的可行性和价值,提出了基于6Sigma的敏捷软件开发方法的YfX黑盒模型和白盒模型,并进行DMAIC分析,实现敏捷开发方法的持续改进。  相似文献   

5.
王冲 《福建电脑》2011,27(4):61-62,129
敏捷开发是软件工程领域中新兴的一种软件开发模式,作为一种流行趋势的新兴技术,不少公司都在尝试实施敏捷开发转型。本文对这种新兴的敏捷开发与传统软件开发模式作了比较,通过比较阐述敏捷开发思想的优越性,并给出了敏捷开发在教学中的一些建议。  相似文献   

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

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

8.
敏捷软件开发中的风险管理   总被引:2,自引:0,他引:2  
敏捷软件开发的诞生源于对高失败率的传统软件开发方法的改进和探索,是一种处理软件开发过程中各个级别上风险的软件开发方法。但是敏捷软件开发很少明确地看到风险管理的内容,经常缺乏对风险的关注。本文根据敏捷软件开发的特点和项目风险管理理论,从人、过程、产品和技术四个纬度就如何防范和缓解敏捷软件开发风险进行了探析。  相似文献   

9.
敏捷方法的研究与实践   总被引:10,自引:1,他引:9  
沈雷  沈备军 《计算机工程》2005,31(7):219-222
敏捷软件开发方法正逐渐成为软件开发的新模式。针对这一趋势,文章分析了敏捷方法的核心理念和特点,并结合RUP、XP、FDD等敏捷方法,提出了适应中小型软件企业的敏捷软件开发方法——AUP,并成功地进行了实践。  相似文献   

10.
谢然 《互联网周刊》2014,(14):42-43
正世界5大软件开发教父之一的Martin Fowler认为,当前只有敏捷的软件开发模式才能使IT跟上业务变化的脚步,才能使软件在快速交付的同时保证高质量和低成本。若问现今软件开发模式的热词,那就非"敏捷"莫属了!敏捷开发的确蕴涵着无限商机,但同时也是对中国软件产业的严峻挑战。对于起步远远滞后于西方的中国软件业来说,各种提高软件开发速度及降低软件开发成本的方式和措施都是值得探讨与借鉴的。笔者认为敏捷开发模式对中国的软件  相似文献   

11.
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.  相似文献   

12.
敏捷方法是一种面临迅速变化的需求快速开发软件的新开发方法,这种方法以快捷、轻便的思维方式,迅速解决了一些传统软件开发企业的生产效率问题,得到了迅速的推广。介绍了敏捷软件过程与极限编程的主要内容,并以一个债权管理系统的开发为例,展示了其实际应用过程。  相似文献   

13.
分析CMMI的特点以及在实际应用中遇到的问题,以CMMI理论模型为基础,通过适当的裁剪,并结合敏捷软件开发的思想,提出基于CMMI的轻型软件质量保证框架(SQAF).SQAF构建在CMMI的十个过程域上,沿用了CMMI中的主要角色和组,结合了敏捷软件开发的思想和实践.SQAF主要针对中小软件企业,易于实施和应用.  相似文献   

14.
敏捷方法在软件项目开发中的实践   总被引:1,自引:0,他引:1  
目前很多企业内中小型软件项目面临开发时间紧迫、人手不足、需求不断变化的困难,传统重量级的软件开发方法无法应对这样的挑战.敏捷方法是基于实践的软件开发方法学,为解决这类轻量级项目管理和开发所碰到的问题提供了新的思路.通过分析敏捷方法的主要目标、观点和原则,并结合一个实际的管理信息系统项目开发,从项目计划、项目文档、重构的改进和项目维护的4个方面探讨了敏捷方法的实践应用.实践证明,采用敏捷方法的观点和原则进行必要的改进,能取得项目开发的成功.  相似文献   

15.
敏捷开发方法及一个非典型应用实例   总被引:7,自引:0,他引:7  
敏捷(agile)软件开发方法是近几年来新兴的一种软件开发方法,它的主要特征是允许对过程进行自主调整,并且强调软件开发中人的因素,和传统开发方法有着很多不同。本文对这一新的软件开发方法作一些简单的讨论,简要介绍了其中有代表性的几种方法,并给出了自己的一个应用实例。  相似文献   

16.
In the last years the interest in developing research on integration of usability and agile software development has been increasing. The number of systematic literature reviews, systematic mapping studies and non-systematic reviews, related to this thematic has also increased. Nevertheless, there is no analysis on the quality of these published secondary studies, nor is there a consolidated research that brings the answer of how to integrate these two areas. The goal of this paper is to categorize secondary studies related to the integration of usability and agile software development and present a critical analysis on the quality of the selected studies. To accomplish this goal a tertiary study was performed to categorize the related studies selected. Initially 3,065 papers were identified and further narrowed to 14 by applying exclusion criteria and analysis. We classified the selected studies as systematic literature reviews, systematic mapping studies and non-systematic literature reviews to report the data analysis. As a result of this study different forms to integrate usability and agile software development were detected as well as the various challenges that must be overcome for the integration success. Six main categories were identified to represent ways of integrating usability into agile development: processes, techniques, practices, recommendations, principles and different approaches. Regarding to the challenges for the integration seven main categories were also identified: issues related to tests, time, work balance, modularization, feedback, prioritization, and documentation. Although the interest in researching the integration of usability and agile software development has increased in the last years, mostly of the analyzed studies neglected the quality criteria and presented difficulties to use methods to synthetize the research results. Despite this, it has been realized that the integration of usability with agile software development is possible and is strongly aligned with user-centered design. The initial studies indicated a separation of activities and roles into specific tracks with parallel work to treat usability in agile software development, but the trend is no longer to manage and control these activities in separate ways, so new challenges are becoming to appear. Although we have identified several points of tension, the integration does not become unfeasible.  相似文献   

17.
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.  相似文献   

18.
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.  相似文献   

19.
Agile software development provides a way to organise the complex task of multi-participant software development while accommodating constant project change. Agile software development is well accepted in the practitioner community but there is little understanding of how such projects achieve effective coordination, which is known to be critical in successful software projects. A theoretical model of coordination in the agile software development context is presented based on empirical data from three cases of co-located agile software development. Many practices in these projects act as coordination mechanisms, which together form a coordination strategy. Coordination strategy in this context has three components: synchronisation, structure, and boundary spanning. Coordination effectiveness has two components: implicit and explicit. The theoretical model of coordination in agile software development projects proposes that an agile coordination strategy increases coordination effectiveness. This model has application for practitioners who want to select appropriate practices from agile methods to ensure they achieve coordination coverage in their project. For the field of information systems development, this theory contributes to knowledge of coordination and coordination effectiveness in the context of agile software development.  相似文献   

设为首页 | 免责声明 | 关于勤云 | 加入收藏

Copyright©北京勤云科技发展有限公司  京ICP备09084417号