L. Bratthall, E. Johansson, and B. Regnell, "Is a design rationale vital when predicting change impact? a controlled experiment on software architecture evolution," in Second International Conference on Product Focused Software Process Improvement (PROFES), ser. LNCS, vol. 1840. Springer, 2000, pp. 126--139. [Online]. Available: citeseer.nj.nec.com/bratthall00is.html Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Capturing Communication and Context in the Software Project.. - Zaychik, Regli (2002) (Correct)
....and evolution of software. The term most widely used in the research literature to describe these concepts is Design Rationale (DR) Documenting DR during the design process has been shown to be a vital approach to improved correctness and speed in both the Engineering[4] and the Software[3] domains. In areas which mainly use ad hoc tools, such as open source projects, the need is felt most strongly: although mailing lists of communications between developers are archived and available online, the lack 5 For submission to Research in Engineering Design. of structure of these ....
Lars Bratthall, Enrico Johansson, and Bjorn Regnell. Is a design rationale vital when predicting change impact? - a controlled experiment on software architecture evolution. In Proceedings of PROFES'00: 2nd International Conference on Product Focused Software Process Improvement, Oulu, Finland, June 20-22 2000.
Rationale Management in Software Engineering - Dutoit, Paech (2000) (Correct)
....engineering project course using a similar approach for status meeting [14] 4. 4 Predicting Change Impact By capturing the justification of the current design, maintainers have better and more information on which to base when designing changes hence avoiding the problem of architectural erosion [5]. However, designers usually dislike making Issue Proposal Argument Resolution addresses resolves supports based on Minutes Agenda opposes Action Item 18 Handbook of Software Engineering and Knowledge Engineering additional documentation. Also, all expansions of the software ....
....Issue Proposal Argument Resolution addresses resolves supports based on Minutes Agenda opposes Action Item 18 Handbook of Software Engineering and Knowledge Engineering additional documentation. Also, all expansions of the software development process may affect lead time negatively. [5] proposes a simple approach for documenting design rationale which was used to set up a controlled experiment to study effectiveness of rationale. Identification and acquisition. Designers write down a note for each system aggregation level documenting why it is broken down into the lower ....
L. Bratthall, E. Johansson & B. Regnel, Is a Design Rationale Vital when Predicting Change Impact?A Controlled Experiment on Software Architecture Evolution, InInt. Conf. on Product Focused Software Process Improvement, LNCS 1840, 2000
Evaluation of Tool Support for - Architectural Evolution Anton (2004) (Correct)
No context found.
L. Bratthall, E. Johansson, and B. Regnell, "Is a design rationale vital when predicting change impact? a controlled experiment on software architecture evolution," in Second International Conference on Product Focused Software Process Improvement (PROFES), ser. LNCS, vol. 1840. Springer, 2000, pp. 126--139. [Online]. Available: citeseer.nj.nec.com/bratthall00is.html
Using Development History Sticky Notes to Understand Software.. - Hassan, Holt (2004) (Correct)
No context found.
L. Bratthall, E. Johansson, and B. Regnell. Is a design rationale vital when predicting change impact? a controlled experiment on software architecture evolution. In Proceedings of the International Conference on Product Focused Software Process Improvement, Oulu, Finland, 2000.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC