Case Studies of I-CBSD

Abstract

INVESTIGATION of I-CBSD issues and questions with the SYN tools has unique advantages, but also characteristic difficulties. The tools allow an experimenter to learn exactly what happens in component testing and system synthesis, because they provide graphs and analysis automatically. The difficulty comes in finding example components and systems that address a real issue of interest, yet fall within the severe restrictions the tools impose. For example, Section 18.3.3 studies the way in which two components with state are synthesized into a system with a cross-product state. A real example of this situation is a command-line editor component (with its state modes) invoked by a front-end control component whose state keeps track of what the editor will be allowed to do. The real example might use as components the UNIX ‘vi’ editor and a control program with a GUI. But these real components are far beyond the capabilities of the SYN tools, so in Section 18.3.3 they have simple stand-in components that roughlymodel editor- and control features. Finding and tuning these stand-ins so that SYN can handle them yet they retain the intuitive character of the real situation is not easy.