基于Agile方法的软件架构设计与实现

介绍了一种新兴的Agile软件开发方法及其特点,提出了基于Agile的软件架构设计思路和开发方法。在此基础上,结合事例实现了基于Agile方法的软件架构设计与开发,指出了在Agile方法的发展过程中需要解决的一些问题。     

新版本带来新风尚

2005年11期,我们刊登了《Agile的中国初体验》,报道刚刚进入中国市场的PLM厂商Agile,并且专访了Agile软件公司大中国区总经理廖志逢先生.经过了半年的时间,Agile于2006年7月在中国地区发布了新的版本Agile9.2.1.     

基于Agile方法的软件设计实现

经济和科学技术的迅猛发展,对软件开发来说意味着需求的迅速变化。研究并实践Agile方法对软件开发意义重大。但是Agile方法也面临一些亟需解决的问题。Agile方法特别强调软件开发中相关人员间信息的交流,这种信息的交流必然要受到不同人文化差异的制约。     

敏捷需求建模的研究与设计

文章综合研究了敏捷方法与极限编程开发过程,结合需求工程方法,设计提出了基于敏捷思想的敏捷需求建模（Agile Requiremenb Modeling。简称ARM）。敏捷需求建模作为各种敏捷方法在软件需求中的实践补充,能够满足CMMI的目标。可以为中小型软件开发组织的行动指南提供参考。     

极限编程(XP)在工程质量监管系统中的应用

"极限编程"(eXtreme Programming,简称XP)是目前最流行的敏捷软件开发方法(Agile Software Development,ASD).通过XP在实际项目中的应用"实践",本文将对XP的理论和实践方法进行探讨,并衡量XP方法在项目中的应用效果,给出实际应用XP方法的一些建议.     

基于Test RT的嵌入式系统自动化测试

自动化测试在Agile开发过程中非常重要。但是在嵌入式系统中,自动化测试一直没有找到一种行之有效的方法,从而严重影响了软件质量和开发效率。本文提出了一种基于Test RT的自动化测试方案,描述了实施的技术细节并比较了与其他方案的优势,为Agile的广泛应用铺平了道路。     

面向OWL知识的问答系统Agile

介绍了一个面向OWL知识的问答系统Agile,并重阐述了其在问题规范和知识索引方面的技术方案。为了得到合适的映射单位,Agile系统定义了两个数据结构用于规范问题和OWL本体知识字典,并借助自然语言处理工具和OWL解析工具将两种源知识进行了形式化。实验分析表明:与现有网络问答系统相比,Agile系统能够处理的问题领域和形式更加丰富。     

PLM成中国制造业信息化利器——Agile锁定高科技电子市场

7月19日,美国PLM厂商Agile公司在北京宣布Agile9.2.1正式经过客户认可计划(customeracceptanceprogram)上线。Agile公司在全球覆盖高科技电子、生命科学、消费性包装等三大领域,而未来几年将着力拓展中国的高科技电子市场。Agile企业战略部执行副总裁ChrisW o n g指出,近年来,中国制造业开始考虑如何在全球市场上对自己的品牌进行革新、开发并推向市场。经过多年的市场推广,P L M系统被应用到了各个领域,开始帮助航空航天、电子、机械、军工等制造行业不断地提高自己的核心竞争力——P L M正在成为中国制造业实现腾飞的信息化利器。与…     

级限编程（XP）在工程质量监管系统中的应用

“极限编程”（extreme Programming．简称XP）是目前最流行的敏捷软件开发方法（Agile Software Development，ASD）。通过XP在实际项目中的应用“实践”，本文将对XP的理论和实践方法进行探讨．并衡量XP方法在项目中的应用效果，给出实际应用XP方法的一些建议。     

我的Lean＆Agile项目经历

精简和敏捷是指制造业里的敏捷管理和精简库存的意思。精简和敏捷管理在90年代初才被引入软件制造业,我曾有幸经历了一次Lean&Agile项目,感触颇深,下面我将和读者分享我的Lean&Agile项目经历。     

A statistical analysis of the effects of Scrum and Kanban on software development projects

Traditionally, software development processes have relied on the use of the “Waterfall” and “Vee” models. Later, Agile methodologies were used to handle the challenges of managing complex projects during the development phase. Agile methodologies are a group of incremental and iterative methods that are more effective, and have been used in project management. Kanban and Scrum are two powerful Agile project management approaches in software development. The objective of Scrum and Kanban is achieved by optimizing the development process by identifying the tasks, managing time more effectively, and setting-up teams. A review of the literature reveals that there is a lack of statistical evidence to conclude which methodology is more effective in dealing with the traditional project management factors of budget handling, risk control, quality of the project, available resources, having clear project scope, and schedule handling. This research statistically compares the effectiveness of the Scrum and Kanban methods in terms of their effects on the project management factors for software development projects. Numerical analysis is performed based on survey responses from those with experience in the Scrum and Kanban methods. Results suggest that both Scrum and Kanban lead to the development of successful projects, and that the Kanban method can be better than the Scrum method in terms of managing project schedule.     

