Privacy-Preserving Reengineering of Model-View-Controller Application Architectures Using Linked Data

When a legacy system’s software architecture cannot be redesigned, implementing additional privacy requirements is often complex, unreliable and costly to maintain. This paper presents a privacy-by-design approach to reengineer web applications as linked data-enabled and implement access control and privacy preservation properties. The method is based on the knowledge of the application architecture, which for the Web of data is commonly designed on the basis of a model-view-controller pattern. Whereas wrapping techniques commonly used to link data of web applications duplicate the security source code, the new approach allows for the controlled disclosure of an application’s data, while preserving non-functional properties such as privacy preservation. The solution has been implemented and compared with existing linked data frameworks in terms of reliability, maintainability and complexity

RETHINKING THE BUSINESS PROCESS THROUGH REENGINEERING

Rethinking business through reengineering is based on the assumption that to meet contemporary demands of quality, service, flexibility, and low cost, processes must be kept simple. Examples of simplifying processes are combining several jobs into one, letting workers make decisions, performing the steps in a process in a natural order, and performing work where it makes the most sense. The net result is that work may be shifted across functional boundaries several times to expedite its accomplishment. Traditional inspection and control procedures are often eliminated or deferred until the process is complete, providing further cost savings. The authors, focusing their research on enterprises from Oltenia Region, demonstrate how reengineering can be carried out in a variety of corporate settings. But although workers are the ones who need to be empowered to carry out reengineering, the authors are adamant that the process must start at the top. This is because it involves making major changes that are likely to cut across traditional organizational boundaries. Those empowered to make the changes at lower levels must know they have the support of top management, or change won�t occur.reengineering, rethinking business processes, regional economy, leadership, organization

Beyond enterprise resource planning projects: innovative strategies for competitive advantage

ABSTRACT A rapidly changing business environment and legacy IT problems has resulted in many organisations implementing standard package solutions. This 'common systems' approach establishes a common IT and business process infrastructure within organisations and its increasing dominance raises several important strategic issues. These are to what extent do common systems impose common business processes and management systems on competing firms, and what is the source of competitive advantage if the majority of firms employ almost identical information systems and business processes? A theoretical framework based on research into legacy systems and earlier IT strategy literature is used to analyse three case studies in the manufacturing, chemical and IT industries. It is shown that the organisations are treating common systems as the core of their organisations' abilities to manage business transactions. To achieve competitive advantage they are clothing these common systems with information systems designed to capture information about competitors, customers and suppliers, and to provide a basis for sharing knowledge within the organisation and ultimately with economic partners. The importance of these approaches to other organisations and industries is analysed and an attempt is made at outlining the strategic options open to firms beyond the implementation of common business systems

The impact of enterprise application integration on information system lifecycles

Information systems (IS) have become the organisational fabric for intra-and inter-organisational collaboration in business. As a result, there is mounting pressure from customers and suppliers for a direct move away from disparate systems operating in parallel towards a more common shared architecture. In part, this has been achieved through the emergence of new technology that is being packaged into a portfolio of technologies known as enterprise application integration (EAI). Its emergence however, is presenting investment decision-makers charged with the evaluation of IS with an interesting challenge. The integration of IS in-line with the needs of the business is extending their identity and lifecycle, making it difficult to evaluate the full impact of the system as it has no definitive start and/or end. Indeed, the argument presented in this paper is that traditional life cycle models are changing as a result of technologies that support their integration with other systems. In this paper, the need for a better understanding of EAI and its impact on IS lifecycles are discussed and a classification framework proposed.Engineering and Physical Sciences Research Council (EPSRC) Grant Ref: (GR/R08025) and Australian Research Council (DP0344682)

Structured Review of the Evidence for Effects of Code Duplication on Software Quality

This report presents the detailed steps and results of a structured review of code clone literature. The aim of the review is to investigate the evidence for the claim that code duplication has a negative effect on code changeability. This report contains only the details of the review for which there is not enough place to include them in the companion paper published at a conference (Hordijk, Ponisio et al. 2009 - Harmfulness of Code Duplication - A Structured Review of the Evidence)

An Empirical Study of a Repeatable Method for Reengineering Procedural Software Systems to Object- Oriented Systems

This paper describes a repeatable method for reengineering a procedural system to an object-oriented system. The method uses coupling metrics to assist a domain expert in identifying candidate objects. An application of the method to a simple program is given, and the effectiveness of the various coupling metrics are discussed. We perform a detailed comparison of our repeatable method with an ad hoc, manual reengineering effort based on the same procedural program. The repeatable method was found to be effective for identifying objects. It produced code that was much smaller, more efficient, and passed more regression tests than the ad hoc method. Analysis of object-oriented metrics indicated both simpler code and less variability among classes for the repeatable method

A Model-Driven Architecture Approach to the Efficient Identification of Services on Service-oriented Enterprise Architecture

Service-Oriented Enterprise Architecture requires the efficient development of loosely-coupled and interoperable sets of services. Existing design approaches do not always take full advantage of the value and importance of the engineering invested in existing legacy systems. This paper proposes an approach to define the key services from such legacy systems effectively. The approach focuses on identifying these services based on a Model-Driven Architecture approach supported by guidelines over a wide range of possible service types

Towards a methodology for the development of integrated IT infrastructures

In this paper, the authors propose and validate a methodology for the development of integrated Information Technology (IT) infrastructures. The motivation for putting forward a new methodology is grounded on the limitations of the various software engineering methodologies (traditional) that exist today. Despite that the traditional methodologies result in the development of Information Systems (IS) from scratch, Enterprise Application Integration (EAI) builds integrated IT infrastructures using existing applications. This significant difference is associated with many issues needed to be realised and addressed like: (a) the changes that such an infrastructure brings to organisations, (b) the resistance to change and (c) the extension of IS lifecycle’s. The proposed methodology consist of eight stages and aims at supporting software engineers, organisations and researchers to build integrated IT infrastructures. As a result the methodology seeks to contribute to the body of knowledge