Gathering and Prioritizing Requirements

Requirements gathering is typically done in groups. It is not recommended that one person define the requirements of a particular part of the system, even if that person is the undisputed authority on the subject. Having varied skill sets in the team is also a plus. In Figure 8-3, the requirements team is responsible for developing most of the requirements artifacts, whereas project management and the architecture team are responsible for prioritizing them.

Figure 8-3. Developing requirements

A requirements team is made up of at least one representative of the user or stakeholder community and a technical ...

Get Building Web Applications with UML Second Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.