| 
|
QuoteRef: clarS11_1999
topics >
all references >
ThesaHelp:
references c-d
Topic:
object-oriented design
Topic:
good requirement specifications
Topic:
importance of information hiding for requirement specification
Topic:
software components
Group:
requirement specification
Topic:
aspect-oriented programming
Topic:
design errors
Topic:
design for change
Topic:
sensitivity of software to change
Topic:
requirement specification by function
Topic:
pseudocode design
Reference
Clarke, S., Harrison, W., Ossher, H., Tarr, P., "Subject-oriented design: towards improved alignment of requirements, design and code.", OPPSLA '99, November 1999, Denver, CO, USA, pp. 325-339. Google
325 ;;Quote: object-oriented design limited: too large, limited reuse, too specialized, does not match requirements
325+;;Quote: a small change to requirements (features) may lead to widespread change of design (interfaces, classes, methods)
326 ;;Quote: UML and other object-oriented design languages align well with code and poorly with requirements
326 ;;Quote: subject-oriented programming--decompose design into design subjects, one per requirement; model each subject with an object-oriented design language; may overlap
327 ;;Quote: problem of scattering--a simple requirements change causes widespread change across the class hierarchy
327 ;;Quote: problem of tangling--design details for one requirement intermingled with details for other requirements
327 ;;Quote: problem of traceability--how does change in one software artifact (requirement, design, code) affect other artifacts
328 ;;Quote: design by functional decomposition aligns poorly with object-oriented code
ThesaHelp: references c-d (337 items)
Topic: object-oriented design (29 items)
Topic: good requirement specifications (36 items)
Topic: importance of information hiding for requirement specification (23 items)
Topic: software components (11 items)
Group: requirement specification (11 topics, 306 quotes)
Topic: aspect-oriented programming (2 items)
Topic: design errors (15 items)
Topic: design for change (75 items)
Topic: sensitivity of software to change (44 items)
Topic: requirement specification by function (20 items)
Topic: pseudocode design (43 items)