Topic: execution with program stubs

Summary

In design, particularly top-down design, a program may be tested after partial specification. The designer wants to try out his design before fully implementing his programs. He can partially execute already completed programs by defining program stubs for unimplemented procedures or by prompting the user for unimplemented results. The goal of partial execution is an incomplete but working system. Often this goal can be better satisfied by independent sub-systems tied together in a user interface. Program stubs are useful for managing large-scale software development. (cbb 5/80)

Subtopic: program stubs

Quote: with TOPD's design notation can specify a model for unimplemented parts; execution checks for consistency [»hendP9_1975]

QuoteRef: snowRA_1973 ;;Pearl allows partial execution of a partially specified program

Quote: in top-down design, a proper top can execute early in development; allows iterative process of code, integrate, and test [»millHD_1979] no ref ;;Mills 71: debug higher level programs by user supplied program stubs for undefined components

Subtopic: prompt user for stubs

QuoteRef: smitDC6_1975 ;;88 don't have to specify all paths-- if path unspecified at execution time then machine prompts user for more info

QuoteRef: sammJE_1969 ;;244 user talked through command if it is incomplete

Related Topics

Group: requirement specification   (11 topics, 307 quotes)
Topic: executable code from specifications and designs (18 items)
Topic: incremental development (74 items)
Topic: incremental execution (22 items)
Topic: incremental testing
(26 items)