Requirements, architectures and risks

Author

Kozaczynski, Wojtek

Author_Institution

Rational Software, USA

fYear

2002

fDate

2002

Firstpage

6

Lastpage

7

Abstract

Modern software development processes, like the Rational Unified Process, prescribe an iterative approach to software development. A fundamental assumption of an iterative process is that system requirements don\´t have to be completely understood to commence development. At first glance the assumption that one can start developing a system without completely understanding its requirements seems paradoxical. However, upon closer inspection requirements can be divided into many categories, one of them being "architecturally-significant requirements". It is the understanding of these requirements, the associated development risks, and the system architecture that drive the early iterations of system development.

Keywords

formal specification; risk management; software architecture; software prototyping; systems analysis; Rational Unified Process; architecturally significant requirements; development risks; iterative software development; software development processes; system architecture; system requirements; Computer architecture; Contracts; Design engineering; Inspection; Iterative methods; Programming; Reliability engineering; Shape; Software development management; Usability;

fLanguage

English

Publisher

ieee

Conference_Titel

Requirements Engineering, 2002. Proceedings. IEEE Joint International Conference on

ISSN

1090-705X

Print_ISBN

0-7695-1465-0

Type

conf

DOI

10.1109/ICRE.2002.1048499

Filename

1048499