gIBIS: a hypertext tool for exploratory policy discussion
ACM Transactions on Information Systems (TOIS)
Design environments for constructive and argumentative design
CHI '89 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
SIBYL: A qualitative decision management system
Artificial intelligence at MIT expanding frontiers
Design management based on design traces
DAC '90 Proceedings of the 27th ACM/IEEE Design Automation Conference
Questions, options, and criteria: elements of design space analysis
Design rationale
Version models for software configuration management
ACM Computing Surveys (CSUR)
Automated capture of rationale for the detailed design process
AAAI '99/IAAI '99 Proceedings of the sixteenth national conference on Artificial intelligence and the eleventh Innovative applications of artificial intelligence conference innovative applications of artificial intelligence
Versioned Hypermedia can improve software document management
Proceedings of the thirteenth ACM conference on Hypertext and hypermedia
Design Rationale Systems: Understanding the Issues
IEEE Expert: Intelligent Systems and Their Applications
Evolution Support by Homogeneously Documenting Patterns, Aspects and Traces
CSMR '02 Proceedings of the 6th European Conference on Software Maintenance and Reengineering
The software concordance: a new software document management environment
Proceedings of the 21st annual international conference on Documentation
An infrastructure for development of object-oriented, multi-level configuration management services
Proceedings of the 27th international conference on Software engineering
Design rationale: Researching under uncertainty
Artificial Intelligence for Engineering Design, Analysis and Manufacturing
| Hi-index | 0.00 |
Software Concordance Design Rationale (SCDR) is a tool for recording design rationale, which describes the reasons that a system's design was chosen. Using the editing, linking, and versioning services of the Software Concordance system, SCDR allows developers to structure their design discussions and connect them to any of the other software documents used in the system. The versioning services, in particular, show developers the context of the design discussions, making those discussion comprehensible even in systems whose components have changed considerably over time.