01 Definitions

Terminology

created by the customer as basis of discussion
defines what must be delivered
- Functions
- Quantities
- Quality (clear and understandable)
- Constraints
basis for discussion and potential implementation
reference document
- contractual binding if accepted and signed by both sides
- crucial if the supplier fulfilled the agreement
- whether the payment is due, in case of disputes or acceptance testing
Only this document is reference is no others are explizit listed

Category	English Term	Purpose / Content	Contractual Status	Examples
Contractual Baseline	Requirements Specification / Statement of Work (SoW)	Defines what must be delivered and accepted.	Binding when referenced or signed.	Customer Requirements Spec, Lastenheft, SoW, Contract Appendices
Technical Documents	Technical Specification / System Design Specification	Describes how requirements will be met.	Binding only if approved or referenced.	Design Spec, Pflichtenheft, Implementation Plan
Clarification Documents	Supplier’s Comments on Requirements / Clarification Report	Capture supplier feedback or open points before approval.	Informative, may become binding after agreement.	Lastenheft-Stellungnahme, Review Notes
Supporting Documents	Presentations / Meeting Notes / PDFs / Emails	Support communication and understanding.	Not binding unless formally included.	PowerPoints, Workshop Notes, Emails
Change Records	Change Request (CR) / Engineering Change Notice (ECN)	Document approved changes to the agreed scope.	Binding once approved and integrated.	Change Log, Updated Requirements

“Something the customer wants from us”

A condition that must be satisfied for the output of a work effort to be acceptable
explicit, objective, clear and often quantitative description

“Something we are planning to give to the customer”

We distinguish three complementary views on the remaining effort:

Remaining budget (d) = planned (d) – actual (d) → How many days of the original budget are still available. Can become negative if the budget is exceeded.
Remaining effort (plan) (d) = planned (d) × (1 – progress) → How many days should be left according to the original plan and reported progress.
Remaining effort (forecast) (d) = (actual (d) / progress) – actual (d) → Estimated remaining effort based on current efficiency (extrapolation of actual performance).

These values provide insight into budget consumption (remaining budget), plan status (plan), and expected outcome (forecast).