A Model-Driven Approach for the Design and Implementation of Software Development Methods

2012 ◽  
Vol 3 (4) ◽  
pp. 86-103 ◽  
Author(s):  
Mario Cervera ◽  
Manoli Albert ◽  
Victoria Torres ◽  
Vicente Pelechano
Keyword(s):  
Software Development ◽  
Method Engineering ◽  
Model Driven ◽  
Design And Implementation ◽  
Two Phases ◽  
Definition Of ◽  
Model Driven Approach ◽  
Development Methods ◽  
Software Development Methods

The Situational Method Engineering (SME) discipline emerged two decades ago to address the challenge of the in-house definition of software development methods and the construction of the corresponding supporting tools. Unfortunately, current SME approaches still have limitations that are hindering their adoption by industry. One of these limitations is that most approaches do not properly encompass two phases of the SME lifecycle, which refer to the method design and the method implementation. To address this limitation, this paper demonstrates how Model-Driven Development (MDD) techniques can contribute to successfully cover both phases. The proposal is illustrated by a real case study that is currently being used at the Valencian Regional Ministry of Infrastructure, Territory and Environment.

Fixed Priced Projects in Agile

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.

scholarly journals Development of custom notation for XML-based language: A model-driven approach

2017 ◽  
Vol 14 (3) ◽  
pp. 939-958 ◽  
Author(s):  
Sergej Chodarev ◽  
Jaroslav Porubän
Keyword(s):  
User Experience ◽  
Explicit Representation ◽  
Abstract Syntax ◽  
Iterative Design ◽  
Model Driven ◽  
Domain Specific ◽  
Concrete Syntax ◽  
Definition Of ◽  
Model Driven Approach

In spite of its popularity, XML provides poor user experience and a lot of domain-specific languages can be improved by introducing custom, more humanfriendly notation. This paper presents an approach for design and development of the custom notation for existing XML-based language together with a translator between the new notation and XML. The approach supports iterative design of the language concrete syntax, allowing its modification based on users feedback. The translator is developed using a model-driven approach. It is based on explicit representation of language abstract syntax (metamodel) that can be augmented with mappings to both XML and the custom notation. We provide recommendations for application of the approach and demonstrate them on a case study of a language for definition of graphs.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Sign in / Sign up

Export Citation Format

Share Document