Adding a Textual Syntax to an Existing Graphical Modeling Language: Experience Report with GRL

Abdelzad, Vahdat; Amyot, Daniel; Lethbridge, Timothy C.

doi:10.1007/978-3-319-24912-4_12

Cited by 6 publications

(3 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It has also contributed to resolve the well-known challenge of integrating formal methods into the existing software processes (see for example Abrial [7] (p. 766) and Alagar et al [8] (Chapter 2)). The second group comprises works pertaining to improve, transform or extend the syntax of the graphical model with, for instance, text-based notations such as XML to facilitate model construction and/or transformation [9][10][11][12]. The last category includes works addressing the concept of refinement, which is very poorly integrated in semi-formal techniques [13][14][15].…”

Section: Related Workmentioning

confidence: 99%

An Improved User Requirements Notation (URN) Models’ Construction Approach

Dongmo

Poll

2023

Systems

View full text Add to dashboard Cite

Semi-formal software techniques have been very successful in industry, government institutions and other areas such as academia. Arguably, they owe a large part of their success to their graphical notation, which is more human-oriented than their counterpart text-based and formal notation techniques. However, ensuring the consistency between two or more models is one of the known challenges of these techniques. This work looks closely at the specific case of the User Requirements Notation (URN) technique. Although the abstract model of URN provides for link elements to ensure the consistency between its two main components, namely, Goal-Oriented Requirement Language (GRL) and Use Case Maps (UCM), the effective implementation of such links is yet to be fully addressed. This paper performs a detailed analysis of the existing URN models construction process and proposes an improved process with some guidelines to ensure, by construction, the correctness and consistency of the GRL and UCM models. A case study is used throughout the paper to illustrate the suggested solution.

show abstract

Section: Related Workmentioning

confidence: 99%

An Improved User Requirements Notation (URN) Models’ Construction Approach

Dongmo

Poll

2023

Systems

View full text Add to dashboard Cite

show abstract

“…Especially when using versatile modeling platforms such as Simulink or Ptolemy II, it is possible to create domain libraries that aid users by providing reusable APIs or objects. The Modelica language is well-known for its large number of object libraries, 1 that add capabilities to model specific domains such as chemical processes, hydraulic flows or power systems.…”

Section: Domain-specific Approachesmentioning

confidence: 99%

“…The advantage of these types of modeling languages is the quick model creation and manipulation, since the focus remains on the actual model, rather than positioning, shape or size of its representation. They also tend to be more powerful in terms of "intelligent editors and copy&paste support" [1]. Further, they often benefit from advanced features such as IDEs, static analysis, code suggestions, as they are more easily created for textual than graphical languages.…”

Section: Crest-conceptmentioning

confidence: 99%

Pragmatic reuse for DSML development

Klikovits

Buchs

2020

Softw Syst Model

View full text Add to dashboard Cite

By bridging the semantic gap, domain-specific language (DSLs) serve an important role in the conquest to allow domain experts to model their systems themselves. In this publication we present a case study of the development of the Continuous REactive SysTems language (CREST), a DSL for hybrid systems modeling. The language focuses on the representation of continuous resource flows such as water, electricity, light or heat. Our methodology follows a very pragmatic approach, combining the syntactic and semantic principles of well-known modeling means such as hybrid automata, data-flow languages and architecture description languages into a coherent language. The borrowed aspects have been carefully combined and formalised in a well-defined operational semantics. The DSL provides two concrete syntaxes: CREST diagrams, a graphical language that is easily understandable and serves as a model basis, and , an internal DSL implementation that supports rapid prototyping—both are geared towards usability and clarity. We present the DSL’s semantics, which thoroughly connect the various language concerns into an executable formalism that enables sound simulation and formal verification in , and discuss the lessons learned throughout the project.

show abstract

Textual User Requirements Notation

Kumar

Mussbacher

2018

System Analysis and Modeling. Languages, Methods, and Tools for Systems Engineering

View full text Add to dashboard Cite

Adding a Textual Syntax to an Existing Graphical Modeling Language: Experience Report with GRL

Cited by 6 publications

References 15 publications

An Improved User Requirements Notation (URN) Models’ Construction Approach

An Improved User Requirements Notation (URN) Models’ Construction Approach

Pragmatic reuse for DSML development

Textual User Requirements Notation

Contact Info

Product

Resources

About