Skip to content
Astera Technology

Separate an optional record from its required fields

Model existence and internal completeness as different conditions.

Compare the rule with concrete cases

Fictional project may have no supplementary note. If a note is created, both subject and author are required. A missing note is valid; an existing empty note is invalid. “Note optional” alone cannot specify the fields of an existing note.

Filled synthetic modelling cases
ProjectChild noteSubject / authorValidity
R1AbsentNot applicableValid
R2PresentPresent / presentValid
R3PresentPresent / absentInvalid
Download editable CSV ↓

Work through the distinction

A child-existence decision is not a field-default decision. Automatically creating an empty note would turn a valid project into an invalid one under this model.

The project has no note. Must software invent an author to complete it?

Show the worked answer

No. No note is allowed. Only an existing note needs its actual subject and author.

Acceptance wording to adapt

Permit a project with zero supplementary notes. When a supplementary note exists, reject saving that note if its subject or author is missing. Do not create a placeholder note automatically.

Related resources

Custom software development →