Master Requirement Engineering: From Business Analysis to System Acceptance

Outline

Requirement Engineering

Business Process Analysis

Define System Boundary

Functional Requirements

Non‑Functional Requirements

System Acceptance Criteria

Article Summary

1. Requirement Engineering

Basic Process

Requirement engineering consists of five independent stages of requirement acquisition.

Through communication with users, observation of existing systems, and task analysis, user needs are captured, refined, and documented.

Requirement modeling creates a conceptual model that abstracts the system for end users, capturing real‑world semantics.

Requirement specification generates a precise, formal description of the requirement model, serving as a contract between users and developers.

Requirement verification uses the specification as input, applying symbolic execution, simulation, or rapid prototyping to assess correctness and feasibility, including validity, consistency, feasibility, and verifiability checks.

Requirement management supports the evolution of requirements, ensuring shared understanding, controlling changes, and tracking requirements throughout the project.

Architect’s View of Requirements

Clarify system goals to satisfy all stakeholders.

Fully understand requirements, identify core needs, and design architecture around them.

Requirement layering theory: business, user, and system requirements.

Requirement classification theory: basic, extended, and priority requirements.

Requirements are the foundation of architecture; they must be forward‑looking yet avoid over‑design.

Requirement Analysis Methodology

Purpose: Analyze user needs and produce a clear, standardized requirement definition, answering “what to build”.

Requirement Types: Business, user, system, functional, non‑functional (including quality attributes and constraints).

Process: Business goals → business processes → boundary definition → functional requirements → non‑functional requirements → system scope → acceptance criteria.

Tools & Techniques: Context diagrams, use‑case diagrams, activity diagrams, function trees, functional block diagrams, feature lists, surveys, interviews, etc.

Roles Involved: Customers, users, project managers, requirement analysts, architects, domain experts, etc.

Inputs: Business requirements, stakeholder inputs, user needs.

Outputs: Requirement specification document, system prototypes, requirement analysis documentation.

2. Business Process Analysis

3. Define System Boundary

4. Functional Requirements

5. Non‑Functional Requirements

6. System Acceptance Criteria

7. Article Summary