Requirements Engineering

Requirements Engineering

The process of establishing a service a customer requires of a system and constraints in which the system operates and is developed under.

Requirements

System Services and Constraints developed during the Requirements Engineering Process.

User Requirements

A Natural Language + Diagrams of system services and operational constraints(non-functional requirements).

System Requirements

A structured document setting out detailed descriptions of the system's functions, services and operational constraints. Defines what should be implemented so may be part of a contract between client and contractor.

Functional Requirements

Statements of services the system should provide, how system should react(provoked action) and behave(intrinsic action) in particular situations.

Non-Functional Requirements

Constraints on the services or functions offered by the system(ex: timing constraints, development process constraints, standards, operating system, etc..)

Domain Requirements

Constraints that arise for the system by result of the domain of operation(Ex: Medical , Military, Aircraft, etc..)

Functional User Requirements

High Level statements of the systems intended services and behaviors(Note: user friendly for customer to understand)(Note: services: user observable, behaviors: actions of a situation)(Ex: user can withdraw money)

Functional System Requirements

Describes the system services in detail on what they actually due rather than abstraction(Ex: if user withdraws money -> request pin -> verify -> etc..)

Process Requirements

Constraints or rules that are followed while developing(process) system.

Non-Functional Product Requirements

Constraints which developed product must withhold(think system traits: speed, reliability, etc..)

Non-Functional Organizational Requirements

Constraints on system or development process that arise from company police(Think: house rules)

Non-Functional External Requirements

Constraints on system or development process that arise from external police(legislative regulation, interoperability(OS), Market Expectations)

Requirement Elicitation

Requirement Gathering via Stakeholders

Requirement Analyzation

Analyzing and Prioritizing Requirements that were gathered during [ELICITATION STAGE]

Requirement Specification

Documenting Prioritized Requirements in a detailed manner

Requirements Document

Contains user and system requirements

Requirement Validation

Concerned with demonstrating requirements satisfy customers system needs, Verifiability, Comprehensibility, Traceability, Adaptability

Requirement Change

Actual Modification of Requirement or change

Requirement Management

Deals with the ongoing process of managing requirements, updating, changing, and making sure it preserves requirement Identification(uniqueness), Impact and Costs of Requirements, Traceability(Relationships of Requirements), Tool Support(Tools used to help manage the on going requirement changes).

SWOT Analysis

Used to help asses Strengths and Weaknesses(internal to organization) as well as Opportunites and Threats(external to organization) to benefit the organization