The first step in the requirements workflow is the analysis phase, where the developer determines what kind of software needs to be developed. The next, and the most important step, is the requirements phase, where the developer defines and documents the software products that the users require. This is usually done in collaboration with the end-users and domain experts, and it is critical that all stakeholders involved establish a common understanding of the domain under study. Once the requirements are defined, they are formally specified in the form of a legal document. Typically, this document includes functional requirements, performance requirements, interface requirements, design requirements, and development standards. As a result, this document must eliminate all ambiguous, incomplete, and contradictory statements. Since this is not an easy task, many methodologies recommend using a modeling approach (e.g., the Rational Unified Process (RUP) recommends using Unified Modeling Language (UML) use cases and class diagrams). Other researchers recommend using a more formal approach that provides a precise specification of the requirements agreed upon by all stakeholders (e.g., Petri nets - see Jorgensen and Bossen [2004]).
When you complete this unit, you will be able to
Updated September 29 2016 by FST Course Production Staff