Add to ORKGDesign Rationale consists of the reasons behind decisions made while designing. This information would be particularly useful during software maintenance. In this paper, we describe a study performed to investigate the content, structure, and use of design rationale during maintenance. The major goal of this study was to discover an agenda for further research into the use of design rationale for software maintenance
Most large systems development efforts proceed in a top-down fashion where initial specifications an...
Design Rationale (DR) consists of the decisions made during the design process and the reasons behin...
proven difficult in the absence of design information [19]; maintainers often spend considerable ene...
The Problem For a number of years, members of the Artificial Intelligence (AI) in Design community h...
peer-reviewedSoftware maintenance is widely known as a problematic area that may consume up to 80% o...
Software maintenance is widely known as a problematic area that may consume up to 80% of a software ...
For a number of years, members of the Artificial Intelligence (AI) in Design community have studied ...
In every software engineering project, large number of decisions is taken over an extended period of...
In every software engineering project, large number of decisions is taken over an extended period of...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
Design rationale in software engineering fills in the gaps between the original requirements of a sy...
Abstract. Design Rationale (DR), the reasons behind decisions made while designing, offers a richer ...
Most large systems development efforts proceed in a top-down fashion where initial specifications an...
Design Rationale (DR) consists of the decisions made during the design process and the reasons behin...
proven difficult in the absence of design information [19]; maintainers often spend considerable ene...
The Problem For a number of years, members of the Artificial Intelligence (AI) in Design community h...
peer-reviewedSoftware maintenance is widely known as a problematic area that may consume up to 80% o...
Software maintenance is widely known as a problematic area that may consume up to 80% of a software ...
For a number of years, members of the Artificial Intelligence (AI) in Design community have studied ...
In every software engineering project, large number of decisions is taken over an extended period of...
In every software engineering project, large number of decisions is taken over an extended period of...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
A complete and detailed (full) Design Rationale Documentation (DRD) could support many software deve...
Design rationale in software engineering fills in the gaps between the original requirements of a sy...
Abstract. Design Rationale (DR), the reasons behind decisions made while designing, offers a richer ...
Most large systems development efforts proceed in a top-down fashion where initial specifications an...
Design Rationale (DR) consists of the decisions made during the design process and the reasons behin...
proven difficult in the absence of design information [19]; maintainers often spend considerable ene...