敏捷开发中软件架构设计与实践

软件架构在软件开发中起着非常关键的作用.在传统软件开发中,软件架构难以改变,对架构的调整需要付出较大成本.与此相比,敏捷开发(Agile Development)是轻量级的,拥抱变化的,能快速响应变化的开发方法.在对敏捷软件开发及架构分析的基础上,提出一套敏捷开发中架构设计的方法论.结合实际项目中的架构设计验证该方法论的有效性.     

MCU平台的嵌入式系统软件设计研究

嵌入式系统的运行需要可靠性和实时性的保证,因此良好的可靠性和实时性是嵌入式系统软件设计的重要标准。同时为了使软件系统的鲁棒性更强,嵌入式系统的设计需要一个非常好的软件架构。这里介绍了一种基于MCU平台的嵌入式系统软件架构方法。在这个方法中,事件驱动机制的引入满足了对软件架构的要求,主程序中不仅采用了优先调度机制,同时也加入了软件抗干扰措施,这些都使系统的实时性和可靠性得到了明显的提高。设计实验比较由该方法得到的软件架构与原始软件架构的实时性,得出由该方法优化后的软件架构确实具有更好的性能。     

面向构件的门诊部信息管理系统软件架构

构件化软件的设计集中于软件体系结构设计,其最主要的特征在于目标系统由大量可复用构件组成,这就要求在设计阶段应当设计出满足需求的软件体系结构。以一个门诊部信息管理系统软件架构为例,介绍了面向构件的软件架构方法,并对系统架构选型进行分析,提出了本系统的软件架构,为基于构件技术的系统实现提供良好的依据。     

Agile方法研究综述

本文综述了近来新出现的Agile方法,对其应用范围、价值系统、核心实践给出了阐述,并介绍了XP、SCRUM、Crystal等主要的Agile方法及其发展趋势,在此基础上,给出了CMM与Agile方法之间的比较分析,最后提出了Agile方法待研究的问题。     

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

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

设计模式在软件架构可靠性评估平台中的应用

软件架构设计对软件质量有很大影响。本文设计了软件架构可靠性评估平台,可用于在软件设计阶段对基于软件架构的软件可靠性进行评估。在该平台的设计开发过程中使用了一些设计模式,包括组合模式、抽象工厂模式、访问者模式、原型模式等,从而优化了系统结构,使系统具有很好的灵活性。     

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

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

双核微处理器实时系统的软件架构方法

针对双核微处理器在工业控制领域的应用,探讨了基于共享内存的双核处理器软件架构的设计方法,主要分析讨论了双核之间的通信方法、数据共享策略以及双核任务分配方法。以F28M35双核处理器为例,介绍了该处理器资源结构、双核间的通信机制以及共享内存的使用方法。设计了一种以系统控制块数据结构为核心的软件架构方法,并成功运用在注塑机控制系统中。     

基于场景轻量级软件构架分析方法

软件架构是软件开发的基础,决定了软件产品的质量,它的重要性不言而喻。随着计算机软件开发技术的发展和进步,目前评价一个系统的软件架构变得越来越重要。在架构权衡分析方法与软件架构分析方法的基础上提出了一种基于场景软件架构分析方法,这种方法主要是基于场景的分析过程,再构建相对应的评价指标与场景库,给软件架构分析建立了一种轻量级分析手法。     

基于AJAX三层软件架构的可重用解决方案

基于AJAX的技术在富互联网应用（RIA）当中扮演着重要角色,同时,基于AJAX的三层软件架构也就成为一种经典的软件开发模式。研究表明,在基于AJAX的三层软件架构中,数据访问层与业务逻辑层可设计成通用模块且表示层可划分为通用模块与专用模块。概括地说,对于基于AJAX的三层软件架构而言,开发者通过通用化设计可以找到一个具有良好扩展性的可重用解决方案。     

基于在线检测技术的敏捷软件开发方法的模型

针对敏捷软件开发方法尚未从本质上消除控制滞后性的问题,运用发酵调控学领域的在线检测技术和反馈控制技术,设定三个控制目标函数,设置若干检测参数及控制参数,建立基于在线检测技术以及反馈控制技术的敏捷软件开发方法的模型,研究控制变量、可测变量与控制目标变量三者之间的关系,从而解决控制滞后问题,实现敏捷软件过程的优化。     

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

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

Agile MERODE: a model-driven software engineering method for user-centric and value-based development

Agile is often associated with a lack of architectural thinking causing technical debt but has the advantage of user centricity and a strong focus on value. Model-driven software engineering (MDSE) strongly performs for building a quality architecture and code, but lacks focus on user requirements and tends to consider development as a monolithic whole. The combination of Agile and MDSE has been explored, but a convincing integrated method has not been proposed yet. This paper addresses this gap by exploring the specific combination of MERODE—as an example of a proven MDSE method—with Scrum, a reference agile method offering a concrete (sprint-based) life cycle management on the basis of user stories. The method resulting of this integration is called Agile MERODE; it is driven by user stories, themselves associated with behavior-driven development scenarios. It allows for domain-driven design and permits fast development from domain models by means of code generation. An illustrative example further clarifies the practical application of Agile MERODE, while a case study shows the planning game application in the case’s context. While the approach, in its entirety, allows reducing technical debt by building the architecture in a logical, consistent and complete manner, introducing MDSE involves a trade-off with pure value-driven development. Agile MERODE contributes to the state of the art by showing how to increase user centricity in MDSE, how to align model-driven engineering with the Scrum cycle, and how to reduce the technical debt of agile developments yet remaining value-focused.

     

敏捷开发平台的设计

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

基于MDA的模式化软件设计方法与应用

以环境保护信息系统的建设为例,把模型驱动体系结构和模式化软件设计结合起来形成 了基于MDA来模式化设计方法。该方法可以降低复用模型的粒度,支持项目之间和业务领域之间 的模型复用,提高软件开发效率。     

6 Sigma 管理在敏捷软件开发中的应用

6 Sigma是过程量化与控制、过程改进的有力工具和有效方法,针对敏捷软件开发方法现阶段在质量管理和过程控制上可能存在的问题,分析了6Sigma在敏捷软件开发方法中应用的可行性和价值,提出了基于6Sigma的敏捷软件开发方法的YfX黑盒模型和白盒模型,并进行DMAIC分析,实现敏捷开发方法的持续改进。     

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.     

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.     

Agile transition and adoption human-related challenges and issues: A Grounded Theory approach

Agile methods in software development have been introduced to cope with the inherent problems of the traditional methods. The increasing prevalence of using these methods reflects their important role in the future of software development. However, leaving traditional approach and adapting to Agile approach has been a central attention of the researchers. Indeed, Agile transition needs enough time and effort and most often is subject to several challenges and barriers, mainly because of its people-centric nature. Human-related challenges in several studies have been reported as the major transition challenges. However, exploring the primary origins and reasons of these challenges has received less effort in a large-scale research study. A Grounded Theory in context of Agile software development has been conducted involving 49 Agile practitioners across the 13 different countries. This study identified different aspects of human-related challenges throughout Agile transition process. The results of this study show that the root of the emerged issues is the people's perceptions about Agile transition. The main purpose of this paper is to describe the origins and reasons of these challenges and issues in order to help software companies and development teams. Considering the findings may help them to facilitate Agile transition process with less cost, time and effort and to get better results by considering these potential challenges.