© 2002 by Carnegie Mellon University Carnegie Mellon Software Engineering Institute V2.6wjh, page 1 Fundamental Model - Calling Thru an API API Provider API Caller Coding & design standards API Interface correctness & sufficiency Test Performance Change control / stability Lessons / Evolution

© 2002 by Carnegie Mellon University Carnegie Mellon Software Engineering Institute V2.6wjh, page 2 JMPS -- Building on Unknowns Are there services that the Framework does not supply that applications will need? How to test the framework itself? Will there be performance issues for apps? How stable is the framework? Will it change? Who is in charge of these changes? Were coding standards followed? What lessons from designing the Framework API will apply to designing component APIs? Framework unknowns Underlying OS and HW xxxx framework (basic svcs)

© 2002 by Carnegie Mellon University Carnegie Mellon Software Engineering Institute V2.6wjh, page 3 Are there services that the Framework does not supply that applications will need? How to test the framework itself? Will there be performance issues for apps? How stable is the framework? Will it change? Who is in charge of these changes? Were coding standards followed? What lessons from designing the Framework API will apply to designing component APIs? xxx -- Building on Unknowns Note: Generic ABC is not totally representative of a “real” ABC or common component Will common component(s) need to go around the framework? For what reasons? What interfaces are exposed in the Common component(s) for the ABCs? How do we test common component(s)? Will components raise performance issues? Who controls changes to components? How are they decided upon? Who/what defines/enforces coding and development styles?? What are Lessons learned from the 1 st common component? How to leverage these? What is the plan for evolution of common components? Common components unknowns Underlying OS and HW xxxx framework (basic svcs) Common component - ZZZZ Common component – WWWW, etc Instability at Lower Levels Can Lead to System Wide Chaos

© 2002 by Carnegie Mellon University Carnegie Mellon Software Engineering Institute V2.6wjh, page 4 xxxx – Full Architecture A complete pilot requires all layers. Will it all come together? Underlying OS and HW xxxx framework (basic svcs) Common component - ZZZZ Common component – WWWW, etc Enables system throughput analysis Enables identification and handling of CM, version control and other stability issues Provides some validation of coding and development styles Provides some degree of interface validation Provides testable, integrated thread throughout the system Enables initial validation of “system manager” roles tt ABC tu ABC

3. Integration Tasks 2. Integration Interface Artifacts Integration document debug repair enhance test UPC Development(s) 1. Other Integration Efforts

2. Integration Interface Artifacts Integration document debug repair enhance test UPC Development(s) Framework Common Components Revision design dialogs 3. Integration Tasks

Integration document debug repair enhance test UPC Development(s) Source Repository(s) UPC Problem Reports Framework Common Components Revision design dialogs 3. Integration Tasks

2. Integration Interface Artifacts Integration document debug repair enhance test UPC Development(s) Source Repository(s) UPC Problem Reports Framework Common Components Revision design dialogs 4. Test Facility planner Evaluator / trainer Distribute Rebuild & test Help desk

Integration document debug repair enhance test UPC Development(s) Source Repository(s) UPC Problem Reports 1. Other Integration Efforts Framework Common Components Revision design dialogs test facility(s) planner Evaluator / trainer Distribute Rebuild & test Help desk