敏捷方法在软件项目开发中的实践

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

基于UML的敏捷建模方法研究

企业要想不断的适应社会的快速变化,必须在需求和技术不断变化的过程中实现快速的软件开发.UML作为一个有效的建模工具,可以对软件开发的过程进行可视化,敏捷建模是一种有效的、轻量的软件开发方法.基于UML的敏捷建模方法研究,将敏捷方法贯穿于整个系统分析建模过程中,通过创建简单内容,采用迭代、递增的方法建模,达到包容需求变化的目的,提高软件开发的质量和速度,为企业创造竞争优势.     

敏捷开发方法及一个非典型应用实例

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

敏捷软件开发与计划驱动开发的概述比较

人们在设想、确定以及创建软件时,身边的环境不断在变更.敏捷是为了在动荡的业务环境中获益而创造变革和响应变革的能力.极限编程是最著名的敏捷软件开发方法.传统的开发侧重于计划和架构,计划驱动开发关注的是软件的质量和过程的可预见性.计划驱动开发最佳范例是能力成熟度模型.两种表面上有不同观点的方法在争夺着软件开发的主导权,对敏捷软件开发与计划驱动开发进行了概述,并就特征、擅长领域和关键要素等进行比较.     

Dynamic organization and methodology for agile virtual enterprises

With the trend of the worldwide market competition ,the global agile manufacturing will become an advanced manufacturing technology in 21st century,and the Agile Virtual Enterprise(AVE) will also become a new organization form of manufacturing enterprises.As AVE is a complicated enterprise,how to build an optimal AVE organuization is a difficult problem.In this paper,based on the analysis of the AVE organization,the methodology for AVE including enterprise architecture,reference model,enterprise modeling methods and toolkit,guideline for system implementation is proposed.This paper also presents a Virtual Organization Integrated Support Environment(VOISE),which provides the computer-aided support for rapidly duilding an optimal AVE.     

Supporting the deployment of ISO-based project management processes with agile metrics

Agile approaches are well perceived in software development companies. These approaches are not faced with traditional process models. This research analyses how by defining and monitoring a set of Agile metrics, Agile mature companies can be also conformant with the best practices proposed by the targeted ISO process reference models. Conformance has been identified with five Technical Management processes of the ISO/IEC/IEEE 12207 standard and with two activities of the Project Management process of the ISO/IEC TR 29110-5-1-2 standard. The findings may be of the interest of those Agile settings that need to work according to the process model established in the company.     

涉众为中心的敏捷需求建模

提出一种将涉众为中心和敏捷方法有机结合的敏捷需求建模方法。所有软件系统需求获取以涉众为中心,基于涉众扩展特征建立涉众Power/Interest分布图来确定涉众优先级,并用优先级处理不同涉众之间的需求冲突,根据涉众为中心的敏捷需求方法,提出敏捷需求实践方法,融合敏捷方法的短周期、演化、增量、迭代、重构、反馈机制,使软件系统需求建模过程更加完备、精确、高效、快捷,用双变迁Petri网DTPN为该方法建立形式化敏捷需求模型,为软件系统需求建模提出了一种新的方法。     

Using metrics in Agile and Lean Software Development – A systematic literature review of industrial studies

ContextSoftware industry has widely adopted Agile software development methods. Agile literature proposes a few key metrics but little is known of the actual metrics use in Agile teams.ObjectiveThe objective of this paper is to increase knowledge of the reasons for and effects of using metrics in industrial Agile development. We focus on the metrics that Agile teams use, rather than the ones used from outside by software engineering researchers. In addition, we analyse the influence of the used metrics.MethodThis paper presents a systematic literature review (SLR) on using metrics in industrial Agile software development. We identified 774 papers, which we reduced to 30 primary studies through our paper selection process.ResultsThe results indicate that the reasons for and the effects of using metrics are focused on the following areas: sprint planning, progress tracking, software quality measurement, fixing software process problems, and motivating people. Additionally, we show that although Agile teams use many metrics suggested in the Agile literature, they also use many custom metrics. Finally, the most influential metrics in the primary studies are Velocity and Effort estimate.ConclusionThe use of metrics in Agile software development is similar to Traditional software development. Projects and sprints need to be planned and tracked. Quality needs to be measured. Problems in the process need to be identified and fixed. Future work should focus on metrics that had high importance but low prevalence in our study, as they can offer the largest impact to the software industry.