Software Engineering

Requirement Analysis (RA)

Requirement analysis (RA)

Systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users.

Requirements analysis is critical to the success of a development project.

Requirements must be actionable, measurable, testable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

RA consist of 3 parts

  1. Requirement Gathering: Understand what is the requirement
  2. Analyzing requirement: Recheck if requirement is unclear, incomplete, ambiguous, or contradictory, and then resolving these issues
  3. Recording requirement: Document requirement in the form use cases or prototyping

RA workbook

  1. Identify stakeholders
  2. Interview stakeholders – Understand their requirement or visualize there requirement
  3. Measurable goals – Create goals of what has achieved so far. Once a small set of critical, measured goals been established, rapid prototyping and short iterative development phases may proceed to deliver actual stakeholder value long before the project is half over.
  4. Prototype – They are mock ups of application. This allows users to visualize an application that hasn’t yet been constructed. This helps to prevent confusion over the final visual look and feel of the application.
  5. Use case – Provides one or more scenarios that convey how the system should interact with the end user or another system to achieve a specific business goal. It simply shows the steps that a user follows to perform a task. All the ways that users interact with a system can be described here. Use case is also known as functional requirement.