ProgramByDesign: Difference between revisions

Revision as of 08:32, 24 November 2015

Revision as of 02:22, 20 September 2018

Line 97:

Along the process dimension students learn that there are six steps to designing a

(simple) program, before they can run it and others can use it:

*# problem analysis with the goal of describing the classes of data that go into the program and come out;

*# the reformulation of the problem statement as a concise purpose statement;

*# the creation of examples that illustrate the purpose statement and that serve as criteria for success;

*# the organization of givens, also called a template or inventory;

*# coding;

*# and the creation of a test suite from examples to ensure the program works properly on small inputs.

Note that, as in [[test-driven development]], test cases are written ''before'' coding, as part of requirements analysis, rather than afterward as part of testing.