| 
|
QuoteRef: pearDJ7_1973
topics >
all references >
ThesaHelp:
references p-r
Topic:
incremental development
Topic:
CADES structural modeling with holons
Topic:
data-driven design
Topic:
decomposition of a system into levels
Topic:
the 'uses' hierarchy for organizing systems
Topic:
information hiding
Topic:
automated tests of specifications and designs
Topic:
programming with a database of modules
Topic:
executable code from specifications and designs
Topic:
test data selection
Topic:
execution profile
Topic:
design languages
Group:
program design
Topic:
programming environment
Topic:
database implementation
Reference
Pearson, D.J., "'CADES' -- Computer aided design and evaluation system", Computer Weekly, July 26, August 2, August 9, 1973, pp. unnumbered. Google
Other Reference
QuoteRef: pratGD9_1976
1 ;;Quote: software design should be an iterative process
1 ;;Quote: design code for manipulation of data structures instead of designing data structures for functional codifications
1 ;;Quote: CADES design is a series of levels; each level an abstract machine
1 ;;Quote: a holon is the unit of CADES design; narrative description and formal design notation in SDL
1 ;;Quote: CADES formal design describes interaction of holons and how they manipulate data items
1 ;;Quote: in a good CADES design, each holon manipulates a small subset of data items provided by its parent holon
2 ;;Quote: CADES uses a design analyzer to manage the complex network of linkages between thousands of holons
2 ;;Quote: CADES generates code from a formal holon description and a design information system database
1 ;;Quote: CADES generates tests from a formal holon description and a design information system database
2 ;;Quote: the CADES animator uses individual holon performance estimates to evaluate overall performance
4 ;;Quote: should design until you think you understand a problem; code until you realize you don't; then iterate
4 ;;Quote: stage one of CADES structural modeling is initial designing; it should be short
4 ;;Quote: stage two of CADES structural modeling is designing the data structures
4 ;;Quote: stage three of CADES structural modeling is defining the system's levels and functions
4 ;;Quote: stage four of CADES structural modeling is defining a holon tree
4 ;;Quote: stage five of CADES structural modeling is narrative descriptions of each holon which relate it to other holons
4 ;;Quote: Structural modeling uses the systems description language, SDL, to code high level narratives
4+;;Quote: stage six of CADES structural modeling is formal definitions of each holon
4 ;;Quote: the formal definition of a CADES holon defines the information and holons provided by its parent
6 ;;Quote: the formal definition of a CADES holon defines its data blocks, calls, call parameters, and call actions
6 ;;Quote: each CADES holon includes project management information such as start date and percentage complete
6 ;;Quote: the CADES holon database is implemented as a transposed file with columns of data
ThesaHelp: references p-r (245 items)
Topic: incremental development (74 items)
Topic: CADES structural modeling with holons (24 items)
Topic: data-driven design (41 items)
Topic: decomposition of a system into levels (49 items)
Topic: the 'uses' hierarchy for organizing systems (18 items)
Topic: information hiding (50 items)
Topic: automated tests of specifications and designs (12 items)
Topic: programming with a database of modules (94 items)
Topic: executable code from specifications and designs (18 items)
Topic: test data selection (39 items)
Topic: execution profile (42 items)
Topic: design languages (12 items)
Group: program design (13 topics, 453 quotes)
Topic: programming environment (46 items)
Topic: database implementation (18 items)