A Rationale-based Model for Architecture Design Reasoning
A Rationale-based Model for Architecture Design Reasoning
A Rationale-based Model for Architecture Design Reasoning
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
BIBLIOGRAPHY<br />
[24] E. Conklin and B.-Y. K.C., “A Process-Oriented Approach to <strong>Design</strong> <strong>Rationale</strong>,”<br />
in <strong>Design</strong> <strong>Rationale</strong>: Concepts, Techniques and Use, T. Moran and J. Carroll, Eds.<br />
Lawrence Erlbaum Associates, 1996, ch. 14, pp. 393–427.<br />
[25] J. Conklin, “<strong>Design</strong> <strong>Rationale</strong> and Maintainability,” in Proceedings of the 22nd International<br />
Conference on System Sciences, 1989, pp. 533–539.<br />
[26] J. Conklin and M. Begeman, “gIBIS: A hypertext tool <strong>for</strong> exploratory policy discussion,”<br />
in Proceedings ACM Conference on Computer-Supported Cooperative Work,<br />
1988, pp. 140–152.<br />
[27] B. Curtis, H. Krasner, and N. Iscoe, “A field study of the software design process<br />
<strong>for</strong> large systems.” Commun. ACM, vol. 31, no. 11, pp. 1268–1287, 1988.<br />
[28] A. Dardenne, A. Van-Lamsweerde, and S. Fickas, “Goal-directed Requirements Acquisition,”<br />
Science of Computer Programming, vol. 20, pp. 1–36, 1993.<br />
[29] M. Den<strong>for</strong>d, J. Leaney, and T. O’Neill, “Non-Functional Refinement of Computer<br />
Based Systems <strong>Architecture</strong>,” in The 11th IEEE International Conference and<br />
Workshop on the Engineering of Computer-Based Systems, 2004, pp. 168–177.<br />
[30] R. Dijkman, D. A. Quartel, L. F. Pires, and M. J. van Sinderen, “A Rigorous<br />
Approach to Relate Enterprise and Computational Viewpoints,” in Proceedings 8th<br />
IEEE International Enterprise Distributed Object Computing Conference (EDOC),<br />
2004.<br />
[31] DoD, “Department of Defense <strong>Architecture</strong> Framework version 1.0 - Volumn<br />
1 definition and guideline and Volumn 2 product descriptions,”<br />
http://www.aitcnet.org/dodfw, 2003, last accessed: April 1, 2004.<br />
[32] R. Domges and K. Pohl, “Adapting traceability environments to project-specific<br />
needs,” Communications of the ACM, vol. 41, no. 12, pp. 54–62, 1998.<br />
[33] A. Dutoit and B. Paech, “<strong>Rationale</strong> Management in Software Engineering,” in Handbook<br />
of Software Engineering and Knowledge, Nov. 30 2000.<br />
[34] A. H. Dutoit and B. Paech, “<strong>Rationale</strong>-Based Use Case Specification,” Requirements<br />
Engineering, vol. 7, no. 1, pp. 3–19, 2002.<br />
[35] T. Dyba, B. Kitchenham, and M. Jorgensen, “Evidence-<strong>based</strong> software engineering<br />
<strong>for</strong> practitioners,” IEEE Software, vol. 22, no. 1, pp. 58–65, 2005.<br />
[36] T. Dybå, “An instrument <strong>for</strong> measuring the key factors of success in software process<br />
improvement.” Empirical Software Engineering, vol. 5, no. 4, pp. 357–390, 2000.<br />
215