Transitioning from Requirements to Design

  • Paul Reed President
  • Published 2002


Most team members seem to realize the benefits of making a correct decision as well as the downside of making an incorrect one. Leap too early, and the project runs the risk of formulating a design based on sketchy requirements. Leap too late, and you take on more risk by postponing highrisk architecture decisions until later in the project lifecycle. In addition, when preparing the artifacts to transition from requirements to design, you must take care not to lose the context in which they were originally captured (e.g., Who made the decisions? Were there unique relationships between certain requirements?).

3 Figures and Tables

Cite this paper

@inproceedings{President2002TransitioningFR, title={Transitioning from Requirements to Design}, author={Paul Reed President}, year={2002} }