The role of software architecture in requirements engineering

Author

Shekaran, Chandra ; Garlan, David ; Jackson, Michael ; Mead, Nancy R. ; Potts, Colin ; Reubenstein, Howard B.

Author_Institution

GTE Labs. Inc., Waltham, MA, USA

fYear

1994

fDate

18-22 Apr 1994

Firstpage

239

Lastpage

245

Abstract

The role of software architecture (which reflects high-level implementation constraints) in requirements engineering is clarified by providing perspectives on relevant issues, including the following: is requirements engineering merely a front end to the software development process that is concerned only with problem definition? Is software architecture an application-specific, high-level design of a system (for example, “an object-oriented system with a specified object hierarchy”)? What is the relationship between the problem definition and the solution structure? What is the relationship between the roles of requirements engineer, software architect, and application domain specialist?

Keywords

formal specification; professional aspects; systems analysis; application domain specialist; application-specific high-level design; high-level implementation constraints; problem definition; requirements engineer; requirements engineering; software architect; software architecture; software development process; solution structure; Computer architecture; Computer industry; Laboratories; Performance analysis; Programming; Reliability engineering; Shape; Software architecture; Software engineering; Software systems;

fLanguage

English

Publisher

ieee

Conference_Titel

Requirements Engineering, 1994., Proceedings of the First International Conference on

Conference_Location

Colorado Springs, CO

Print_ISBN

0-8186-5480-5

Type

conf

DOI

10.1109/ICRE.1994.292379

Filename

292379