Group:
hypertext
Group:
program module
Topic:
automated tests of specifications and designs
Topic:
compiling pseudocode designs
Topic:
data-driven design
Topic:
design documentation
Topic:
design languages
Topic:
formal methods and languages
Topic:
programming with a database of modules
Topic:
stepwise refinement
Topic:
temporal database
| |
Summary
Pratten, Snowdon, and Pearson describe CADES as a structural modeling language in units called holons. The holons have formal and narrative descriptions. The formal description includes the input and output data items. The database includes variants and historical versions. In Pearson's preliminary design, the system generates test case, code, animations, and performance estimates.
CADES is a system for iterative construction of a conceptual representation of software. Brooks sees such conceptual representations as the proper target for building software. (cbb 3/98)
Subtopic: design with interlocking, abstract machines that manipulates data structures 
| Quote: CADES design is a series of levels; each level an abstract machine [»pearDJ7_1973]
| | Quote: design code for manipulation of data structures instead of designing data structures for functional codifications [»pearDJ7_1973]
| | Quote: the hard part of programming is constructing the interlocking concepts that make a software entity [»brooFP_1986]
|
Subtopic: holon
| Quote: a holon is the unit of CADES design; narrative description and formal design notation in SDL [»pearDJ7_1973]
| | Quote: the formal definition of a CADES holon defines the information and holons provided by its parent [»pearDJ7_1973]
| | Quote: the formal definition of a CADES holon defines its data blocks, calls, call parameters, and call actions [»pearDJ7_1973]
| | Quote: in a good CADES design, each holon manipulates a small subset of data items provided by its parent holon [»pearDJ7_1973]
| | Quote: the CADES holon database is implemented as a transposed file with columns of data [»pearDJ7_1973]
|
Subtopic: versions
| Quote: CADES defines variants for related versions of information with generations for minor variations [»pratGD9_1976]
| | Quote: software design should be an iterative process [»pearDJ7_1973]
| | Quote: each CADES holon includes project management information such as start date and percentage complete [»pearDJ7_1973]
|
Subtopic: analysis, animator, testing, code generation
| Quote: CADES uses a design analyzer to manage the complex network of linkages between thousands of holons [»pearDJ7_1973]
| | Quote: the CADES animator uses individual holon performance estimates to evaluate overall performance [»pearDJ7_1973]
| | Quote: CADES generates tests from a formal holon description and a design information system database [»pearDJ7_1973]
| | Quote: CADES generates code from a formal holon description and a design information system database [»pearDJ7_1973]
|
Subtopic: formal design
| Quote: CADES formal design describes interaction of holons and how they manipulate data items [»pearDJ7_1973]
| | Quote: the CADES indices for documentation and source files are very important [»pratGD9_1976]
| | Quote: Structural modeling uses the systems description language, SDL, to code high level narratives [»pearDJ7_1973]
|
Subtopic: stages of design
| Quote: stage one of CADES structural modeling is initial designing; it should be short [»pearDJ7_1973]
| | Quote: stage two of CADES structural modeling is designing the data structures [»pearDJ7_1973]
| | Quote: stage three of CADES structural modeling is defining the system's levels and functions [»pearDJ7_1973]
| | Quote: stage four of CADES structural modeling is defining a holon tree [»pearDJ7_1973]
| | Quote: stage five of CADES structural modeling is narrative descriptions of each holon which relate it to other holons [»pearDJ7_1973]
| Quote: stage six of CADES structural modeling is formal definitions of each holon
|
Related Topics
Group: hypertext (44 topics, 786 quotes)
Group: program module (10 topics, 336 quotes)
Topic: automated tests of specifications and designs (12 items)
Topic: compiling pseudocode designs (8 items)
Topic: data-driven design (41 items)
Topic: design documentation (43 items)
Topic: design languages (12 items)
Topic: formal methods and languages (53 items)
Topic: programming with a database of modules (94 items)
Topic: stepwise refinement (25 items)
Topic: temporal database
(25 items)
|
