Agile enterprise software development using domain-driven design and test first

Landre, Einar; Wesenberg, Harald; Olmheim, Jorn

doi:10.1145/1297846.1297967

Cited by 17 publications

(13 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The Java and the EMF implementations are exactly the same but for the implementation of the domain classes, which are declared in a different namespace. In addition, the Java domain classes are linked to a MariaDB relational database 4 via JPA and the EMF domain classes only contain the feature values, thus forming a view model, that are relevant for the tasks to be computed. The correctness of the Java/EMF queries is cross-checked with the results obtained with the corresponding SQL queries for each database every time a query is executed.…”

Section: Empirical Evaluationmentioning

confidence: 99%

“…The times reported are average times (in ms) extracted from 1000 iterations for experiments for size factors up to 2 −1 , and from 100 iterations for the rest of cases, but for size factor 2 4 , where 10 iterations were run. The first 10% of results have been considered as warm up exercise for the JVM and have been excluded from the analysis.…”

Section: A Experiments Setupmentioning

confidence: 99%

“…Uludag et al showed how DDD facilitates the integration of design practices, including the definition of a domain model, in agile software development for large systems [3]. However, it is difficult to systematize the design of the domain model according to DDD [4].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Code-First Model-Driven Engineering: On the Agile Adoption of MDE Tooling

Boronat

2019

2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

Domain models are the most important asset in widely accepted software development approaches, like Domain-Driven Design (DDD), yet those models are still implicitly represented in programs. Model-Driven Engineering (MDE) regards those models as representable entities that are amenable to automated analysis and processing, facilitating quality assurance while increasing productivity in software development processes. Although this connection is not new, very few approaches facilitate adoption of MDE tooling without compromising existing value, their data. Moreover, switching to MDE tooling usually involves re-engineering core parts of an application, hindering backward compatibility and, thereby, continuous integration, while requiring an up-front investment in training in specialized modeling frameworks. In those approaches that overcome the previous problem, there is no clear indication − from a quantitative point of view − of the extent to which adopting state-of-the-art MDE practices and tooling is feasible or advantageous.In this work, we advocate a code-first approach to modeling through an approach for applying MDE techniques and tools to existing object-oriented software applications that fully preserves the semantics of the original application, which need not be modified. Our approach consists both of a semiautomated method for specifying explicit view models out of existing object-oriented applications and of a conservative extension mechanism that enables the use of such view models at run time, where view model queries are resolved on demand and view model updates are propagated incrementally to the original application. This mechanism enables an iterative, flexible application of MDE tooling to software applications, where metamodels and models do not exist explicitly. An evaluation of this extension mechanism, implemented for Java applications and for view models atop the Eclipse Modeling Framework (EMF), has been conducted with an industrytargeted benchmark for decision support systems, analyzing performance and scalability of the synchronization mechanism. Backward propagation of large updates over very large views is instant.

show abstract

Section: Empirical Evaluationmentioning

confidence: 99%

Section: A Experiments Setupmentioning

confidence: 99%

See 1 more Smart Citation

Code-First Model-Driven Engineering: On the Agile Adoption of MDE Tooling

Boronat

2019

2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

show abstract

“…In the analysis phase, models are usually general and with no information that can lead to a technical solution. In a Scrum-based SDP, Landre et al (2007) recommend to execute cycles of feedback in which clients test a functionality under development in process iterations of short duration, named Sprints. These enriched models can be used to enable automatic generation of source code.…”

Section: Introductionmentioning

confidence: 99%

Combining MDE and Scrum on the rapid prototyping of web information systems

Basso

Pillat

Roos‐Frantz

et al. 2015

IJWET

View full text Add to dashboard Cite

Rapid application prototyping (RAP) is recommended to obtain quick feedback from clients, allowing the validation of software requirements before acceptance tests. In this regard, model-driven engineering (MDE) and agile methods are two important approaches that suggest the use of techniques for RAP. Some fundamental differences between them exist: MDE focuses on software reuse through annotated system models while agile methods recommend the use simpler models to achieve quick feedback from clients. In order to comply with agility principles but still concerned about the future reuse of the developed software, the quick design of annotated models must be considered. This paper presents a MDE-based RAP methodology and tool support to quickly generate web front ends and models based on the MVC architectural pattern. In addition, we report a case study that has joined MDE and Scrum by applying our methodology and tool support for complete development of web information system in a Scrum-based industrial software project. We also present lessons learnt from the case study and point out some issues for future research in software engineering to facilitate the introduction of MDE in target contexts.

show abstract

“…Outro exemplo de aplicação de DDD é reportado por Landre et al (2007), em um projeto de desenvolvimento de aplicações de comércio e fornecimento de petróleo e produtos refinados. O objetivo era substituir os sistemas legados da empresa por novas aplicações, as quais deveriam ser capazes de lidar com computações complexas sobre grandes volumes de dados.…”

Section: Trabalhos Relacionadosunclassified

Diretrizes para desenvolvimento de linhas de produtos de software com base em Domain-Driven Design e métodos ágeis

Macedo¹

View full text Add to dashboard Cite

Agradeço à professora Rosana Teresinha Vaccare Braga, por todas as dicas, conselhos e ensinamentos, e por ter aceitado tão prontamente me orientar nesta investigação. Agradeço a toda minha família, especialmente ao meu pai, que, pelo exemplo e pela disciplina, despertou em mim o gosto pela Ciência. Obrigado igualmente pela educação baseada em princípios morais sólidos, sem os quais, certamente, não teria sido possível chegar até aqui. Agradeço ao Joe Martins, pela oportunidade que me ofereceu de aprender sobre desenvolvimento de software, nos tempos da IT GIS. Obrigado, também, pela força nos primeiros meses do Mestrado. Agradeço à Paula, que esteve sempre ao meu lado, especialmente nos momentos mais críticos desta penosa empreitada. Seu incentivo tem me ajudado muito! Agradeço aos amigos que estiveram por perto durante esse tempo: Lionis, Julio, Antonielly, Tott, Cristina (Kika), Carlos, Wanderley, Krishna, Padma e Matheus. Esses agradecimentos também se estendem aos amigos de longe, pois a amizade não se rompe facilmente com a distância. São eles: Elcimar, Tiago, Marisa e Glauber. Por fim, meus agradecimentos institucionais ao ICMC e ao CNPq. v Resumo L inhas de produtos de software (LPS) são coleções de sistemas que compartilham características comuns, desenvolvidas de forma sistemática a partir de um conjunto comum de ativos centrais. Dentre as técnicas propostas por vários autores para o desenvolvimento de LPS, dois padrões podem ser observados: o processo de desenvolvimento geralmente é sequencial e o foco do projeto (design) costuma estar em interesses técnicos, como alocação de componentes e separação em subsistemas, e não em um modelo de domínio. Embora essas práticas sejam reportadas como bemsucedidas, um outro paradigma de desenvolvimento, baseado em métodos ágeis e em um conjunto de princípios de projeto conhecido como domaindriven design, é apresentado neste trabalho e pode produzir resultados mais satisfatórios, comparados aos métodos tradicionais. Essa hipótese é sustentada por comparações entre padrões de modelagem e por um estudo de caso feito neste trabalho.

show abstract

Agile enterprise software development using domain-driven design and test first

Cited by 17 publications

References 3 publications

Code-First Model-Driven Engineering: On the Agile Adoption of MDE Tooling

Code-First Model-Driven Engineering: On the Agile Adoption of MDE Tooling

Combining MDE and Scrum on the rapid prototyping of web information systems

Diretrizes para desenvolvimento de linhas de produtos de software com base em Domain-Driven Design e métodos ágeis

Contact Info

Product

Resources

About