Situational Method Engineering: Fundamentals and Experiences

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 faceted framework to understand and classify issues in system development SME. The framework identifies four different but complementary viewpoints. Each view allows us to capture a particular aspect of situational methods. Inter-relationships between these views show how they influence each other. In order to study, understand and classify a particular view of SME in its diversity, we associate a set of facets with each view. As a facet allows an in-depth description of one specific aspect of SME, the views show the variety and diversity of these aspects.

💡 Research Summary

The paper addresses the emerging field of Situational Method Engineering (SME), which seeks to construct development methods that are tailored to the specific circumstances of individual projects rather than relying on one‑size‑fits‑all approaches. To bring order to the diverse issues that arise in SME, the authors propose a faceted framework built around four complementary viewpoints. Each viewpoint captures a distinct dimension of method engineering and is described by a set of “facets” that allow a fine‑grained description of that dimension.

The first viewpoint, Method Construction, focuses on the selection, composition, and configuration of method components (e.g., process fragments, techniques, tools). Its facets include granularity, reusability, dependency relations, extensibility, and degree of standardization. By defining a component library and explicit composition rules, this view enables engineers to assemble a method that matches the needs identified elsewhere in the framework.

The second viewpoint, Situational Modeling, provides a structured representation of the project’s context: domain characteristics, organizational culture, technical environment, team skills, schedule and budget constraints, and risk factors. Facets here are used to quantify and qualify each contextual variable, producing a “situational model” that can be matched against method components.

The third viewpoint, Method Application, translates the constructed method into concrete project activities. Its facets cover the lifecycle phases (planning, design, implementation, testing, deployment), tool integration, training requirements, verification mechanisms, and feedback collection points. This view supplies detailed workflows, checklists, and metrics that guide the execution of the tailored method.

The fourth viewpoint, Evaluation and Feedback, closes the loop by assessing product quality, process performance, and risk mitigation outcomes. Facets include performance indicators (quality, cost, time), risk analysis results, lessons‑learned documentation, and mechanisms for continuous improvement. Evaluation results are fed back into the situational model, prompting updates to the context description and, consequently, to the method construction in future iterations.

A key contribution of the paper is the explicit modeling of inter‑relationships among the four viewpoints. For instance, a high‑risk factor identified in the situational model influences the selection of risk‑handling components during method construction; the outcomes of method application generate evaluation data that may trigger a revision of the situational model, leading to a new composition of method components. This cyclical interaction supports dynamic adaptation throughout the project lifecycle.

To validate the framework, the authors present two industrial case studies. In the first, a large enterprise’s internal information‑system project suffered from schedule overruns when a traditional waterfall process was used. By applying the SME framework, the team built a hybrid Agile‑Waterfall method that incorporated risk‑aware planning and incremental delivery. The result was a 30 % reduction in schedule variance and improved stakeholder satisfaction. In the second case, a university course required students to develop educational software with limited experience. The situational model highlighted low team competence, leading the instructors to select lightweight prototyping techniques and to create a reusable component repository for future semesters. Both cases demonstrate how the facets enable systematic reuse of method components while still respecting project‑specific constraints.

The paper concludes by acknowledging current limitations: the definition of facets can be somewhat abstract, and the framework relies heavily on expert judgment. The authors call for the development of tool support—knowledge‑bases, recommendation engines, and possibly machine‑learning models—to automate the mapping between situational models and method components. They also suggest standardizing facet taxonomies to facilitate broader adoption across domains such as business‑process engineering. Overall, the work positions SME as a middle ground between rigid, generic methodologies and ad‑hoc, undocumented practices, offering a structured yet flexible path to method customization.