A Rationale-based Model for Architecture Design Reasoning
A Rationale-based Model for Architecture Design Reasoning
A Rationale-based Model for Architecture Design Reasoning
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
BIBLIOGRAPHY<br />
[10] B. W. Boehm, Software Engineering Economics. New Jersey: Prentice Hall PTR,<br />
1981.<br />
[11] J. Bosch, “Software <strong>Architecture</strong>: The Next Step,” in Proceedings 1st European<br />
Workshop on Software <strong>Architecture</strong> (EWSA), St Andrews, UK., 2004, pp. 194–199.<br />
[12] L. Bratthall, E. Johansson, and B. Regnell, “Is a <strong>Design</strong> <strong>Rationale</strong> Vital when<br />
Predicting Change Impact? A Controlled Experiment on Software <strong>Architecture</strong><br />
Evolution,” in Second International Conference on Product Focused Software Process<br />
Improvement, 2000, pp. 126–139.<br />
[13] S. Buckingham Shum and N. Hammond, “Argumentation-Based <strong>Design</strong> <strong>Rationale</strong>:<br />
What Use at What Cost?” International Journal of Human-Computer Studies,<br />
vol. 40, no. 4, pp. 603–652, 1994.<br />
[14] J. Burge, “Software Engineering Using design RATionale,” Ph.D. dissertation,<br />
Worcester Polytechnic Institute, 2005.<br />
[15] S. Bushell, “It is the Business, Stupid.” http :<br />
//www.cio.com.au/index.php/id; 719608738; pp; 1; fp; 16; fpid; 0, 2006.<br />
[16] Carnegie Mellon Software Engineering Institute, “CMMI SE/SW Version 1.1,”<br />
http://www.sei.cmu.edu/cmmi/models/model-components-word.html, 2002.<br />
[17] Carrington, K. and Pratt, A., “How Far Have We Come? Gender Disparities in the<br />
Australian Higher Education System,” 2003.<br />
[18] J. Carroll and M. Rosson, “Deliberated Evolution: Stalking the View Matcher in<br />
<strong>Design</strong> Space,” in <strong>Design</strong> <strong>Rationale</strong>: Concepts, Techniques and Use, T. Moran and<br />
J. Carroll, Eds. Lawrence Erlbaum Associates, 1996, ch. 4, pp. 107–146.<br />
[19] R. Charette, Software Engineering Risk Analysis and Management. New York:<br />
McGraw-Hill Book Company, 1989.<br />
[20] L. Chung, B. Nixon, E. Yu, and J. Mylopoulos, Non-functional requirements in<br />
software engineering. Boston: Kluwer Academic, 2000.<br />
[21] CIO-Council, “Federal Enterprise <strong>Architecture</strong> Framework version 1.1,”<br />
http://www.cio.gov/archive/fedarch1.pdf, 1999, last accessed: May 21, 2004.<br />
[22] ——, “A Practical Guide to Federal Enterprise <strong>Architecture</strong> version 1.0,”<br />
http://www.cio.gov/archive/bpeaguide.pdf, 2001, last accessed: May 21, 2004.<br />
[23] P. Clements, F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and<br />
J. Staf<strong>for</strong>d, Documenting Software <strong>Architecture</strong>s : Views and Beyond, 1st ed. Addison<br />
Wesley, 2002.<br />
214