• Aucun résultat trouvé

Executable Modeling: Retrospective and Prospective

N/A
N/A
Protected

Academic year: 2022

Partager "Executable Modeling: Retrospective and Prospective"

Copied!
1
0
0

Texte intégral

(1)

Executable Modeling: Retrospective and Prospective

(Keynote) Stephen Mellor

Email: StephenMellor@StephenMellor.com

Index Terms—Executable Models; Action Languages; UML I. ABSTRACT

In the mid-Eighties, there were thirty object-oriented nota- tions and thirty object-oriented methods. These fell into three main groups: sketches of software structure, depictions of soft- ware (usually with gaps to fill in the code) and what we now call executable models. By the late-Nineties, there was one notation and zero methods. Executable models were hard to find. The method wars were over. We (all) lost. Worse, models as graphical descriptions of code are “just documentation”, overhead that gets in the way of the real thing: code. The Agile Manifesto of 2001 elevates “working software” over models.

But “software” can also mean executable models.

The difference between a programming language and an action language is, as always, the level of abstraction. Pro- gramming languages are “aware” of data structures and threads of control. Action languages can abstract these away. Over more than a decade an action language has been added to UML and open-source implementations made available. Defined semantics are now on the horizon for state models. Perhaps UML can be made executable after all.

That will help, but it’s not enough. We need our executable models to be composable so that when two components have been tested and the manner of their interactions tested too, we

can have confidence that the combined component works. We need this now we are connecting industrial control systems to the Internet. Composable execution units are needed to bring executable modeling to growing industrial applications.

II. BIOGRAPHY

Stephen Mellor is the Chief Tech- nical Officer for the Industrial In- ternet Consortium, where he directs the standards requirements and tech- nology and security priorities for the Industrial Internet. In that role, he coordinates the activities of the several engineering, architecture, se- curity and testbed working groups and teams.

He is a well-known technology consultant on methods for the con- struction of real-time and embedded systems, a signatory to the Agile Manifesto, and adjunct professor at the Australian National University in Canberra, ACT, Australia. Stephen is the author of Structured Development for Real-Time Systems, Object Lifecycles, Executable UML, and MDA Distilled.

1

Références

Documents relatifs

Unit´e de recherche INRIA Rocquencourt, Domaine de Voluceau, Rocquencourt, BP 105, 78153 LE CHESNAY Cedex Unit´e de recherche INRIA Sophia-Antipolis, 2004 route des Lucioles, BP

Dans cette partie de notre travail nous avons traité des thèmes de la prise de décision, de la perception, de l'anticipation, en particulier dans le contexte de

Like diagnostic security information and knowledge, prescriptive aspects should be assignable to each security topic as easily and intuitively as possible, and

Security Best Practices and Risk Assessment of SCADA and Industrial Control Systems. The

Editorial for Special Issue “Rare Earth Deposits and Challenges of World REE Demand for High-Tech and Green-Tech at the Beginning of the 3rd

What is happening here, with these moves around extra-territorial access to data or the censorship of terrorist propaganda, is a major reconfiguration of secu- rity assemblages

The orders coming from different systems will be gathered to one integrated view allowing the contractor to apply logistics optimization tool and decrease

A short time after the declaration of the Second Spanish Republic (1931-39), Gordón, a veterinarian and one of the most influential politicians of the time, introduced the