A Unified Approach to Modeling and Programming

Madsen, Ole Lehrmann; Møller-Pedersen, Birger

doi:10.1007/978-3-642-16145-2_1

Cited by 15 publications

(6 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is also about investigating modelling and programming paradigms that would allow to consider concurrency and decentralization of control an essential design dimension of programs and system. Actors, concurrent objects and agents can be framed as conceptual extensions of the OO paradigm in this direction, and they could play an important role in investigating unified approaches for modelling and programming, as put forth in [11].…”

Section: Discussionmentioning

confidence: 99%

Away from the sequential paradigm tarpit

Ricci

Yonezawa

2013

Proceedings of the Second International Workshop on Combined Object-Oriented Modelling and Programming Languages

View full text Add to dashboard Cite

The fundamental turn of software towards concurrency that we are witnessing today has a strong impact on modeling and programming. How to properly integrate OO modelling/programming and concurrency is still an open problem, in spite of the many ad-hoc mechanisms, libraries and frameworks that have been introduced so far. We believe that such integration requires modelling and programming paradigms that make it possible to naturally exploit concurrency, decentralization of control and interaction as main ingredients of problem solving, as well as of program design and coding. In this paper we elaborate this point by discussing some main approaches in literature that propose such integration: in particular we review actors and concurrent objects first, then a recent proposal based on agentoriented programming.

show abstract

Section: Discussionmentioning

confidence: 99%

Away from the sequential paradigm tarpit

Ricci

Yonezawa

2013

Proceedings of the Second International Workshop on Combined Object-Oriented Modelling and Programming Languages

View full text Add to dashboard Cite

show abstract

“…If development environments for modeling languages for executable models will not be able to match development environments for programming languages, then users still have to cope with both a modeling language and a programming language, and based upon experience the code artifact will be the dominant. Really returning to the original approach would imply going for a combined modeling -and programming language, see [48] for an account of that. Class models and state machine models will obviously be part of such a combined language, with e.g.…”

Section: Conclusion: Executable Models or Unified Modeling And Programentioning

confidence: 99%

“…Based upon a former role modeling method[48]. Trygve Reenskaug was member of the UML Core Team, and part of small group that made the first proposal for UML1.1.…”

mentioning

confidence: 99%

Scandinavian Contributions to Object-Oriented Modeling Languages

Møller-Pedersen

2011

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

The history of Scandinavian contributions to modeling languages is interesting in many respects. The most interesting part of the history is that some of mechanisms were conceived very early, years before modeling became mainstream. It is well-known that object-orientation started with SIMULA in 1967, but it is less known that SIMULA formed the basis for a modeling language already in 1973, and that the Ericsson AXE software structure (1976) was one of the foundations (via SDL) for composite structures in UML2. It is also interesting that there has been a development towards making mechanisms less particular: while early modeling languages had special structuring mechanisms, UML2 now cover this by composite classes. In addition, early modeling languages were executable, in fact they were combined modelingand programming languages. After a period where modeling was just for the purpose of analysis and design, the trend is now towards executable models, i.e. almost going back to the original Scandinavian approach.

show abstract

“…to be composed of other components (internal components or sub-components.) Like in [9] or UML, we also see components as just special objects able to explicitly describe provisions, requirements and architectures. Components' contracts are defined in terms of ports, which are connection and communication units each described by a name, an interface, a role (provided or required) and a visibility (external or internal).…”

Section: Introductionmentioning

confidence: 98%

Wringing out objects for programming and modeling component-based systems

Špaček

Dony

Tibermacine

et al. 2013

Proceedings of the Second International Workshop on Combined Object-Oriented Modelling and Programming Languages

View full text Add to dashboard Cite

Languages and technologies used to implement componentbased software are not component-based, i.e. while the design phase happens in the component world, the programming phase occurs in the object-oriented world. When an object-oriented language is used for the programming stage, then the original component-based design vanish, because component concepts like requirements and architectures are not treated explicitly. This makes it difficult to keep model and its implementation causally connected. We present a new pure reflective component-based programming and modeling language where all core component concepts are treated explicitly and therefore keeping original componentdesign alive. The language makes it possible to model and program component-based software using the same language plus its uniform component-based meta-model and integrated reflection capabilities make the language and its applications open and flexible.

show abstract

A Unified Approach to Modeling and Programming

Cited by 15 publications

References 11 publications

Away from the sequential paradigm tarpit

Away from the sequential paradigm tarpit

Scandinavian Contributions to Object-Oriented Modeling Languages

Wringing out objects for programming and modeling component-based systems

Contact Info

Product

Resources

About