Exploring Multi-Paradigm Modeling Techniques

Hardebolle, Cécile; Boulanger, Frédéric

doi:10.1177/0037549709105240

Cited by 51 publications

(19 citation statements)

References 57 publications

(68 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This can be accomplished through approaches like model merging, profiling or extension mechanisms provided by UML [6], model weaving with KerMeta [7], or other model composition approaches. However, it becomes difficult, when models are conforming to different paradigms [8]. Model federation approach is developed as a possible response to a request for proposal (RFP) by OMG [9].…”

Section: Model Federationmentioning

confidence: 99%

“…Other techniques like KerMeta using aspect weaving for multi-paradigm modeling [7] pose the same problems of conformity to MOF. Most of the existing techniques that allow the development of new views from existing models in the context of multiple paradigms are either bound to MOF or are not modular enough to be used in requirements engineering where new information resources can be linked to the requirements model even late in system development [8]. Model federation is a modular approach that is not confined to MOF for linking different kinds of information resources to the requirements models.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Continuous Requirements Engineering Using Model Federation

Golra

Beugnard

Dagnat

et al. 2016

2016 IEEE 24th International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

Abstract-Researchers in software engineering have been striving to produce new methods to improve the quality of development methodologies to consequently produce quality products. Proposition of iterative and evolutionary approaches was triggered by the realization that requirements engineering is not confined to the initial phases of software development only. With this shift of perspective, requirements engineering has become more or less a continuous process in software development lifecycles. We believe that existing requirements engineering approaches and associated tooling leave a room for improvement in putting 'continuity' into practice. A continuous requirements engineering methodology needs to take into account different concerns of all the stakeholders involved in the process. Approaches like KAOS bring the multi-view nature of requirements modeling in focus by using different views for goal, responsibility, object and operation modeling. We argue that a multi-view approach, maintaining a dynamic link between the requirement models and multiple sources of requirements, can offer a better support for continuous requirements engineering methodology. In this paper, we expand on this argument and present the early findings with the associated in progress tooling support.

show abstract

Section: Model Federationmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Continuous Requirements Engineering Using Model Federation

Golra

Beugnard

Dagnat

et al. 2016

2016 IEEE 24th International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

show abstract

“…Then, it was elaborated in context of several reuse approaches to software development including design patterns, components, software architectures and frameworks [15]. Another use of this term can be found in multi-paradigm modeling approach [16], [17] which aims at dealing with heterogeneous solutions. The need for effective solutions has made a difference in viewing paradigm.…”

Section: A Fundamentals Of Paradigmsmentioning

confidence: 99%

Information Logistics as a Paradigm

Bobkowska

2015

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-This paper presents a paradigm-based approach to information logistics. The approach deals with extracting concepts specific to information logistics in categories typical to paradigms. The resulting description should be easily connected to complementary components which are based on other paradigms, e.g. business process management and information systems development. Empirical part aims at checking and enhancing features typical to information logistics. It is conducted with action research of applying information logistics paradigm in coordination of Erasmus+ program.

show abstract

“…Among the challenges are co-execution, integration of languages and transformation from multiple sources to a shared platform [52].…”

Section: Domain-specific Modellingmentioning

confidence: 99%

Executable and Translatable UML -- How Difficult Can it Be?

Burden

Heldal

Siljamaki

2011

2011 18th Asia-Pacific Software Engineering Conference

View full text Add to dashboard Cite

Model-Driven Engineering is a paradigm for software engineering where software models are the primary artefacts throughout the software life-cycle. The aim is to define suitable representations and processes that enable precise and efficient specification, development and analysis of software.Our contributions to Model-Driven Engineering are structured according to Boyer's four functions of academic activity -the scholarships of teaching, discovery, application and integration. The scholarships share a systematic approach towards seeking new insights and promoting progressive change. Even if the scholarships have their differences they are compatible so that theory, practice and teaching can strengthen each other.Scholarship of Teaching While teaching Model-Driven Engineering to undergraduate students we introduced two changes to our course. The first change was to introduce a new modelling tool that enabled the execution of software models while the second change was to adapt pair lecturing to encourage the students to actively participate in developing models during lectures.Scholarship of Discovery By using an existing technology for transforming models into source code we translated class diagrams and high-level action languages into natural language texts. The benefit of our approach is that the translations are applicable to a family of models while the texts are reusable across different low-level representations of the same model. Scholarship of ApplicationRaising the level of abstraction through models might seem a technical issue but our collaboration with industry details how the success of adopting Model-Driven Engineering depends on organisational and social factors as well as technical.Scholarship of Integration Building on our insights from the scholarships above and a study at three large companies we show how Model-Driven Engineering empowers new user groups to become software developers but also how engineers can feel isolated due to poor tool support. Our contributions also detail how modelling enables a more agile development process as well as how the validation of models can be facilitated through text generation.The four scholarships allow for different possibilities for insights and explore ModelDriven Engineering from diverse perspectives. As a consequence, we investigate the social, organisational and technological factors of Model-Driven Engineering but also examine the possibilities and challenges of Model-Driven Engineering across disciplines and scholarships.

show abstract

Exploring Multi-Paradigm Modeling Techniques

Cited by 51 publications

References 57 publications

Continuous Requirements Engineering Using Model Federation

Continuous Requirements Engineering Using Model Federation

Information Logistics as a Paradigm

Executable and Translatable UML -- How Difficult Can it Be?

Contact Info

Product

Resources

About