Exit-Conditions are usually found in sets. The relevant set of Exit-Conditions is evaluated in an Exit-Process. They are used to determine if there is Exit permission from a task Process. All the Generic and specific Exit-Conditions must normally be met, in order to Exit from a Process, thus releasing Work products to the other ‘downstream’ Processes.
Exit 33: The remaining Quantity of Major-Defects (potentially costly Rule violations) in a Document may be calculated (based on Defects found and fixed) to determine if it is wise to release (Exit) an Engineering or management specification.
We can decide this by considering the alternative Cost consequences (compared to Exit ‘now’) of the remaining Defects, in later test and field use phases.
At stages later than specification, Major-Defects are one and two orders of magnitude more expensive to deal with.
Exit 13: The System design must arguably have a Complete set of designs to reach all Performance-Targets, within Resource-Targets and Generic-Constraints, considering acceptable Risk (negative uncertainty), Credibility and Safety-Margin.
This Concept entered by Adore.
Table of contents: