A Comparison of Six UML-Based Languages for Software Process Modeling

Bendraou, Reda; Jézéquel, Jean-Marc; Gervais, Marie-Pierre; Blanc, Xavier

doi:10.1109/tse.2009.85

Cited by 68 publications

(43 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Therefore, in order to demonstrate the expressiveness power of SP2MN, this process example will also be used as a standard for comparing our results with other similar SPMLs that are applied on the same example. The chosen SPMLs are; Grundy & Hosking approach [12] and UML4SPM [19,45]. The approaches have been chosen due to their similarity to our proposed approach in terms of, the covered concepts in their languages and the representation formalism of their languages.…”

Section: Formalizing the Ispw-6 Software Process Example Problem Umentioning

confidence: 99%

Formalizing the Software Engineering Process Using a Graphical Software Process Modelling Formalism

Khdair¹,

Awad²,

Othman³

2017

IJITCS

View full text Add to dashboard Cite

Abstract-Software process modelling has recently become an area of interest within both academia and industry. It aims at defining and formalizing the software process in the form of formal rigorous models. A software process modelling formalism presents the language or notation in which the software process is defined and formalized. Several software process modelling formalisms have been introduced lately, however, they have failed to gain the attention of the industry. One major objective of formalizing the software process that has ever been an issue of research, is to enhance the understanding and communication among software process users. To achieve this aim, a modelling formalism has to offer a common language to be wellunderstood by all software process users. BPMN presents a graphical-based widely accepted standard formalism, mainly aimed at business process modelling. This paper illustrates a software process modelling formalism based upon BPMN specifications for representing the software process, named as, SP2MN. The paper also demonstrates the applicability and evaluation of the proposed formalism by; utilizing the standard ISPW-6 benchmark problem, in addition to comparing the expressiveness of SP2MN with similar software process modelling formalisms. The evaluations prove that SP2MN contributes in enhancing software process formalization. SP2MN, accordingly, can be used as a standard software process modelling formalism.

show abstract

Section: Formalizing the Ispw-6 Software Process Example Problem Umentioning

confidence: 99%

Formalizing the Software Engineering Process Using a Graphical Software Process Modelling Formalism

Khdair¹,

Awad²,

Othman³

2017

IJITCS

View full text Add to dashboard Cite

show abstract

“…BENDRAOU et al [5] conducted research on the comparison of six languages based on UML for software process modelling. The authors begin by defining a set of criteria to be met by a software modelling process.…”

Section: Related Workmentioning

confidence: 99%

“…Indeed, the scores based on authors' experience can quickly vary from one experiment to another. Furthermore, dependability that is an important property in the majority of real time and embedded systems, is not taken into account in almost all of these works ( [2] [4] [5]). …”

Section: Related Workmentioning

confidence: 99%

A Decision Support Framework for the Choice of Languages and Methods for the Design of Real Time Embedded Systems

Monthe¹,

Nana²,

Kouamou³

et al. 2016

JSEA

View full text Add to dashboard Cite

The choice of methods or design languages is a crucial phase in the development of systems and software, also for real time and embedded systems. An open question that remains in the design of these types of systems is to build a method, or to choose one among those existing, capable to cover the life cycle of a project, and particularly the development phases. This article contributes to answer the question, by proposing an approach based on a multi-criteria comparative study, of few languages and methods dedicated to the design of real time and embedded systems. The underlying objective of this work is to present to designers a wide range of approaches, and elements that can guide their choices. In order to reach this goal, we propose different comparison criteria. Each criterion is divided into sub-criteria, so that the designers can refine their choices according to the qualities they prefer and wish to have in the method or language. We also define a rating scale which is used to assess the retained languages and methods. The scores obtained from this assessment are presented in tables, one table per criterion, followed by a summary table giving the overall scores. Graphics built from these tables are provided and intend to facilitate the judgement and thus the choice of the designers.

show abstract

“…UML Activity Diagrams (AD) are well-known for describing dynamic behavior and have been extensively used as a process modeling language (PML) [3,4,5]. UML is a standard with a good tooling support and AD allow the expression of most of the workflow patterns as identified by [6].…”

Section: Introductionmentioning

confidence: 99%

Formalization of fUML: An Application to Process Verification

Laurent

Bendraou

Baarir

et al. 2014

Advanced Information Systems Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. Much research work has been done on formalizing UML Activity Diagrams for process modeling to verify different kinds of soundness properties (deadlock, unreachable activities and so on) on process models. However, these works focus mainly on the control-flow aspects of the process and have done some assumptions on the precise execution semantics defined in natural language in the UML specification. In this paper, we define a first-order logic formalization of fUML (Foundational Subset of Executable UML), the official and precise operational semantics of UML, in order to apply model checking techniques and therefore verify the correctness of fUML-based process models. Our formalization covers the control-flow, data-flow, resources, and timing dimensions of processes in a unified way. A working implementation based on the Alloy language has been developed. The implementation showed us that many kinds of behavioral properties not commonly supported by other approaches and implying multiple dimensions of the process can be efficiently checked.

show abstract

A Comparison of Six UML-Based Languages for Software Process Modeling

Cited by 68 publications

References 35 publications

Formalizing the Software Engineering Process Using a Graphical Software Process Modelling Formalism

Formalizing the Software Engineering Process Using a Graphical Software Process Modelling Formalism

A Decision Support Framework for the Choice of Languages and Methods for the Design of Real Time Embedded Systems

Formalization of fUML: An Application to Process Verification

Contact Info

Product

Resources

About