Ontology-based patterns for the integration of business processes and enterprise application architectures

Increasingly, enterprises are using Service-Oriented Architecture (SOA) as an approach to Enterprise Application Integration (EAI). SOA has the potential to bridge the gap between business and technology and to improve the reuse of existing applications and the interoperability with new ones. In addition to service architecture descriptions, architecture abstractions like patterns and styles capture design knowledge and allow the reuse of successfully applied designs, thus improving the quality of software. Knowledge gained from integration projects can be captured to build a repository of semantically enriched, experience-based solutions. Business patterns identify the interaction and structure between users, business processes, and data. Specific integration and composition patterns at a more technical level address enterprise application integration and capture reliable architecture solutions. We use an ontology-based approach to capture architecture and process patterns. Ontology techniques for pattern definition, extension and composition are developed and their applicability in business process-driven application integration is demonstrated

A goal-oriented requirements modelling language for enterprise architecture

Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain

Rationale Management Challenges in Requirements Engineering

Rationale and rationale management have been playing an increasingly prominent role in software system development mainly due to the knowledge demand during system evaluation, maintenance, and evolution, especially for large and complex systems. The rationale management for requirements engineering, as a commencing and critical phase in software development life cycle, is still under-exploited. In this paper, we first survey briefly the state-of-the-art on rationale employment and applications in requirements engineering. Secondly, we identify the challenges in integrating rationale management in requirements engineering activities in order to promote further investigations and define a research agenda on rationale management in requirements engineering.

Purposive Teaching Styles for Transdisciplinary AEC Education: A Diagnostic Learning Styles Questionnaire

With the progressive globalisation trend within the Architecture, Engineering, and Construction (AEC) industry, transdisciplinary education and training is widely acknowledged as being one of the key factors for leveraging AEC organisational success. Conventional education and training delivery approaches within AEC therefore need a paradigm shift in order to be able to address the emerging challenges of global practices. This study focuses on the use of Personalised Learning Environments (PLEs) to specifically address learners’ needs and preferences (learning styles) within managed Virtual Learning Environments (VLEs). This research posits that learners can learn better (and be more readily engaged in managed learning environments) with a bespoke PLE, in which the deployment of teaching and learning material is augmented towards their individual needs. In this respect, there is an exigent need for the Higher Educational Institutions (HEIs) to envelop these new approaches into their organisational learning strategy. However, part of this process requires decision-makers to fully understand the core nuances and interdependencies of functions and processes within the organisation, along with Critical Success Factors (CSFs) and barriers. This paper presents findings from the development of a holistic conceptual Diagnostic Learning Styles Questionnaire (DLSQ) Framework, comprised of six interrelated dependencies (i.e. Business Strategy, Pedagogy, Process, Resources, Systems Development, and Evaluation). These dependencies influence pedagogical effectiveness. These finding contribute additional understanding to the intrinsic nature of pedagogy in leveraging transdisciplinary AEC training within organisations (to improve learner effectiveness). This framework can help organisations augment and align their strategic priorities to learner-specific traits

Early aspects: aspect-oriented requirements engineering and architecture design

This paper reports on the third Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, which has been held in Lancaster, UK, on March 21, 2004. The workshop included a presentation session and working sessions in which the particular topics on early aspects were discussed. The primary goal of the workshop was to focus on challenges to defining methodical software development processes for aspects from early on in the software life cycle and explore the potential of proposed methods and techniques to scale up to industrial applications

Technical Debt Prioritization: State of the Art. A Systematic Literature Review

Background. Software companies need to manage and refactor Technical Debt issues. Therefore, it is necessary to understand if and when refactoring Technical Debt should be prioritized with respect to developing features or fixing bugs. Objective. The goal of this study is to investigate the existing body of knowledge in software engineering to understand what Technical Debt prioritization approaches have been proposed in research and industry. Method. We conducted a Systematic Literature Review among 384 unique papers published until 2018, following a consolidated methodology applied in Software Engineering. We included 38 primary studies. Results. Different approaches have been proposed for Technical Debt prioritization, all having different goals and optimizing on different criteria. The proposed measures capture only a small part of the plethora of factors used to prioritize Technical Debt qualitatively in practice. We report an impact map of such factors. However, there is a lack of empirical and validated set of tools. Conclusion. We observed that technical Debt prioritization research is preliminary and there is no consensus on what are the important factors and how to measure them. Consequently, we cannot consider current research conclusive and in this paper, we outline different directions for necessary future investigations

Planning strategically, designing architecturally : a framework for digital library services

In an era of unprecedented technological innovation and evolving user expectations and information seeking behaviour, we are arguably now an online society, with digital services increasingly common and increasingly preferred. As a trusted information provider, libraries are in an advantageous position to respond, but this requires integrated strategic and enterprise architecture planning, for information technology (IT) has evolved from a support role to a strategic role, providing the core management systems, communication networks, and delivery channels of the modern library. Further, IT components do not function in isolation from one another, but are interdependent elements of distributed and multidimensional systems encompassing people, processes, and technologies, which must consider social, economic, legal, organisational, and ergonomic requirements and relationships, as well as being logically sound from a technical perspective. Strategic planning provides direction, while enterprise architecture strategically aligns and holistically integrates business and information system architectures. While challenging, such integrated planning should be regarded as an opportunity for the library to evolve as an enterprise in the digital age, or at minimum, to simply keep pace with societal change and alternative service providers. Without strategy, a library risks being directed by outside forces with independent motivations and inadequate understanding of its broader societal role. Without enterprise architecture, it risks technological disparity, redundancy, and obsolescence. Adopting an interdisciplinary approach, this conceptual paper provides an integrated framework for strategic and architectural planning of digital library services. The concept of the library as an enterprise is also introduced

Management and Service-aware Networking Architectures (MANA) for Future Internet Position Paper: System Functions, Capabilities and Requirements

Future Internet (FI) research and development threads have recently been gaining momentum all over the world and as such the international race to create a new generation Internet is in full swing: GENI, Asia Future Internet, Future Internet Forum Korea, European Union Future Internet Assembly (FIA). This is a position paper identifying the research orientation with a time horizon of 10 years, together with the key challenges for the capabilities in the Management and Service-aware Networking Architectures (MANA) part of the Future Internet (FI) allowing for parallel and federated Internet(s)

Uptake of BIM and IPD within the UK AEC Industry: the evolving role of the architectural technologist

Building Information Modelling is not only a tool, but also the process of creation, maintenance, distribution and co-ordination of an integrated database that collaboratively stores 2D and 3D information, with embedded physical and functional data within a project-building model. The uptake of BIM within the UK Architecture, Engineering and Construction (AEC) industry has been slow since the 1980’s, but over recent years, adoptions have increased. The increased collaborative nature of BIM, external data sharing techniques and progressively complex building design, promotes requirements for design teams to coordinate and communicate more effectively to achieve project goals. To manage this collaboration, new or evolved job roles may emerge. This research examined the current use of BIM, Integrated Project Delivery (IPD) and collaborative working in the UK AEC industry and job roles that have evolved or been created to cater for them. Using semi-structured interviews the interviewees indicated while several of the key enablers of IPD were being used, IPD itself had not been fully adopted. BIM was being used with some success but improvements could be made. New job roles such as the BIM Engineer and BIM Coordinator had been seen in the industry and evidence that the Architectural Technologist (AT) role is evolving into a more multidisciplinary role; this reflects similar findings of recent research