Teaching architectural design in an undergraduate software engineering curriculum

@inproceedings{citeulike:2099879, abstract = {In the fall of 1996, the Rochester Institute of Technology (USA) began admitting students to the nations first baccalaureate program in software engineering. One of the curriculum's primacy themes is software design, ranging from the very concrete (e.g., code, data structures and algorithms) to the more abstract (e.g., subsystems, architectural designs). At each of these levels the authors are able to address the variety of software quality issues that arise at different points in the software development process. This paper describes the structure of their introductory course in software architectures and their experience teaching it. They also speculate on how the course could evolve over time}, author = {Naveda, J. F. }, booktitle = {Frontiers in Education Conference, 1999. FIE '99. 29th Annual}, citeulike-article-id = {2099879}, journal = {Frontiers in Education Conference, 1999. FIE '99. 29th Annual}, keywords = {architecture, design, education, software, software-architecture, software-engineering}, pages = {12B1/1--12B1/4 vol.2}, posted-at = {2007-12-12 18:12:17}, priority = {0}, title = {Teaching architectural design in an undergraduate software engineering curriculum}, url = {http://ieeexplore.ieee.org/xpls/abs\_all.jsp?arnumber=841562}, volume = {2}, year = {1999} }

TY - CONF ID - citeulike:2099879 L3 - citeulike-article-id:2099879 TI - Teaching architectural design in an undergraduate software engineering curriculum T2 - Frontiers in Education Conference, 1999. FIE '99. 29th Annual JF - Frontiers in Education Conference, 1999. FIE '99. 29th Annual VL - 2 SP - 12B1/1 EP - 12B1/4 vol.2 N2 - In the fall of 1996, the Rochester Institute of Technology (USA) began admitting students to the nations first baccalaureate program in software engineering. One of the curriculum's primacy themes is software design, ranging from the very concrete (e.g., code, data structures and algorithms) to the more abstract (e.g., subsystems, architectural designs). At each of these levels the authors are able to address the variety of software quality issues that arise at different points in the software development process. This paper describes the structure of their introductory course in software architectures and their experience teaching it. They also speculate on how the course could evolve over time KW - architecture KW - design KW - education KW - software KW - software-architecture KW - software-engineering AU - Naveda, JF PY - 1999/// UR - http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=841562 ER -