How Waterfall Deals with Software Requirements

Revision as of 16:08, 28 May 2018 by Rasimsen (talk | contribs) (Created page with "Waterfall projects define all software requirements upfront. The project cannot proceed unless these requirements have been identified and documented. Some Waterfall projects...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Waterfall projects define all software requirements upfront. The project cannot proceed unless these requirements have been identified and documented.

Some Waterfall projects may have a dedicated team to capture, collect, and gather these requirements. They may use questionnaires, face-to-face or phone interviews, white boards, and modeling tools to capture stakeholder and customer requirements.

Once the initial requirements are defined, the team should produce a requirements specification document (sometimes they may create more than one). This document defines what needs to be delivered so everyone understands the scope of the project.