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

An Introduction to MultiAgent Systems.

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 Unified Modeling Language User Guide」

Software systems dealing with distributed applications in changing environments normally require human supervision to continue operation in all conditions. These (re-)configuring, troubleshooting, and in general maintenance tasks lead to costly and time-consuming procedures during the operating phase. These problems are primarily due to the open-loop structure often followed in software development. Therefore, there is a high demand for management complexity reduction, management automation, robustness, and achieving all of the desired quality requirements within a reasonable cost and time range during operation. Self-adaptive software is a response to these demands; it is a closed-loop system with a feedback loop aiming to adjust itself to changes during its operation. These changes may stem from the software system's self (internal causes, e.g., failure) or context (external events, e.g., increasing requests from users). Such a system is required to monitor itself and its context, detect significant changes, decide how to react, and act to execute such decisions. These processes depend on adaptation properties (called self-a properties), domain characteristics (context information or models), and preferences of stakeholders. Noting these requirements, it is widely believed that new models and frameworks are needed to design self-adaptive software. This survey article presents a taxonomy, based on concerns of adaptation, that is, how, what, when and where, towards providing a unified view of this emerging area. Moreover, as adaptive systems are encountered in many disciplines, it is imperative to learn from the theories and models developed in these other areas. This survey article presents a landscape of research in self-adaptive software by highlighting relevant disciplines and some prominent research projects. This landscape helps to identify the underlying research gaps and elaborates on the corresponding challenges.

/pdf/self-adaptive-software-landscape-and-research-challenges-4rt6vhdmq2.pdf

Self-adaptive software: Landscape and research challenges

Active database management systems have been developed for applications needing an automatic reaction in response to certain events. Events can be simple in nature or complex. Complex events rely on simpler ones and are usually specified with the help of operators of an event algebra. There are quite a few papers dealing with extensions of existing event algebras. However, a systematic and comprehensive analysis of the semantics of complex events is still lacking. As a consequence most proposals suffer from different kinds of peculiarities. Independent aspects are not treated independently, leading to shady mixtures of aspects in operators. Moreover, aspects are not always treated uniformly. Operators may have other semantics than expected. The paper addresses these problems by an extensive and in-depth analysis of the foundations of complex events. As a result of this analysis, a (formal) meta-model for event algebras is introduced that subdivides the semantics of complex events into elementary, independent dimensions. Each of these dimensions are discussed in detail. The resulting language specification fulfils the criteria for a good language design (like orthogonality, symmetry, homogeneity, lean set of language constructs) to a large extent.

On the semantics of complex events in active database management systems

AspectJ is a well-established programming language for the implementation of aspect-oriented programs. It supports the aspect-oriented programming paradigm by providing a special unit, called "aspect", which encapsulates crosscutting code. While with AspectJ a suitable aspect-oriented programming language is at hand, no feasible modeling language is available that supports the design of AspectJ programs. In this work, such a design notation for AspectJ programs is presented based on the UML. It provides representations for all language constructs in AspectJ and specifies an UML implementation of AspectJ's weaving mechanism. The design notation eases the perception of aspect-orientation and AspectJ programs. It carries over the advantages of aspect-orientation to the design level.

/pdf/a-uml-based-aspect-oriented-design-notation-for-aspectj-d4482lhm8r.pdf

A UML-based aspect-oriented design notation for AspectJ

https://www.cse.msu.edu/~chengb/CSE891/Handouts/autonomic-computing-concise-intro-Sterritt.pdf

A concise introduction to autonomic computing

Keynotes.- AspectJ(tm): Aspect-Oriented Programming in Java.- Agile Processes and Modeling.- Eclipse - An Open Source Platform for the Next Generation of Development Tools.- Regular Papers.- A Framework for Resource Management in Peer-to-Peer Networks.- A Lightweight Communication Infrastructure for Spontaneously Networked Devices with Limited Resources.- Serialization of Distributed Execution-State in Java.- Specification of Business Components.- Graph Rewrite Systems for Software Design Transformations.- Lightweight Plug-In-Based Application Development.- Supporting Component-Based Software Evolution.- Java Smart Ticket Demo Application Scrutinized.- Java Class Deployment Using Class Collections.- Do We Need Components for Persistent Data Storage in the Java 2 Enterprise Environment?.- Consistency Checking of Financial Derivatives Transactions.- Toolkits for Generating Wrappers.- Developing a Generic Concept of an Electronic Negotiation Process with ebXML.- AspectS - Aspect-Oriented Programming with Squeak.- Relational Database Support for Aspect-Oriented Programming.- Object Teams: Improving Modularity for Crosscutting Collaborations.- Ubiquitous Healthcare: The OnkoNet Mobile Agents Architecture.- Extending Activity Diagrams to Model Mobile Systems.- A Concrete Method for Developing and Applying Product Line Architectures.- Generic Implementation of Product Line Components.- Qualifying Types Illustrated by Synchronisation Examples.- Advanced Thread Synchronization in Java Using Interaction Expressions.- Refactoring Browser for UML.- Test-Driven Web Application Development in Java.- UML-Based Statistical Test Case Generation.- Do We Need 'Agile' Software Development Tools?.

/pdf/objects-components-architectures-services-and-applications-56tlno6i1u.pdf

Objects, Components, Architectures, Services and Applications for a Networked World

GRIDs are both a new and an old concept. Many of the components have been the subject of R&D and some exist as commercial products. The GRIDs concept represents many different things to different people: metacomputing, distributed computing, advanced networking, distributed database, information retrieval, digital libraries, hypermedia, cooperative working, knowledge management, advanced user interfaces, mobile and pervasive computing and many others. More importantly, end-users see the GRIDs technology as a means to an end to improve quality, speed of working and cooperation in their field. GRIDs will deliver the required information in an appropriate form to the right place in a timely fashion. The novelty of GRIDs lies in the information systems engineering required in generating missing components and putting the components together. Ambient computing provides new possibilities in connectivity of a person (with or without sensors or data detectors) to a GRIDs environment allowing previously unimaginable possibilities in information delivery, data collection, command and control, cooperative working, communications, learning and entertainment.

Rainer Unland

Papers

On the semantics of complex events in active database management systems

A UML-based aspect-oriented design notation for AspectJ

A concise introduction to autonomic computing

Objects, Components, Architectures, Services and Applications for a Networked World

Web, Web-Services, and Database Systems