On Model-Based Software Development

Heitmeyer, Constance L.; Shukla, Sandeep K.; Archer, Myla; Leonard, Elizabeth I.

doi:10.1007/978-3-642-37395-4_4

Cited by 7 publications

(5 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This unit covers issues of a building of the minimal state machine model, which is essential to prove that the model satisfies a defined some security property. 25 In addition, course unit takes up the question of the proving, that the security model satisfies the property using a mechanical verifier.…”

Section: Formal Methods For a Certifiable Secure Software Systemmentioning

confidence: 99%

Formal and Intelligent Methods for Security and Resilience: Education and Training Issues

Pomorova¹,

Lysenko²

2016

IISIJ

View full text Add to dashboard Cite

This article presents the results of the implementation of TEMPUS SEREIN project in the Khmelnitsky National University. The main challenge was to develop curriculum and course materials for masters and PhD students. The authors introduce the module description of the course "Formal and Intelligent Methods for Security and Resilience." The module deals with the issues of development and usage of formal methods for designing secure software systems and implementation of formal methods for assuring security of computer networks. We also present some issues on the usage of intelligent systems for security and address the questions of enhancing systems' resilience. The implementation of the developed training course will improve the quality of education and will make graduates more successful on the labour market.

show abstract

Section: Formal Methods For a Certifiable Secure Software Systemmentioning

confidence: 99%

Formal and Intelligent Methods for Security and Resilience: Education and Training Issues

Pomorova¹,

Lysenko²

2016

IISIJ

View full text Add to dashboard Cite

show abstract

“…A model is a simplified representation of a (software) system, that is used to study aspects of the system one is interested in [357,291,408,142,270,124] and are key to support human understanding, reasoning and communication [394]. Models allow representing and studying systems even prior to implementation [479,410] and are being used to explain and validate the intended behavior of a (software) system [410,203]. Therefore, models are an important input for the design and development of software [479,295,76].…”

Section: Way Of Supportingmentioning

confidence: 99%

“…As mentioned in Chapter 1, a model is a simplified representation of a (software) system, that is used to study aspects of the system one is interested in [357,291,408,142,270,124] and are key to support human understanding, reasoning and communication [394], allowing for validation before actual implementation [479,410,203]. It is therefore considered an important artifact in the software development process [479,60,295,76].…”

Section: Models and Its Relationship With Softwarementioning

confidence: 99%

“…MDD or, more specifically, MDSD puts models at the heart of software development with the promise to bridge the gap between requirements of an organization and the technical implementation of the software system by means of model transformation [412,315,428,352,43,56], using the models to generate code or for real-time interpretation by running software [149,203,56]. While there are differences between code generation and model interpretation in terms of easiness to understand, debugging possibilities, performance of the execution environment, and compile and deploy time, from a usage perspective these differences don't really matter; both need a mapping (or transformation definition) from higher order (business domain) model to lower order software model, and they can even be combined [68,113,56].…”

Section: Model-driven Software Developmentmentioning

confidence: 99%

“…Main advantages of an MDSD approach include a) a common and better understanding and reasoning about the required or created system [26,203,56], b) the possibility to simulate before building the system [248,203], c) an increased productivity of the development team due to (partial) automation of the development process [248,26,203,56], d) a reduction of the number of bugs or defects, as they can be discovered early in the development process when they are less costly to fix [248,203,56], and e) traceability between model and the code [5,396].…”

Section: Advantages Of Mdsdmentioning

confidence: 99%

See 2 more Smart Citations

On the design of enterprise ontology-driven software development

Krouwel

View full text Add to dashboard Cite

published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rightsCopyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.• Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal.If the publication is distributed under the terms of Article 25fa of the Dutch Copyright Act, indicated by the "Taverne" license above, please follow below link for the End User

show abstract

From enterprise models to low-code applications: mapping DEMO to Mendix; illustrated in the social housing domain

Krouwel,

Op ’t Land,

Proper

2024

Softw Syst Model

View full text Add to dashboard Cite

Due to hyper-competition, technological advancements, regulatory changes, etc, the conditions under which enterprises need to thrive become increasingly turbulent. Consequently, enterprise agility increasingly determines an enterprise’s chances for success. As software development often is a limiting factor in achieving enterprise agility, enterprise agility and software adaptability become increasingly intertwined. As a consequence, decisions that regard flexibility should not be left to software developers alone. By taking a Model-driven Software Development (MDSD) approach, starting from DEMO ontological enterprise models and explicit (enterprise) implementation design decisions, the aim of this research is to bridge the gap from enterprise agility to software adaptability, in such a way that software development is no longer a limiting factor in achieving enterprise agility. Low-code technology is a growing market trend that builds on MDSD concepts and claims to offer a high degree of software adaptability. Therefore, as a first step to show the potential benefits to use DEMO ontological enterprise models as a base for MDSD, this research shows the design of a mapping from DEMO models to Mendix for the (automated) creation of a low-code application that also intrinsically accommodates run-time implementation design decisions.

show abstract

On Model-Based Software Development

Cited by 7 publications

References 27 publications

Formal and Intelligent Methods for Security and Resilience: Education and Training Issues

Formal and Intelligent Methods for Security and Resilience: Education and Training Issues

On the design of enterprise ontology-driven software development

From enterprise models to low-code applications: mapping DEMO to Mendix; illustrated in the social housing domain

Contact Info

Product

Resources

About