Abstract. The work presented in this paper is related to the area of Situational Method Engineering (SME) which focuses on project-specific method construction. We propose a generic process model supporting the integration of different existing SME approaches. This model shall help the method engineer either selecting one SME approach or combining several approaches that best fit the situation of the method engineering project at hand. The generic model presented in this paper already contains three SME techniques: (1) to assemble method chunks (2) to extend an existing method and (3) to generate a method by abstraction/instantiation of a model/meta-model. The paper presents and illustrates these three techniques and show how other SME techniques could be integrated in the model. 1.

The Software Engineering Body of Knowledge (Swebok, 2004), notably a book with 200 pages mentions the word interoperability just twice, once as an example for a system requirement and the second time as the title of a standard for library data models. This stands in contrast to the challenges of globalizing economy that

The area of method engineering has emerged in response to an increasing feeling that methods are not well suited to the needs of their users, the application engineers. Method engineering aims at developing methods. The paper uses the four worlds framework to investigate the subject of method engineering. It presents a state-of-art survey with a view to identifying the important problems and research directions being followed to solve these. The major problems not yet addressed or which have newly emerged are highlighted Key-words Method engineering, process engineering, fragment method, situational method 1.

Abstract. Model-driven user interface development environments and their associated methodologies have evolved over time to become more explicit, flexible, and reusable but they still lack to reach a level that allows tailoring a method to the reality of software development organizations and their projects. In order to address this shortcoming, method engineering provides strategies to define and tailor software engineering methods. They should address any usability concerns, which are primordial for the integration of model-driven user interface development methods in the competitive reality of software organizations. To address the issues of explicitly defining a flexible method, we defined a strategy based on method engineering for model-driven user interface development that uses usability goals as a starting point. With the application of this strategy, we aim to help method engineers executing the method with more efficiency when defining or tailoring methods and facilitate the application of model-based user interface development methods in software organizations.

Developers need tool support to help manage the wide range of inconsistencies that occur during software development. Such tools need to provide developers with ways to define, detect, record, present, interact with, monitor and resolve complex inconsistencies between different views of software artefacts, different developers and different phases of software development. This paper describes our experience with building complex multiple-view software development tools that support diverse inconsistency management facilities. We describe software architectures we have developed, user interface techniques used in our multiple-view development tools, and discuss the effectiveness of our approaches compared to other architectural and HCI techniques.