Using formal metamodels to check consistency of functional views in information systems specification

UML notations require adaptation for applications such as Information Systems (IS). Thus we have defined IS-UML. The purpose of this article is twofold. First, we propose an extension to this language to deal with functional aspects of IS. We use two views to specify IS transactions: the first one is defined as a combination of behavioural UML diagrams (collaboration and state diagrams), and the second one is based on the definition of specific classes of an extended class diagram. The final objective of the article is to consider consistency issues between the various diagrams of an IS-UML specification. In common with other UML languages, we use a metamodel to define IS-UML. We use class diagrams to summarize the metamodel structure and a formal language, B, for the full metamodel. This allows us to formally express consistency checks and mapping rules between specific metamodel concepts. (C) 2007 Elsevier B.V. All rights reserved

PuLSE-I: Deriving instances from a product line infrastructure

Reusing assets during application engineering promises to improve the efficiency of systems development. However, in order to benefit from reusable assets, application engineering processes must incorporate when and how to use the reusable assets during single system development. However, when and how to use a reusable asset depends on what types of reusable assets have been created.Product line engineering approaches produce a reusable infrastructure for a set of products. In this paper, we present the application engineering process associated with the PuLSE product line software engineering method - PuLSE-I. PuLSE-I details how single systems can be built efficiently from the reusable product line infrastructure built during the other PuLSE activities

Enhancing the employability of fashion students through the use of 3D CAD

The textile and apparel industry has one of the longest and most intricate supply chains within manufacturing. Advancement in technology has facilitated its globalisation, enabling companies to span geographical borders. This has led to new methods of communication using electronic data formats. Throughout the latter part of the 20th Century, 2D CAD technology established itself as an invaluable tool within design and product development. More recently 3D virtual simulation software has made small but significant steps within this market. The technological revolution has opened significant opportunities for those forward thinking companies that are beginning to utilise 3D software. This advanced technology requires designers with unique skill sets. This paper investigates the skills required by fashion graduates from an industry perspective. To reflect current industrial working practices, it is essential for educational establishments to incorporate technologies that will enhance the employability of graduates. This study developed an adapted action research model based on the work of Kurt Lewin, which reviewed the learning and teaching of 3D CAD within higher education. It encompassed the selection of 3D CAD software development, analysis of industry requirements, and the implementation of 3D CAD into the learning and teaching of a selection of fashion students over a three year period. Six interviews were undertaken with industrial design and product development specialists to determine: current working practices, opinions of virtual 3D software and graduate skill requirements. It was found that the companies had similar working practices independent of the software utilised within their product development process. The companies which employed 3D CAD software considered further developments were required before the technology could be fully integrated. Further to this it was concluded that it was beneficial for graduates to be furnished with knowledge of emerging technologies which reflect industry and enhance their employability skills

How should a small company interact in its business network to sustain its exchange effectiveness?

This paper investigates the dynamic alignment of network and business\ud development of two small firms in the printing industry. Developments are\ud followed over more than 8 years. The aim of the paper is to understand how\ud small firms can manage their network relations by maintaining both their\ud efficiency in existing business and flexibility to develop new business. The case comparison suggests that different networking approaches drive business\ud development. For successful business development both strong and varied ties\ud as well as the existence of different intermediary functions of partners are\ud necessary

Addressing business agility challenges with enterprise systems

It is clear that systems agility (i.e., having a responsive IT infrastructure that can be changed quickly to meet changing business needs) has become a critical component of organizational agility. However, skeptics continue to suggest that, despite the benefits enterprise system packages provide, they are constraining choices for firms faced with agility challenges. The reason for this skepticism is that the tight integration between different parts of the business that enables many enterprise systems\u27 benefits also increases the systems\u27 complexity, and this increased complexity, say the skeptics, increases the difficulty of changing systems when business needs change. These persistent concerns motivated us to conduct a series of interviews with business and IT managers in 15 firms to identify how they addressed, in total, 57 different business agility challenges. Our analysis suggests that when the challenges involved an enterprise system, firms were able to address a high percentage of their challenges with four options that avoid the difficulties associated with changing the complex core system: capabilities already built-in to the package but not previously used, leveraging globally consistent integrated data already available, using add-on systems available on the market that easily interfaced with the existing enterprise system, and vendor provided patches that automatically updated the code. These findings have important implications for organizations with and without enterprise system architectures