物件導向軟體之架構(Object-Oriented Software Construction)探討

Aspect] is a simple and practical aspect-oriented extension to Java With just a few new constructs, AspectJ provides support for modular implementation of a range of crosscutting concerns. In AspectJ's dynamic join point model, join points are well-defined points in the execution of the program; pointcuts are collections of join points; advice are special method-like constructs that can be attached to pointcuts; and aspects are modular units of crosscutting implementation, comprising pointcuts, advice, and ordinary Java member declarations. AspectJ code is compiled into standard Java bytecode. Simple extensions to existing Java development environments make it possible to browse the crosscutting structure of aspects in the same kind of way as one browses the inheritance structure of classes. Several examples show that AspectJ is powerful, and that programs written using it are easy to understand.

An overview of AspectJ

The increasing integration of the Internet of Everything into the industrial value chain has built the foundation for the next industrial revolution called Industrie 4.0. Although Industrie 4.0 is currently a top priority for many companies, research centers, and universities, a generally accepted understanding of the term does not exist. As a result, discussing the topic on an academic level is difficult, and so is implementing Industrie 4.0 scenarios. Based on a quantitative text analysis and a qualitative literature review, the paper identifies design principles of Industrie 4.0. Taking into account these principles, academics may be enabled to further investigate on the topic, while practitioners may find assistance in identifying appropriate scenarios. A case study illustrates how the identified design principles support practitioners in identifying Industrie 4.0 scenarios.

/pdf/design-principles-for-industrie-4-0-scenarios-3z7bfvbmm7.pdf

Design Principles for Industrie 4.0 Scenarios

The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

Model Driven Engineering

[서평]「Component Software」 - Beyond Object-Oriented Programming -

Component adaptation is widelyrecognised to be one of the crucial problems in Component-Based Software Engineering (CBSE). We present a formal methodologyfor adapting components with mismatching interaction behaviour. The three main ingredients of the methodologyare: (1) the inclusion of behaviour specifications in component interfaces, (2) a simple, high-level notation for expressing adaptor specifications, and (3) a fullyautomated procedure to derive concrete adaptors from given high-level specifications.

/pdf/a-formal-approach-to-component-adaptation-3hec0wyu0s.pdf

A formal approach to component adaptation

http://www.lcc.uma.es/~av/Publicaciones/04/ws-fm04.pdf

Formalizing Web Service Choreographies

There's growing interest in developing applications for the Internet of Things. Such applications' main objective is to integrate technology into people's everyday lives, to be of service to them en masse. The form in which this integration is implemented, however, still leaves much room for improvement. Usually, the user must set parameters within the application. When the person's context changes, they have to manually reconfigure the parameters. What was meant to be a commodity in an unforeseen situation then becomes extra noise. This article describes a reference architecture that improves how people are integrated with the IoT, with smartphones doing the connecting. The resulting integration opens the way to new IoT scenarios supporting evolution towards the Internet of People.

From the Internet of Things to the Internet of People

Component-Based Software Engineering focuses on the reuse of existing software components. In practice, most components cannot be integrated directly into an application-to-be, because they are incompatible. Software Adaptation aims at generating, as automatically as possible, adaptors to compensate mismatch between component interfaces, and is therefore a promising solution for the development of a real market of components promoting software reuse. In this article, we present our approach for software adaptation which relies on an abstract notation based on synchronous vectors and transition systems for governing adaptation rules. Our proposal is supported by dedicated algorithms that generate automatically adaptor protocols. These algorithms have been implemented in a tool, called Adaptor, that can be used through a user-friendly graphical interface.

/pdf/model-based-adaptation-of-behavioral-mismatching-components-4e3n9c4eu2.pdf

Model-Based Adaptation of Behavioral Mismatching Components

Several notations and languages for software architectural specification have been recently proposed. However, some important aspects of composition, extension, and reuse deserve further research. These problems are particularly relevant in the context of open systems, where system structure can evolve dynamically, either by incorporating new components, or by replacing existing components with compatible ones. Our approach tries to address some of these open problems by combining the use of formal methods, particularly process algebras, with concepts coming from the object-oriented domain. In this paper we present LEDA, an Architecture Description Language for the specification, validation, prototyping and construction of dynamic software systems. Systems specified in LEDA can be checked for compatibility, ensuring that the behaviour of their components conforms to each other and that the systems can be safely composed. A notion of polymorphism of behaviour is used to extend and refine components while maintaining their compatibility, allowing the parameterisation of architectures, and encouraging reuse of architectural designs.

/pdf/specification-and-refinement-of-dynamic-software-2jbn6zgt6a.pdf

Carlos Canal

Papers

A formal approach to component adaptation

Formalizing Web Service Choreographies

From the Internet of Things to the Internet of People

Model-Based Adaptation of Behavioral Mismatching Components

Specification and Refinement of Dynamic Software Architectures