Requirements, Architectures and Risks

Authors:
Wojtek Kozaczynski
Affiliations:
-
Venue:
RE '02 Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering
Year:
2002

Citing 0
Cited 3

Controversy Corner: On the similarity between requirements and architecture

Journal of Systems and Software
VRRM: a value-based requirements' risk management process

SE '08 Proceedings of the IASTED International Conference on Software Engineering
An exploratory study of architectural effects on requirements decisions

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

Modern software development processes, like the Rational Unified Process, prescribe iterative approach to software development. One of the fundamental assumptions of an iterative process is that system requirements don't have to be completely understood tocommence 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 divide into many categories one of them being the "architecturally-significant requirements". It is the understanding of these requirements, the associated development risks, and the system architecture that drive the early iterations ofsystem development.