Many developers and customers like to focus on design and the end product and often place a lower priority on requirements. The outcome of that approach could lead to missed requirements and a partially useable system. A good systems analyst will be skillful in placing high priority on the requirements definition phase. The analyst may have to obtain stakeholder agreement to do so as it is important to understand what the customer specifics are as it relates to requirements.

How are requirements specified?

What do you believe are the benefits of modeling requirements?

What are two methods you would use to ensure quality requirements are documented?