Pattern 15.10 Specify Component Views

Pattern 14.36, Construct a system behavior spec (p.628) — Pattern 14.38, Using state charts in system type models (p.636) describe concrete techniques to build the specification of the system of interest. Pattern 14.39, Specify component views (p.640) and Pattern 14.40, Compose Component views (p.642) explain how to show that separately specified components, when composed together in a particular way, realize the required behavior. 

Often, the context model will yield several classes of user, each with a different view of the system see Pattern 14.39, Specify component views (p.640) and Pattern 14.40, Compose Component views (p.642). 

We have several separately constructed views — Pattern 14.39, Specify component views (p.640). 

Pattern 14.30, Specify components (p.615) motivates the extra effort involved in separating specification of expected behavior from its implementation. Pattern 14.31, Bridge requirements and specifications (p.617) outlines a pragmatic view of requirements, as stated and understood by a user, and the more precise specifications that a developer might use to understand what must be built. Pattern 14.32, Use-case led system specification (p.619) explains why a use-case driven approach to requirements capture is prudent, but should always be interleaved with tools of more precise specifications. 

In the overall system view of the RailCab example (Figure 2), the RailCab component takes part in both, the Registration and the Convoy pattern. While those patterns have been specified independently from each other, a system requirement states ... 

---