105 ;;Quote: before release, need to merge bug fixes into main development work; DSEE provides a multi-window interactive merge command to help automate the process

106 ;;Quote: DSEE uses interleaved deltas like SCCS; allows single pass recovery of any version (an 'extended stream'); difficult in RCS

106 ;;Quote: Cedar isolates changes by requiring an explicit request to merge changes into your version

106 ;;Quote: a DSEE system model describes the components, their build dependencies, and the build rules needed to recreate the system

107 ;;Quote: the DSEE configuration thread states which version of each component goes into a build; specific, most recent, etc.

108 ;;Quote: software development requires much more than programming (e.g., telephoning customers); an environment should support all of these activities

108 ;;Quote: a DSEE task has a title which describes a high-level activity and a list of textual items defining necessary sub-tasks

108 ;;Quote: DSEE tasks are displayed graphically as active items and completed items; the later forms the 'transcript'; the former includes the 'current task'

108 ;;Quote: when DSEE's history manager receives a user's modification comments it sends copies to the task's transcript

108+;;Quote: every new version of a DSEE element is tagged with the name of the current task that created the element

108 ;;Quote: a DSEE tasklist contains references to tasks; for managing each user's active tasks and each library's active and completed tasks

110 ;;Quote: DSEE advice manager for common tasks; contains task templates and forms

110 ;;Quote: in source control, users should define dependencies between elements for warnings prior to changes and notification after changes

111 ;;Quote: DSEE can automatically send alarms for changes to a tasklist

112 ;;Quote: DSEE manages over a million lines of code successfully