Search

Abstract Nowadays, large numbers of organizations may opt for Aspect-Oriented Programming (AOP), which is an enhancement to Object-Oriented Programming (OOP). This is due to the addition of a number of concepts that have assisted in the production of more flexible and reusable components. One of the most important elements added by AOP is software reuse, which is based on reusability attributes. These attributes indicate the possibility of reusing one or more components in the development of a new system. It is one of the most essential attributes to evaluate the quality of a system’s components. Thus far, little attention has been paid to the process of measuring AOP reusability, and it has not yet been standardized. The objective of the current study is to come up with a reasonable measurement for AOP software reuse, which is simultaneously a significant topic for researchers while offering several advantages for organizations. Although numerous models have been built to estimate the reusability of software, most of them are not dedicated to Aspect-Oriented Software (AOS). In this study, a model has been designed for AOS reusability estimation and measurement based on a new equation depending on five attributes that have a range of positive and negative impacts on AOS reusability. Three of those attributes, namely coupling, cohesion, and design size, have been included in previous studies. This study proposes complexity and generality as two new attributes to be considered. Each of these attributes was measured based on the metrics also proposed in this study. A new equation to calculate AOS reusability was constructed based on the most important reusability attributes and metrics. Seven aspect projects were employed as a case study to apply the proposed equation. After the proposed equation was applied to the selected projects, we obtained new values of reusability to compare with the values that resulted from applying the previous equation. The fact that new values emerged indicates that the proposed reusability metrics and attributes had a significant effect.

Nowadays, large numbers of organizations may opt for Aspect-Oriented Programming (AOP), which is an enhancement to Object-Oriented Programming (OOP). This is due to the addition of a number of concepts that have assisted in the production of more flexible and reusable components. One of the most important elements added by AOP is software reuse, which is based on reusability attributes. These attributes indicate the possibility of reusing one or more components in the development of a new system. It is one of the most essential attributes to evaluate the quality of a system's components. Thus far, little attention has been paid to the process of measuring AOP reusability, and it has not yet been standardized. The objective of the current study is to come up with a reasonable measurement for AOP software reuse, which is simultaneously a significant topic for researchers while offering several advantages for organizations. Although numerous models have been built to estimate the reusability of software, most of them are not dedicated to Aspect-Oriented Software (AOS). In this study, a model has been designed for AOS reusability estimation and measurement based on a new equation depending on five attributes that have a range of positive and negative impacts on AOS reusability. Three of those attributes, namely coupling, cohesion, and design size, have been included in previous studies. This study proposes complexity and generality as two new attributes to be considered. Each of these attributes was measured based on the metrics also proposed in this study. A new equation to calculate AOS reusability was constructed based on the most important reusability attributes and metrics. Seven aspect projects were employed as a case study to apply the proposed equation. After the proposed equation was applied to the selected projects, we obtained new values of reusability to compare with the values that resulted from applying the previous equation. The fact that new values emerged indicates that the proposed reusability metrics and attributes had a significant effect. [ABSTRACT FROM AUTHOR]

Separation of cross-cutting concerns is an important issue in business process management, where Aspect-Oriented Business Process Modeling (AO-BPM) aims to support this separation through a new form of encapsulation technique. Although different researchers have investigated how these models can be designed to support separation of non-retroactive cross-cutting concerns, there is no study that defines the separation of retroactive ones. The lack of a unified definition of the syntax and the operational semantics for these models hinders their enactment in practice as well. As a result, the perceived usefulness and usability of these approaches have not yet been investigated so far. Thus, this article fills this gap by formalizing an AO-BPM language and the semantics that can support enactment of such models. The semantics is validated through the state-space analysis technique, and the feasibility of the implementation is also demonstrated. The perceived usefulness and easy to use of the AO-BPM is evaluated by applying the Technology Acceptance Model during a workshop session. The result shows that participants perceived the approach usable and easy to use.

