MEMOS: A Methodology for Modeling Services

Mick Kerrigan, Barry Norton, Elena SimperlSBPM 2010 · OpenReview

Introduction

Semantic Web Services (SWS) represent a significant evolution in Service-Oriented Architecture (SOA), promising a future where machines can automatically discover, compose, and invoke services based on logic rather than just syntax. Despite this potential, industry adoption has been hindered by the extreme complexity of building these services. Developing an SWS requires a sophisticated blend of ontology engineering, functional description, and behavioral modeling.

MEMOS (Methodology for Modeling Services) addresses this "barrier to entry" by providing a comprehensive, standardized framework. It bridges the gap between high-level business requirements and executable, semantically-enriched IT services, offering a systematic roadmap for engineers to reduce costs and improve the quality of service descriptions.

Methodology Structure

The MEMOS framework is structured to provide "consistency of action" across the development lifecycle. It defines the relationships between the various components of a project, ensuring that every participant understands their role and the expected outputs.

The MEMOS meta-model illustrating the relationships between roles, phases, activities, tasks, and artifacts.

As shown in the meta-model in Figure 1, the methodology is organized hierarchically:

  • Phases contain multiple Activities.
  • Activities are further broken down into specific Tasks.
  • Roles (of which there are 14 defined) are assigned to perform these tasks.
  • Tasks utilize or produce Artifacts, which serve as the tangible outputs of the process.

The Five Phases of MEMOS

MEMOS aligns with the standard Software Development Cycle (SDC) but tailors it specifically for the nuances of semantic modeling. The methodology is divided into five distinct phases, encompassing 28 activities and 94 individual tasks.

A detailed breakdown of the five development phases and their associated activities.
  1. Requirements: This phase focuses on identifying the core needs and gathering functional, non-functional (NF), behavioral, and knowledge requirements.
  2. Design: Engineers define the high-level and physical architectures. A critical component here is the design of "Mediators" to handle data heterogeneities and the definition of choreographies.
  3. Implementation: Designs are translated into concrete semantic artifacts, including ontologies, service descriptions, and groundings.
  4. Testing: This phase involves rigorous unit and integration testing, including functional and user acceptance tests.
  5. Installation & Checkout: The final phase ensures the services are documented, installed, and that maintainers are properly trained.

Key Insights and Innovations

MEMOS introduces several critical concepts that distinguish it from simpler modeling approaches:

  • Provider-Requester Split: The methodology explicitly separates tasks for service providers (advertising functionality) and service requesters (fulfilling specific goals). This dual perspective ensures that both sides of a service interaction are adequately modeled.
  • Mediators as First-Class Citizens: In a distributed web environment, data uniformity is rare. MEMOS treats the creation of "Mediators"—which resolve differences between different ontologies—as a core design activity rather than an afterthought.
  • Grounding as the Technical Bridge: A significant portion of the methodology focuses on "Grounding," the link between abstract semantic concepts and concrete data schemas (like WSDL). This is essential for making semantic services executable in existing web infrastructures.

Evaluation and Results

The methodology was validated through professional reviews by the OASIS Semantic Execution Environment technical committee and a week-long case study involving three SWS experts. In the case study, which focused on a Tourism Domain (hotel and car bookings), experts found the requirements and implementation tasks intuitive and easy to follow using the provided guidelines.

Key results from the evaluation include:

  • Standardization: MEMOS was successfully adopted by the SHAPE project for use with SoaML (Service oriented architecture Modeling Language), demonstrating its flexibility across different modeling standards.
  • Identification of Bottlenecks: The evaluation highlighted that "High-Level Architecture" design remains the most challenging phase due to the inherent complexity of mapping multiple semantic components.

Conclusion and Future Work

MEMOS provides a much-needed systematic approach to SWS development, offering a comprehensive framework of 28 activities and 94 tasks. While the current version focuses on individual services, future iterations aim to incorporate complex service composition. Additionally, the authors are working toward better integration of the methodology into existing development environments, such as the Web Service Modeling Toolkit, to further automate the transition between tasks and roles.

Summary updated

BibTeX
@inproceedings{kerrigan2010memos,
  author = {Mick Kerrigan and Barry Norton and Elena Simperl},
  title = {{MEMOS: A Methodology for Modeling Services}},
  booktitle = {SBPM},
  year = {2010},
  url = {https://openreview.net/forum?id=OfneEsvBOQ},
}
Figure