Synthesizing Component- Level Behavior Models from Scenarios and Constraints Ivo Krka

Motivation Early development phases Scenarios Properties / Constraints Partial but straightforward Synthesizing behavior models from high-level specifications Statecharts, LTSs Architectural analysis Basis for subsequent development phases Final models do not account for partiality How to support gradual system refinement?

Web Cache System

Cache’s Behavior S0 S1 S2 S3 S4 requestCacheDatarequestServerDataresponseServerData responseCacheData What else can occur? S5 S6 requestCacheData

Modal Transition Systems Specify what is required Specify what is potential S0 S1 S2 A B A? A B?

Partial Behavior Models Proven useful Exploration of design space Requirements elicitation Architectural refinement System-level model issues Scale System-level assumptions Solution? Synthesize Component-Level Models

Synthesis Phases Obtain component-level constraints Generate initial MTSs Annotate sequence diagrams Refine initial MTSs

Web Cache System (2) S0 S1 S2 S3 S4 requestCacheData requestServerDataresponseServerData responseCacheData S5 requestCacheData responseServerData? requestServerData? responseServerData? responseCacheData responseServerData?

Conclusions and Future Work Early discovery of design flaws Overly constraining constraints Bad scenarios Lacking design System vs. component view Future work Realistic case studies Support for requirements elicitation Support in OTS component selection

Thank you!