391 ;;Quote: programming languages are not adequate for building computer systems
|
391 ;;Quote: that standard conception of programming is obsolete: a programmer designs an algorithm and implements it by a sequence of instructions
|
392 ;;Quote: computers are primarily components of complex systems; not solutions for mathematical problems
|
392 ;;Quote: the building blocks of a system are subsystems; not programming language constructs
|
392 ;;Quote: it is often easier to replicate software than to integrate it into a new system
|
392 ;;Quote: the main activity of programming is the integration, modification, and explanation of existing programs
|
392 ;;Quote: programs now must fit an environment of needs, instead of performing a well-specified task
|
392 ;;Quote: an embedded system is one that is logically incorporated in a larger system
|
393 ;;Quote: a behavior specification characterizes what will be done, the sequence to be performed, and real-time measurements
|
393 ;;Quote: computers are mechanisms with which we interact; not an abstraction characterized by its results
|
394 ;;Quote: a programming system should provide a uniform framework for information that now appears in documentation, declarations, and assertions
|
395 ;;Quote: a programming system needs descriptive structures to maintain 'world views'; independent of implementation
|
395 ;;Quote: domain of interaction is independent of the domain of implementation and the subject domain
|
395 ;;Quote: an interaction object, e.g., filling a form, is implemented by a single component; while a subject domain object clearly cuts across the system
|
396 ;;Quote: behavior across an boundary is interaction; behavior within a boundary is implementation
|
396 ;;Quote: bodies of descriptive structures are most useful in the interaction domain
|
396 ;;Quote: need a uniform system for description that is not primarily a set of instructions
|
397 ;;Quote: program via a set of interrelated descriptions; includes prototypes and instances of object categories and processes
|
397 ;;Quote: an object or process instance may have more than one prototype description
|
397+;;Quote: prototype descriptions are related via hierarchies with different degrees of abstraction
|
397 ;;Quote: need multiple viewpoints to understand a component of a system; highly interactive
|
397 ;;Quote: a programmer needs to reorganize information dynamically with different views and levels of detail
|
397+;;Quote: a programmer needs to maneuver through a space of descriptions to view the interconnections
|
397 ;;Quote: each component of a system needs a detailed description; this may be done in stages
|
397 ;;Quote: programming systems will contain a base of knowledge about the application, potential components, and programming concepts
|