Skip to content

Latest commit

 

History

History
68 lines (49 loc) · 1.71 KB

Requirements Engineering.md

File metadata and controls

68 lines (49 loc) · 1.71 KB

#csse3012

Requirements Engineering

Requirements are rarely right at the start "Embrace Change" - Agile

[[Requirements Engineering Process]] [[Business Model Canvas]]

meta

[[Building Complex Systems]]

What is Requirements Engineering

![[Requirements Engineering_2022-03-23 15.23.45.excalidraw]]

[[Why is RE important]]

[[Difference between average, poor, and best software (RE)]] [[What happens if requirements are wrong]] [[Benefits of good requirements]]

Most faults observed in a software project are from incorrect, incomplete, or misinterpreted functional specifications or requirements. - Glass’ Law

Sound basis for resource estimation

  • Earlier detection of mistakes
  • Forces review
  • Enhances communications
  • Record and refine

What is a requirement

  1. A condition or capability needed by a user to solve a problem or achieve an objective
  2. A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed document
  3. A documented representation of a condition or capability as in 1 or 2

![[Requirements Engineering_2022-03-23 15.26.54.excalidraw]]

What documents are included in the requirement (RS)

Primary - Agreement between client and developer Secondary - System or software acceptance test criteria

Types

[[Functional Requirements]] [[Non-Functional Requirements]]

[[Sources Of Requirements]]

[[Requirements Engineering Process|Process]]

[[Who does requirements engineering|Who does it]]?

Resources

[[Week 02a1 - Requirements Engineering.pdf]]

Next

  • [[Business Model Canvas]]
  • [[Project initiation (Tutorial)]]