The 15th issue of CSIMQ presents articles discussing management and modeling aspects of informatics research. The provided models and their application help to understand the domains under discussion. The models range from socio-technical models over business process models to models of usable graphical interfaces. Readers might find a lot of interesting aspects in this broad spectrum of management and modeling research. The published articles support management and modeling of complex systems in different ways on different levels of abstraction. The research results reflected in the articles can help to fill knowledge gaps and facilitate decision making in project management, business process management, very complex domain analysis, and data-intensive cyber-physical systems engineering.

Runtime verification (RV) provides essential mechanisms to enhance software robustness and prevent malfunction. However, RV often entails complex and formal processes that could be avoided in scenarios in which only invariants or simple safety properties are verified, for example, when verifying input data in Graphical User Interfaces (GUIs). This paper describes S-DAVER, a lightweight framework aimed at supporting separate data verification in GUIs. All the verification processes are encapsulated in an independent layer and then transparently integrated into an application. The verification rules are specified in separate files and written in interpreted languages to be changed/reloaded at runtime without recompilation. Superimposed visual feedback is used to assist developers during the testing stage and to improve the experience of users during execution. S-DAVER provides a lightweight, easy-to-integrate and dynamic verification framework for GUI data. It is an integral part of the development, testing and execution stages. An implementation of S-DAVER was successfully integrated into existing open-source applications, with promising results. Copyright © 2015 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

In this paper the modular approach of aspect-oriented programming named join point interfaces or JPI for the Java programming language is discussed. Also, the main differences and advantages of JPI over the classical methodology of aspect-oriented programming for Java (AspectJ) are analyzed with the aim of achieving a modular aspect-oriented programming. In addition, an extension of UML class diagram for the structural and conceptual design of JPI applications is proposed. As a study case, a programming example in AspectJ and JPI, along with a UML class diagram model of the study case, using the modeling proposed in this work, is presented. It is concluded that the proposed class diagram UML JPI allows defining an ingenuous class, an essential element for achieving a complete adaptation and transformation of aspectoriented programming into JPI solutions. [ABSTRACT FROM AUTHOR]

Pointcuts position definition is not clear and weaving operation is inconvenient are two problems in existing aspect-oriented network software evolution method. To address the two issues, an aspect-oriented network software evolution method supported by Role-Goal-Process-Services (RGPS) process meta-model is proposed. In this method, process is defined by RGPS process meta-model and pointcuts position is defined by meta-model control structure. Aspect pointcuts position definition is precise and can be woven in the original process seamlessly because of the consistent definition of aspect and process. Process evolution is defined using formal method and aspect weaving ways in evolution are clearly elaborated. Finally, a case is used to illustrate the aspect weaving process in the evolution method. [ABSTRACT FROM AUTHOR]

Data security and integrity of the transactions, are important objects to the companies that have online systems working directly or indirectly with their assets. The interest in ecommerce has spread in many market types due to low operating costs and also to its global reach, causing a need for constant improvements regarding the safety of these systems. This paper demonstrates the construction of a Web system using Aspect Oriented Programming (AOP), based on a model called multilevel access methods using the AspectJ language. It was used NetBeans IDE as the development environment. It was adopted an alternative syntax, known as Annotations through interfaces, which served to connect the called method and the allowed user profile. This model was implemented in a system of the Federal Institute of Education, named as Programa Monitoria.The Aspect-Oriented Programming, used in this system, has contributed directly to the reduction of scattering and entanglement of source codes between the system modules and non-functional requirements, reducing the coupling and consequently the complexity of the source code. The Aspect-Oriented Programming also promoted the centralization of responsibility for security, which is usually assigned to all developers on the team. [ABSTRACT FROM AUTHOR]

Abstract: Aspect Oriented (Aspect-Oriented, referred to as AO) as a new programming technology is increasingly cause for concern. This article describes a number of experts to study the current object-oriented Petri Nets (OO PN) adding aspect-oriented thinking, combined with software design and development cycle, given the aspect-oriented OO PN in software engineering methods and steps. Shows the method of using AO PN government office system software design and development of application examples, and gives some object class, the log section and the application form. As the plane of isolation, reducing the coupling, the use of AO PN ways in different applications will use a combination of each section, allowing code reusability enhancement. OOPN itself can process the software system design and development of effective control to ensure that the software system reliability and standardization. [Copyright &y& Elsevier]

