@inbook {sa:2023:education,
	title = {A Better Way to Teach Software Architecture},
	year = {2023},
	pages = {101 - 110},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Software architecture education is a weak spot in many undergraduate programs in computer science and software engineering. While the concepts and practices used by software architects in industry are rich and varied, transferring this expertise into a university classroom has proved problematic. Bridging the gap between industry and academia requires ongoing, often heroic, effort. This is a {\textquotedblleft}chicken and egg{\textquotedblright} problem: Because there is a lack of good teaching materials, architecture is seldom taught, and because it is seldom taught, there has been little incentive to create good materials. We would like to change that. Our goal is to establish guidelines for how software architecture practices should be taught{\textemdash}both technical and non-technical topics{\textemdash}and to suggest appropriate teaching methods to best prepare students to be software architects in practice.},
	keywords = {software architecture},
	isbn = {978-3-031-36846-2},
	doi = {10.1007/978-3-031-36847-9_6},
	url = {https://link.springer.com/10.1007/978-3-031-36847-9_6},
	author = {Kazman, Rick and Cai, Yuanfang and Godfrey, Michael W. and Cesare Pautasso and Liu, Anna},
	editor = {Pelliccione, Patrizio and Kazman, Rick and Weber, Ingo and Liu, Anna}
}
@inbook {sa:2023:empirical,
	title = {An Empirical Basis for Software Architecture Research},
	booktitle = { Software Architecture - Research Roadmaps from the Community },
	year = {2023},
	pages = {87 - 100},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Despite the clear need for and importance of performing empirical studies as part of software architecture research, there is still a lack of curated, standardized, clean, well-maintained, documented, easily accessible, reusable, and shared datasets. In this chapter, we provide an overview of the problems, of the motivations, and of the opportunities currently related to mining and sharing datasets for researchers in software architecture. We first explore and describe which artifacts should be included into such datasets, such as code, documentation, and requirements, but also including other architecturally relevant artifacts, such as architectural decision records, models, and other kinds of documentation. This information can be complemented with revision history logs, social metadata, and email or chat discussion archives. The availability of such datasets would enable not only architectural reconstruction studies but would also help to catalyze broader and more ambitious program of empirical studies in software architecture research.},
	keywords = {software architecture},
	isbn = {978-3-031-36846-2},
	doi = {10.1007/978-3-031-36847-9_5},
	url = {https://link.springer.com/chapter/10.1007/978-3-031-36847-9_5},
	author = {Rick Kazman and Roberto Tonelli and Cesare Pautasso},
	editor = {Pelliccione, Patrizio and Kazman, Rick and Weber, Ingo and Liu, Anna}
}
