From Method Fragments to Method Services

In Method Engineering (ME) science, the key issue is the consideration of information system development methods as fragments. Numerous ME approaches have produced several definitions of method parts. Different in nature, these fragments have nevertheless some common disadvantages: lack of implementation tools, insufficient standardization effort, and so on. On the whole, the observed drawbacks are related to the shortage of usage orientation. We have proceeded to an in-depth analysis of existing method fragments within a comparison framework in order to identify their drawbacks. We suggest overcoming them by an improvement of the ?method service? concept. In this paper, the method service is defined through the service paradigm applied to a specific method fragment ? chunk. A discussion on the possibility to develop a unique representation of method fragment completes our contribution

Information Systems Evolution: A Process Model for Integrating New Services

Integration of different components that compose enterprise Information System (IS) represents a big challenge in the IS development. However, it is indispensable in order to avoid fragmentation of the IS and redundancy between different IS applications. In this work we consider service-driven IS engineering as a prospective approach to deal with IS fragmentation and interoperability of different IS components. We introduce the notion of Information System Service (ISS) and propose a process model supporting legacy IS evolution by integration of new services. We claim that such an approach has to take into account a large number of integration situations and therefore has to be built by applying situational method engineering principals and defined as a collection of reusable method chunks

Engineering Methods in the Service-Oriented Context : 4th IFIP WG 8.1 Working Conference on Method Engineering, ME 2011, Paris, France, April 20-22, 2011. Proceedings

International audienceThis book constitutes the refereed proceedings of the 4th IFIP WG 8.1 Working Conference on Method Engineering, ME 2011, held in Paris, France, in April 2011. The 13 revised full papers and 6 short papers presented together with the abstracts of two keynote talks were carefully reviewed and selected from 30 submissions. The papers are organized in topical sections on situated method engineering, method engineering foundations, customized methods, tools for method engineering, new trends to build methods, and method engineering services

Refactoring software development process terminology through the use of ontology

In work that is ongoing, the authors are examining the extent of software development process terminology drift. Initial findings suggest there is a degree of term confusion, with the mapping of concepts to terms lacking precision in some instances. Ontologies are concerned with identifying the concepts of relevance to a field of endeavour and mapping those concepts to terms such that term confusion is reduced. In this paper, we discuss how ontologies are developed. We also identify various sources of software process terminology. Our work to date indicates that the systematic development of a software development process ontology would be of benefit to the entire software development community. The development of such an ontology would in effect represent a systematic refactoring of the terminology and concepts produced over four decades of software process innovation

Refactoring software development process terminology through the use of ontology

peer-reviewedIn work that is ongoing, the authors are examining the extent of software development process terminology drift. Initial findings suggest there is a degree of term confusion, with the mapping of concepts to terms lacking precision in some instances. Ontologies are concerned with identifying the concepts of relevance to a field of endeavour and mapping those concepts to terms such that term confusion is reduced. In this paper, we discuss how ontologies are developed. We also identify various sources of software process terminology. Our work to date indicates that the systematic development of a software development process ontology would be of benefit to the entire software development community. The development of such an ontology would in effect represent a systematic refactoring of the terminology and concepts produced over four decades of software process innovation

Towards Common Ground in SME: An Ontology of Method Descriptors

Part 3: Method Engineering FoundationsInternational audienceThe Method Engineering (ME) community is a prolific research domain where competing Situational Method Engineering (SME) approaches have been defined and used for composing, adapting or/and configuring a method into modular constructs according to their own modularization vision. This diversity shows the richness of the ME domain but implies some drawback like unnecessary confusion for non ME expert, lack of standard & interoperability, lack of implementation tool. However, researchers are agreed that a common ground in SME is a hot matter of discussion. Assuming that the differences between SME approaches are purposeful, we propose to reach a semantic common ground on what types of core concepts constitute a method descriptor. To achieve it, an ontology-based approach is applied in SME to design an ontology of method descriptors as a domain ontology. The semantics of the six most popular SME approaches modular constructs are defined according to this ontology in order to show its usage and its relevance. Finally, usage scenarios have been sketched to show that the ontology can be the start up phase for reducing the ME drawbacks mentioned above

Towards Method Component Contextualization

