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

Development of an Extended Product Lifecycle Management through Service Oriented Architecture.

Organised by: Cranfield UniversityThe aim of this work is to define new business opportunities through the concept of Extended Product Lifecycle Management (ExtPLM), analysing its potential implementation within a Service Oriented Architecture. ExtPLM merges the concepts of Extended Product, Avatar and PLM. It aims at allowing a closer interaction between enterprises and their customers, who are integrated in all phases of the life cycle, creating new technical functionalities and services, improving both the practical (e.g. improving usage, improving safety, allowing predictive maintenance) and the emotional side (e.g. extreme customization) of the product.Mori Seiki – The Machine Tool Company; BAE Systems; S4T – Support Service Solutions: Strategy and Transitio

Designing a consulting services architecture model

textDuring my years of experience in the technology industry, it has become obvious that standard processes and methodologies within the engineering discipline are at a mature state. The realization though is that software engineering specifically lags behind. Most software engineering methodologies that I have studied focus on the mission of software development. It is this realization and the need for structure that led me to review existing methodologies used within my company's software services organization. The definition of what a successful software services methodology entails is rather limited. This report will provide a history of existing software engineering methodologies that I have studied, describe an initial services method that was being developed within my organization, develop a new model that addresses previous shortcomings and identify additional components required to further define a strong software services-oriented delivery methodology.Electrical and Computer Engineerin

Robust decision making for agile systems development Part 1: exploring the paradigm

The need for agility in operational systems within the defence enterprise and procurement domains has been identified by many authors, and over time, there have been a number of initiatives and programmes that have sought to identify the nature of agility, and the means by which it can be defined and employed within individual cases and scenarios. These have identified impediments to the successful realization of agile practices and methods, particularly the resilience of agile decision making throughout the conceptual understanding, design and implementation of the operational system. To further investigate the extent to which this process can be implemented in a robust and reliable manner, Cranfield University created the ‘Robust Enterprise-based Approach for Agility in Capability Through-life (REA2CT)’ framework, which provides a number of functional steps to institute a systems development lifecycle approach to producing agile solutions for use in networked systems and systems-of-systems. This paper briefly examines the Customer Need (CN) for the enterprise-based delivery of system (of systems) agility into the operational domain. Axiomatic Design (AD) theory is used to describe the REA2CT framework, identifying Functional Requirements (FRs) which might satisfy the CN for agility. Initial Design Parameters (DPs) are proposed to satisfy the FRs

Aligning a Service Provisioning Model of a Service-Oriented System with the ITIL v.3 Life Cycle

Bringing together the ICT and the business layer of a service-oriented system (SoS) remains a great challenge. Few papers tackle the management of SoS from the business and organizational point of view. One solution is to use the well-known ITIL v.3 framework. The latter enables to transform the organization into a service-oriented organizational which focuses on the value provided to the service customers. In this paper, we align the steps of the service provisioning model with the ITIL v.3 processes. The alignment proposed should help organizations and IT teams to integrate their ICT layer, represented by the SoS, and their business layer, represented by ITIL v.3. One main advantage of this combined use of ITIL and a SoS is the full service orientation of the company.Comment: This document is the technical work of a conference paper submitted to the International Conference on Exploring Service Science 1.5 (IESS 2015

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

Modeling and Execution of Multienterprise Business Processes

We discuss a fully featured multienterprise business process plattform (ME-BPP) based on the concepts of agent-based business processes. Using the concepts of the subject-oriented business process (S-BPM) methodology we developed an architecture to realize a platform for the execution of distributed business processes. The platform is implemented based on cloud technology using commercial services. For our discussion we used the well known Service Interaction Patterns, as they are empirically developed from typical business-to-business interactions. We can demonstrate that all patterns can be easily modeled and executed based on our architecture. We propose therefore a change from a control flow based to an agent based view to model and enact business processes.Comment: arXiv admin note: substantial text overlap with arXiv:1404.273