| 
|
QuoteRef: belaLA_1979
topics >
all references >
ThesaHelp:
references a-b
Topic:
management of large software projects
Topic:
sensitivity of software to change
Topic:
design for change
Group:
software maintenance
Topic:
configuration management
Topic:
software documentation
Topic:
efficiency
Topic:
deployable module or assembly
Topic:
good requirement specifications
Topic:
interface between program modules
Group:
requirement specification
Reference
Belady, L.A., Lehman, M.M., "The characteristics of large systems", pp. 106-138 , in Wegner, P. (ed.), "Research Directions in Software Technology ", Cambridge, Massachusetts, MIT Press , 1979 . Google
Other Reference
Lehman, M.M. and Belady, L.A. (eds.), Program Evolution. Processes of Software Change, London: Academic Press, 1985, p. 289-330.
108 ;;Quote: what makes a program large is all of its communication requirements; internal, organizational, implementers, users, and operational environment
114 ;;Quote: software complexity grows unless the software is restructured, either periodically or continuously
115 ;;Quote: a system must remain correct under an unending sequence of changes
115 ;;Quote: a system must maintain its good structure despite an unending sequence of changes
116 ;;Quote: measure system complexity by the percentage of modules impacted by a change in one module
121 ;;Quote: software repair should be assigned to those with maximum system overview and insight
121 ;;Quote: with multiple installations, users may reject releases; if so, multiple valid versions of the same module may evolve
122 ;;Quote: with large systems, documentation, tutorials and system may diverge because documentation is cut when schedules fail
126 ;;Quote: as a system grows, need to improve performance
128 ;;Quote: should build large software systems from self-contained software units
129 ;;Quote: the specification of a system unit must be complete, correct, accessible and compatible
129 ;;Quote: a software unit must be 'pluggable', with known loading in its use of other objects
129 ;;Quote: a software unit should have no unidentified side effects; i.e., no hidden assumptions
129 ;;Quote: a software unit's specification is the definition against which the unit is developed, tested, marketed, taught, used, and maintained
ThesaHelp: references a-b (396 items)
Topic: management of large software projects (63 items)
Topic: sensitivity of software to change (44 items)
Topic: design for change (75 items)
Group: software maintenance (14 topics, 355 quotes)
Topic: configuration management (24 items)
Topic: software documentation (64 items)
Topic: efficiency (96 items)
Topic: deployable module or assembly (10 items)
Topic: good requirement specifications (36 items)
Topic: interface between program modules (55 items)
Group: requirement specification (11 topics, 306 quotes)