International audienceMethod Engineering (ME) is a discipline which aims to bring effective solutions to the construction, improvement and modification of the methods used to develop Information Systems (IS). Situational Method Engineering (SME) promotes the idea of retrieving, adapting and tailoring components, rather than complete methodologies, to the specific context. Existing SME approaches use the notion of context for characterizing situations of IS development projects and for guiding the method components selection from a repository. However, in the reviewed literature, there is no proposed approach to specify the specific context of method components. This paper provides a detailed vision of context and a process for contextualizing methods in the IS domain. This proposal is illustrated with three case studies: scenario conceptualization, project portfolio management, and decision-making

Software Process Modeling with Eclipse Process Framework

The software development industry is constantly evolving. The rise of the agile methodologies in the late 1990s, and new development tools and technologies require growing attention for everybody working within this industry. The organizations have, however, had a mixture of various processes and different process languages since a standard software development process language has not been available. A promising process meta-model called Software & Systems Process Engineering Meta- Model (SPEM) 2.0 has been released recently. This is applied by tools such as Eclipse Process Framework Composer, which is designed for implementing and maintaining processes and method content. Its aim is to support a broad variety of project types and development styles. This thesis presents the concepts of software processes, models, traditional and agile approaches, method engineering, and software process improvement. Some of the most well-known methodologies (RUP, OpenUP, OpenMethod, XP and Scrum) are also introduced with a comparison provided between them. The main focus is on the Eclipse Process Framework and SPEM 2.0, their capabilities, usage and modeling. As a proof of concept, I present a case study of modeling OpenMethod with EPF Composer and SPEM 2.0. The results show that the new meta-model and tool have made it possible to easily manage method content, publish versions with customized content, and connect project tools (such as MS Project) with the process content. The software process modeling also acts as a process improvement activity.Ohjelmistoprosessin mallinnus Eclipse Process Frameworkilla ja SPEM 2.0 metamallilla Ohjelmistot ja ohjelmistoteollisuus kehittyvät jatkuvasti. Ketterien menetelmien tulo 1990-luvun loppupuolella, uudet kehitystyökalut ja teknologiat vaativat yhä enemmän huomiota alalla työskenteleviltä ihmisiltä. Organisaatioilla on kuitenkin ollut sekalainen kirjo prosesseja ja erilaisia prosessikuvauskieliä, koska standardia kuvauskieltä ei ole ollut saatavilla. Prosessimetamalli SPEM 2.0 julkaistiin hiljattain. Tätä mallia hyödyntää mm. Eclipse Process Framework Composer (EPFC) –työkalu, joka on suunniteltu prosessien ja menetelmäsisällön kehittämiseen ja ylläpitoon. Työkalun tavoitteena on tukea useita erilaisia projektityyppejä ja kehitystyylejä. Tässä työssä esitellään seuraavat aiheet ja käsitteet: ohjelmistoprosessit, mallit, perinteiset ja ketterät lähestymistavat, metoditekniikkaa sekä prosessien kehittäminen. Lisäksi tutustutaan muutamiin tunnetuimmista metodologioista (RUP, OpenUP, OpenMethod, XP ja Scrum) ja vertaillaan näitä. Työssä tutkitaan tarkemmin Eclipse Process Framework Composer –työkalua, SPEM 2.0 metamallia, näiden ominaisuuksia, käyttöä sekä mallintamista. Esitän tutkimustulokset ja tutkimuksenkulun OpenMethodin mallintamisesta EPFC –työkalulla sekä SPEM 2.0 -metamallilla. Tulokset osoittavat, että uusi metamalli ja työkalu helpottavat prosessin ja menetelmäsisällön hallintaa, mahdollistavat räätälöityjen julkaisujen teon sisällöstä, sekä yhdistävät prosessin projektityökaluihin kuten MS Projectiin. Mallinnus voidaan lisäksi ymmärtää osana prosessin kehittämistä.Siirretty Doriast

Applying Situational Method Engineering to the Development of Service Identification Methods

Recently, situational method engineering (SME) has become more and more popular. Due to the fact that different situations require different methods, SME offers a flexible adaptation of methods. Furthermore, various approaches for the identification of services within service-oriented architectures have been proposed in the last few years. However, none of them provide a significant degree of situation-specific adaptability. Goal of this paper is to develop a meta model that can be used to construct service identification methods specific to certain situations. Therefore, ideas of SME are transferred into the realm of service identification. The meta model is further applied to a fictitious case