Architectural Requirements Engineering: Theory vs. Practice

Abstract

This paper discusses how architectural requirements engineering fits into an overall software development process in the concept and definition phases of a project. It defines a reference process identifying the “ideal” artifacts and their interrelationships, describes some key technical activities that are useful for producing these artifacts, and captures some practical experience in commercial projects.

1 Figure or Table

Cite this paper

@inproceedings{Schwanke2003ArchitecturalRE, title={Architectural Requirements Engineering: Theory vs. Practice}, author={Robert W. Schwanke}, booktitle={STRAW}, year={2003} }