B01

• Input: Project situation, goals, constraints, reusable method fragments, roles, and work products.
• Operation: Select, configure, compose, and adapt method fragments to the situation using an explicit methodology metamodel.
• Output: A situation-specific method with process, people, modeling, and work-product definitions.
• Scope conditions: Information-intensive development and change work.
• Failure conditions: Situation factors are wrong; fragments do not compose; tailoring loses required controls.
• Predicted effect: Better situational fit than using a fixed method.
• Measurement: Requirement coverage, conformance, effort, and project outcomes.
• Implementation test: A separate engineer constructs a method from the same fragments and situation constraints.
• Decision rights: Method engineer proposes; project authority accepts tailoring.
• Uncertainty handling: Alternative configurations may be retained.
• Verification: Metamodel conformance and project review.
• Provenance: Fragment-to-method links.
• Implementation cost: Repository, modeling, and tailoring expertise.
• Limitations: Outcome depends on fragment quality. Direct: original method and metamodel abstracts. Inference: metrics.