The Impact of Integrating Agile Software Development and Model-Driven Development: A Comparative Case Study

Agile Software Development plays a quintessential part in modern day software development. The term Agile refers to frequent reassessment and adaptation of plans and techniques and dividing tasks into shorter tasks for efficiency. Agile Software Development differs considerably from Traditional Software Development Methodology. Agile methodology aims to deliver features of a software project in small steps within a short duration of time (i.e., iterations). Hence, it becomes necessary to use agile software development methodology in todays’ fast-paced revolutionizing software industry. This paper discusses the important subtopics of Agile Software Development which gathered by reviewing/surveying of research papers. First, is the Agile Planning Life Cycle which consists of various stages such as pre-planning, planning, release planning and product backlog management. In the next section, principles such as Scrum, Extreme Programming, Kanban and Lean are discussed. The last section comprises the impact of Agile principles on software quality.

Download Full-text

MoDSEL

Formal and Practical Aspects of Domain-Specific Languages ◽

10.4018/978-1-4666-2092-6.ch020 ◽

2012 ◽

pp. 572-594

Author(s):

Ersin Er ◽

Bedir Tekinerdogan

Keyword(s):

Software Development ◽

Impact Analysis ◽

Software Evolution ◽

Academic Research ◽

Model Driven ◽

Model Driven Software Development ◽

Basic Concepts ◽

The Impact ◽

Development And Evolution

Model-Driven Software Development (MDSD) aims to support the development and evolution of software intensive systems using the basic concepts of model, metamodel, and model transformation. In parallel with the ongoing academic research, MDSD is more and more applied in industrial practices. Like conventional non-MDSD practices, MDSD systems are also subject to changing requirements and have to cope with evolution. In this chapter, the authors provide a scenario-based approach for documenting and analyzing the impact of changes that apply to model-driven development systems. To model the composition and evolution of an MDSD system, they developed the so-called Model-Driven Software Evolution Language (MoDSEL) which is based on a megamodel for MDSD. MoDSEL includes explicit language abstractions to specify both the model elements of an MDSD system and the evolution scenarios that might apply to model elements. Based on MoDSEL specifications, an impact analysis is performed to assess the impact of evolution scenarios and the sensitivity of model elements. A case study is provided to show different kind of evolution scenarios and the required adaptations to model elements.

Download Full-text

Agile Software Development

Security-Aware Systems Applications and Software Development Methods ◽

10.4018/978-1-4666-1580-9.ch001 ◽

2012 ◽

pp. 1-15

Author(s):

Torstein Nicolaysen ◽

Richard Sassoon ◽

Maria B. Line ◽

Martin Gilje Jaatun

Keyword(s):

Software Development ◽

Agile Software Development ◽

Agile Development ◽

Implementation Team ◽

Agile Methodologies ◽

Development Organizations ◽

Development Lifecycle ◽

Software Development Lifecycle ◽

Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Download Full-text

Fixed Priced Projects in Agile

Advances in Systems Analysis, Software Engineering, and High Performance Computing - Emerging Innovations in Agile Software Development ◽

10.4018/978-1-4666-9858-1.ch012 ◽

2016 ◽

pp. 222-236

Author(s):

Anuradha Chaminda Gajanayaka

Keyword(s):

Software Development ◽

Agile Software Development ◽

Development Model ◽

Software Development Model ◽

Responding To Change ◽

The One ◽

Agile Software ◽

Development Methods ◽

Software Development Methods

Agile software development has established as a reliable alternative to waterfall software development model. Unfortunately the use of agile software development has been limited to time based contracts and not for time limited contracts. The main reason for this limitation is the “Agile manifesto” itself. The forth value of the manifesto states that agile believers find more value in “Responding to change over following a plan”. This is the one of the main reasons why agile software development methods are not preferred for a fixed priced contract or time limited contract. The following case study provides an example on how the agile software development can be used for fixed priced software development contracts even when operating in offshore context. The agile software development concepts were used throughout to plan, execute, monitor, report, etc. for the project documented in this case study.

Download Full-text