Data Mining - Concepts and Techniques.

物件導向軟體之架構(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 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

Variability modeling is essential for defining and managing the commonalities and variabilities in software product lines. Numerous variability modeling approaches exist today to support domain and application engineering activities. Most are based on feature modeling (FM) or decision modeling (DM), but so far no systematic comparison exists between these two classes of approaches. Over the last two decades many new features have been added to both FM and DM and it is tough to decide which approach to use for what purpose. This paper clarifies the relation between FM and DM. We aim to systematize the research field of variability modeling and to explore potential synergies. We compare multiple aspects of FM and DM ranging from historical origins and rationale, through syntactic and semantic richness, to tool support, identifying commonalities and differences. We hope that this effort will improve the understanding of the range of approaches to variability modeling by discussing the possible variations. This will provide insights to users considering adopting variability modeling in practice and to designers of new languages, such as the new OMG Common Variability Language.

/pdf/cool-features-and-tough-decisions-a-comparison-of-51gn5ncq6c.pdf

Cool features and tough decisions: a comparison of variability modeling approaches

This paper presents our PABRE method for facilitating Requirements Elicitation on the basis of Requirement Patterns with the goal of saving time and reducing errors during this activity. The process presented applies for elicitation in Off-The-Shelf selection projects driven by call-for-tender processes and uses a Requirement Patterns Catalogue. The process selects patterns from the catalogue that apply to the particular selection project, and convert them into the real requirements that finally configure the project Requirements Document. We show some benefits of the pattern approach for requirements engineers and IT consultants, as well as for customers. Finally we discuss
the strengths and weaknesses of the proposal and identify some future work.

/pdf/a-pattern-based-method-for-building-requirements-documents-2qmnsekrdo.pdf

A pattern-based method for building requirements documents in call-for-tender processes.

Adaptability is a key feature of Service-Oriented-Architecture (SOA) Systems. These systems must evolve themselves in order to ensure their initial requirement as well as to satisfy arising new ones. In SOA Systems there are a lot of dependencies between services, but each service is an independent element of the system. In this situation it is necessary not only ensuring that the system fulfils its requirements but also that every system satisfies its own requirements, and dynamically adapting the system when some of them cannot be ensured. In this paper we propose a SOA system, named Service Level Agreement Monitor (SALMon), for monitoring and adapting SOA Systems at run time. SALMon is based on monitoring the services for detecting Service Level Agreement (SLA) violations. The SALMon architecture is composed of three types of components: Monitors, which are composed of measure instruments themselves; the Analyzer, which checks the SLA rules; and the Decision Maker that performs corrective actions to satisfy SLA rules again. These three types of components are mostly technology-independent and the act as service inside of a SOA system making our architecture very scalable and comfortable for its purpose.

/pdf/monitoring-adaptable-soa-systems-using-salmon-1p1p8gg6h2.pdf

Monitoring Adaptable SOA Systems using SALMon

Agent-oriented models are frequently used in disciplines such as agent-oriented requirements engineering, requirements
engineering and organizational process modelling. i* is currently one of the most widespread notations used for this purpose. Due to both its dissemination and its highly strategic nature, instead of a single definition, several groups have formulated different variants, which define in a slightly different way the basic concepts of the language, as well as propose particular constructs that fit into the particular interests of these groups. In this chapter we first review these proposals and then we present a reference model that establishes the concepts and relationships that are
fundamental in i*. The reference model is expressed as a UML class diagram (with
OCL constraints) together with a vocabulary of the presented terms. Most of the included concepts are common to the seminal i* proposal, the GRL and the diverse variations used in the context of the Tropos methodology. For those concepts that are not shared by these analysed variants, the reference model tries to reconcile the different views whenever possible. The reference model allows determining the differences of any existing i* variant with respect to the model, and also to know how
much different a new variant would be from the core of i*. The variants can be expressed by applying some refactoring operations on the UML class diagram. We
illustrate this situation by applying refactoring to some of the analysed proposals.

A reference model for i

In most cases information system development can be seen as an exercise of business process reengineering, either because it automates some human-based processes or because a legacy system is going to be replaced. From this point of view, we can say that the specification of the system-to-be goes from the observation and analysis of the current system to the specification of the system-to-be, going through the construction and evaluation of alternatives. Goal-oriented models are a valuable formalism to support the strategic analysis of the current process. In this paper, we propose a method supporting that round-trip engineering process, focusing in the prescriptive construction of strategic i* models and the systematic generation of alternatives. Several requirements engineering techniques are used in order to model the existing process, which allow a reliable generation and evaluation of alternatives as well as the reuse of strategic knowledge for information system development.

A goal-based round-trip method for system development

Goal-oriented models have become a consolidated type of artefact in various software and knowledge engineering activities. Several languages exist for representing such type of models but there is a lack of associated methodologies for
guiding their construction up to the necessary level of detail. In this paper we present RiSD, a methodology for building
Strategic Dependency (SD) models in the i* notation. RiSD is defined in a prescriptive way to reduce uncertainness when constructing the model. RiSD also tackles two fundamental issues: on the one hand, it tends to reduce the average size of the resulting models and, on the other hand, it allows including some traceability relationships in the resulting models. As a
result, we may say that RiSD increases the understandability of goal-oriented models whilst improving all construction.

/pdf/risd-a-methodology-for-building-i-strategic-dependency-53ud5ai3hc.pdf

Javier Franch Gutiérrez

Papers

A pattern-based method for building requirements documents in call-for-tender processes.

Monitoring Adaptable SOA Systems using SALMon

A reference model for i

A goal-based round-trip method for system development

RiSD: a methodology for building i* strategic dependency models