Evaluating the Benefits of Model-Driven Development

Domingo, África; Echeverría, Jorge; Pastor, Oscar; Cetina, Carlos

doi:10.1007/978-3-030-49435-3_22

Cited by 13 publications

(7 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A comparison study between MDSE and CcD has been done for over a decade. From the review paper by Domingo et al, many researchers have been evaluating the benefit of the MDSE [17]. Some works said that MDSE decreases development time (up to 89%) relative to Codecentric Development (CcD).…”

Section: Literature Studymentioning

confidence: 99%

The Impact of Design-level Class Decomposition on the Software Maintainability

Priyambadha¹,

Katayama²

2023

IJACSA

View full text Add to dashboard Cite

The quality of the software's internal structure tends to decay due to the adaptation to environmental changes. Therefore, it is beneficial to maintain the internal structure of the software to benefit future phases of the software life cycle. A common correlation exists between decaying internal structures and problems like software smell and maintenance costs. Refactoring is a process to maintain the internal structure of software artifacts based on the smell. Decomposition of classes is one of the most common refactoring actions based on Blob smell performed at the source code level. Moving the class decomposition process to the design artifact seems to affect the quality and maintainability of the source code positively. Therefore, studying the impact of design-level class decomposition on source code quality and software maintainability is essential to ascertain the benefits of implementing design-level class decomposition. The metricsbased evaluation shows that the design-level class decomposition positively impacts the source code quality and maintainability with the rank biserial value is 0.69.

show abstract

Section: Literature Studymentioning

confidence: 99%

The Impact of Design-level Class Decomposition on the Software Maintainability

Priyambadha¹,

Katayama²

2023

IJACSA

View full text Add to dashboard Cite

show abstract

“…Developing innovative financial technology solutions requires a thorough understanding of user needs, regulatory frameworks, and market trends. However, the complexity arises from various factors, including evolving customer expectations, changing regulatory requirements, and emerging technologies [20][21][22][23].…”

Section: Fintech and Financial Regulatory Requirements Complexitymentioning

confidence: 99%

Unified Modeling Language for Requirements Engineering, Strategies and Best Practices for FinTech and Beyond

Challapalli

2023

AJRCoS

View full text Add to dashboard Cite

Effective requirements management is crucial in the rapidly evolving landscape of Financial Technology (FinTech) to deliver innovative and customer-centric solutions. Unified Modeling Language (UML) has emerged as a powerful tool in the FinTech industry for requirements management, providing a standardized notation and comprehensive set of diagrams. By leveraging UML, FinTech companies can overcome challenges such as miscommunication and inconsistency. UML fosters a common understanding among stakeholders, aligning perspectives and enabling informed decisions. This article explores strategies and best practices in leveraging UML for FinTech requirements management, addressing complexities, utilizing key UML diagram types, and overcoming challenges. Clear communication, collaboration, documentation standards, traceability, tool support, requirement validation, iterative approach, and model-driven development are highlighted as key practices. By adopting these strategies, organizations can streamline requirements engineering, ensure compliance, and deliver high-quality FinTech solutions. These strategies are not limited to the FinTech industry but can be applied in any industry and domain within the realm of software engineering and requirements management.

show abstract

“…Empirical evidence on model-driven development benefits. A recent paper by Domingo et al [11] surveys work on empirically measuring the benefits of model-driven development against codecentric approaches and propose a new experiment where a domainspecific language for video game development is compared to a code-centric approach. This work shows that in a model-driven approach, aside from advantages in efficiency previously reported in the literature, there are also advantages in terms of correctness with respect to a specification.…”

Section: General Remarksmentioning

confidence: 99%

Is Modeling Access Control Worth It?

Basin,

Guarnizo,

Krstic

et al. 2023

Proceedings of the 2023 ACM SIGSAC Conference on Computer and Communications Security

View full text Add to dashboard Cite

Implementing access control policies is an error-prone task that can have severe consequences for the security of software applications. Model-driven approaches have been proposed in the literature and associated tools have been developed with the goal of reducing the complexity of this task and helping developers to produce secure software efficiently. Nevertheless, there is a lack of empirical data supporting the advantages of model-driven security approaches over code-centric approaches, which are the de-facto industry standard for software development.In this work, we compare the result of implementing the same functional and security requirements by multiple developer groups in the context of a security engineering graduate course. We thereby obtain evidence on the security and efficiency of a tool-based modeldriven approach to security from the literature compared to a direct implementation in a well-known, modern web-development framework. For example, the projects using model-driven development pass up to 50% more security tests on average with less development effort. Also, we observe that models are twice as concise as manual implementations, which improves system maintainability. CCS CONCEPTS• Software and its engineering → System modeling languages; • Security and privacy → Software security engineering; Access control.

show abstract

Evaluating the Benefits of Model-Driven Development

Cited by 13 publications

References 18 publications

The Impact of Design-level Class Decomposition on the Software Maintainability

The Impact of Design-level Class Decomposition on the Software Maintainability

Unified Modeling Language for Requirements Engineering, Strategies and Best Practices for FinTech and Beyond

Is Modeling Access Control Worth It?

Contact Info

Product

Resources

About