Practitioner requirements for integrated Knowledge-Based Engineering in Product Lifecycle Management.

The effective management of knowledge as capital is considered essential to the success of engineering product/service systems. As Knowledge Management (KM) and Product Lifecycle Management (PLM) practice gain industrial adoption, the question of functional overlaps between both the approaches becomes evident. This article explores the interoperability between PLM and Knowledge-Based Engineering (KBE) as a strategy for engineering KM. The opinion of key KBE/PLM practitioners are systematically captured and analysed. A set of ranked business functionalities to be fulfiled by the KBE/PLM systems integration is elicited. The article provides insights for the researchers and the practitioners playing both the user and development roles on the future needs for knowledge systems based on PLM

Towards guidelines for building a business case and gathering evidence of software reference architectures in industry

Background: Software reference architectures are becoming widely adopted by organizations that need to support the design and maintenance of software applications of a shared domain. For organizations that plan to adopt this architecture-centric approach, it becomes fundamental to know the return on investment and to understand how software reference architectures are designed, maintained, and used. Unfortunately, there is little evidence-based support to help organizations with these challenges. Methods: We have conducted action research in an industry-academia collaboration between the GESSI research group and everis, a multinational IT consulting firm based in Spain. Results: The results from such collaboration are being packaged in order to create guidelines that could be used in similar contexts as the one of everis. The main result of this paper is the construction of empirically-grounded guidelines that support organizations to decide on the adoption of software reference architectures and to gather evidence to improve RA-related practices. Conclusions: The created guidelines could be used by other organizations outside of our industry-academia collaboration. With this goal in mind, we describe the guidelines in detail for their use.Peer ReviewedPostprint (published version

Learning Design and Service Oriented Architectures:a mutual dependency?

This paper looks at how the concept of reusability has gained currency in e-learning. Initial attention was focused on reuse of content, but recently attention has focused on reusable software tools and reusable activity structures. The former has led to the proposal of service-oriented architectures, and the latter has seen the development of the Learning Design specification. The authors suggest that there is a mutual dependency between the success of these two approaches, as complex Learning Designs require the ability to call on a range of tools, while remaining technology neutral. The paper describes a project at the UK Open University, SLeD, which sought to develop a Learning Design player that would utilise the service-oriented approach. This acted both as a means of exploring some of the issues implicit within both approaches and also provided a practical tool. The SLeD system was successfully implemented in a different university, Liverpool Hope, demonstrating some of the principles of re-use

Planning and Design Soa Architecture Blueprint

Service Oriented Architecture (SOA) is a framework for integrating business processes and supporting IT infrastructure as secure, standardized components-services-that can be reused and combined to address changing business priorities. Services are the building blocks of SOA and new applications can be constructed through consuming these services and orchestrating services within a business process. In SOA, services map to the business functions that are identified during business process analysis. Upon a successful implementation of SOA, the enterprise gain benefit by reducing development time, utilizing flexible and responsive application structure, and following dynamic connectivity of application logics between business partners. This paper presents SOA reference architecture blueprint as the building blocks of SOA which is services, service components and flows that together support enterprise business processes and the business goals

Reusability in manufacturing, supported by value net and patterns approaches

The concept of manufacturing and the need or desire to create artefacts or products is very, very old, yet it is still an essential component of all modem economies. Indeed, manufacturing is one of the few ways that wealth is created. The creation or identification of good quality, sustainable product designs is fundamental to the success of any manufacturing enterprise. Increasingly, there is also a requirement for the manufacturing system which will be used to manufacture the product, to be designed (or redesigned) in parallel with the product design. Many different types of manufacturing knowledge and information will contribute to these designs. A key question therefore for manufacturing companies to address is how to make the very best use of their existing, valuable, knowledge resources. […] The research reported in this thesis examines ways of reusing existing manufacturing knowledge of many types, particularly in the area of manufacturing systems design. The successes and failures of reported reuse programmes are examined, and lessons learnt from their experiences. This research is therefore focused on identifying solutions that address both technical and non-technical requirements simultaneously, to determine ways to facilitate and increase the reuse of manufacturing knowledge in manufacturing system design. [Continues.

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

Building Enterprise Architecture Agility and Sustenance with SOA

Service-Oriented Architecture(SOA) is primarily regarded as a technical architecture consisting of tools and service specification to build loosely coupled applications. At another level it is also a means to leverage flexibility and agility to system services as it offers a hierarchical framework to coordinate simultaneous business process design and implementations using loosely coupled service infrastructures. SOA has been debated both in the academy and industry and misinterpretations of its nature impede its adoption. We summarize its historical origins and current evolutions. We review technologies that underlie SOA. In particular, we address how to integrate SOA initiatives with current technology platforms, and how to enforce reuse during the design of loosely coupled systems. We also analyze SOA design methodologies and platforms, and what are their roles in the application integration. Finally we outline challenges and future research directions for SOA

Semantic model-driven development of service-centric software architectures

Service-oriented architecture (SOA) is a recent architectural paradigm that has received much attention. The prevalent focus on platforms such as Web services, however, needs to be complemented by appropriate software engineering methods. We propose the model-driven development of service-centric software systems. We present in particular an investigation into the role of enriched semantic modelling for a modeldriven development framework for service-centric software systems. Ontologies as the foundations of semantic modelling and its enhancement through architectural pattern modelling are at the core of the proposed approach. We introduce foundations and discuss the benefits and also the challenges in this context

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