Week 2. Requirements analysis, UML, and use case diagrams

 

Stages in requirements analysis

Stages in requirements analysis

There are several stages in requirements analysis:

  1. Domain analysis, requirements elicitation
    • Identify stakeholders
    • Gather information on domain + requirements
    • Talk with users, customers, and other stakeholders
    • Look at literature and other similar systems
  2. Evaluation and negotiation
    • Identify conflicts, imprecision, omissions, redundancies
    • Consult and negotiate with stakeholders to agree resolutions
  3. Specification and negotiation
    • Systematically document requirements as system specification
    • In-precise or potentially formal notation
    • Agreement between developers and stakeholders on what will be developed
  4. Validation and verification
    • Check formalised requirements for consistency, completeness and correctness
Link to original

Requirement

A requirement can range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification.

Link to original

User requirement

A user requirement is a statement in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers.

Link to original

System Requirements

The system requirements are a structured document setting out detailed descriptions of the system’s functions, services and operational constraints. It defines what should be implemented so may be part of a contract between the client and contractor.

Link to original

Functional requirement

A functional requirement is what the system should do, it is a series of statements of the services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations.

Link to original

Non-functional requirement

A non-functional requirement is how the system should do it. (refers to performance, usability, extensibility and related) It includes constraints on the services or functions provided by the system.

Link to original

UML 2.0