Software architecture has significance for controlling the complexity of software system and improving software quality. With the development of the research on software architecture, researchers have found the problem of architectural crosscutting. Utilizing aspect, AOP has resolved the crosscutting problem at code level. So, on the basis of the existing research achievements, we propose an approach to aspect-oriented software architecture design based on ACME by introducing the concept of aspect into software architecture design. ACME can validate the design process formally. In accordance with the proposed approach, we design the architecture of an online bookstore system with AcmeStudio. [ABSTRACT FROM AUTHOR]

Abstract: Model-driven code generation has been investigated in traditional and object-oriented design paradigms; significant progress has been made. It offers many advantages including the rapid development of high quality code. Errors are reduced and the consistency between the design and the code is retained, in comparison with a purely manual approach. Here, a model-driven code generation approach based on graph transformations for aspect-oriented development is proposed. The approach has two main transformation activities. The first activity transforms a visual (graphical) model of the design into a formal, text-based notation that can be readily processed. The graphical model is created by the software designer and uses a UML profile for aspect-oriented software (i.e., FDAF) to represent aspects and their components. XML is the target notation for this step; the transformation uses the XML meta-model to ensure that the output complies with the language. The second activity transforms the XML model into AspectJ source code. The transformation uses the AspectJ meta-model to ensure the output complies with the language. The transformations from the extended UML model to XML and from XML to AspectJ code are fully automated. The transformation algorithms are based on graph transformations; tool support has been developed. Key technical issues in the approach are discussed, including performance, the amount of code generated, correctness, and adaptability, in addition to a comparison of the proposal with existing alternative approaches. The approach has been validated on three example systems: a banking system, classroom scheduling system, and an insurance system. The banking system example is presented in the paper. [Copyright &y& Elsevier]

Pervasive applications must be aware of the contexts where they are executed. These contexts may vary greatly and change quickly. Two main problems are associated with this issue: (1) context-awareness is a crosscutting concern that cannot be well-encapsulated in a single module using traditional technologies, thus hindering software maintenance and reusability; and (2) reasoning about application design correctness can be complex due to the number and diversity of potential contexts where a pervasive application could be executed. In order to overcome these problems, we present a process for the design and implementation of context-aware pervasive applications that uses aspect-orientation and executable modelling in order to overcome these shortcomings. Aspect-oriented techniques contribute to the encapsulation of crosscutting concerns, such as context-awareness, into well-localized modules. Executable modelling helps engineers to reason about application design by executing the design models in different contexts and situations. Pervasive applications are modelled using the aspect-oriented executable modelling UML 2.0 profile, executed at the modelling level for testing purposes, and then mapped into an aspect-oriented middleware platform for pervasive applications. This process is illustrated using a location-aware intelligent transportation system consisting of a set of cooperating sentient vehicles. [ABSTRACT FROM AUTHOR]

This paper proposes an extended system dependence graph called AspectSDG to represent control and data dependences for AspectC++ programs, and presents an approach for the construction of AspectSDG. This approach decomposes aspect-oriented programs into three parts: component codes, aspect codes, and weaving codes. It constructs program dependence graphs (PDGs) for each part, and then connects the PDGs at call sites to form the complete AspectSDG. The AspectSDG can deal with advice precedence correctly, and represent the additional dependences caused by aspect codes. Based on this model, we introduce how to compute a static slice of an AspectC++ program. [ABSTRACT FROM AUTHOR]

In this article an analysis about traceability concerns from the aspect-oriented software development over a software system is presented. To achieve that, the general concepts about traceability and the aspect oriented approaches is treated; also the way of this technique can provide elements to verify reliability and evolution of the requirements in the software development process. To treat traceability from this way will drive to developer to identify general elements necessary to determine trace of crosscutting concern when these affect other concerns, and in turn how different pieces of a software artifact associated to this concern type have evolved and affected others along the development of life cycle. [ABSTRACT FROM AUTHOR]