A targeted review of an in-progress software effort to identify important gaps in engineering discipline, traceability, verification support, documentation, and process alignment before those weaknesses become significantly more expensive to correct.
In safety-critical and regulated software development, visible progress can conceal important weaknesses in how the effort is being engineered. Traceability may be incomplete, documentation may be misaligned with implementation reality, verification support may be thin, or lifecycle practices may exist more as expectations than as consistently applied discipline. These issues often remain tolerable until integration pressure, quality escapes, or formal review begins to expose them.
The Safety-Critical Software Gap Scan is designed to reveal those weaknesses while correction is still practical. It is not a formal audit and does not attempt to produce certification findings. Instead, it provides an experienced external perspective on whether the current effort appears to be developing on a stable and defensible footing.
Half-day scope
A half-day scan is best for a bounded look at one major concern area or a limited sample of project artifacts. This format is intended to identify the most visible or likely weaknesses in a defined slice of the effort and to indicate whether that area appears stable or at risk of accumulating avoidable trouble.
Typical half-day activities may include:
-
Review of a small set of lifecycle artifacts before the session.
-
Discussion of the project’s assurance context and current development approach.
-
Identification of likely gaps in lifecycle discipline, technical documentation, or verification support.
-
Concise observations about where hidden risk may be accumulating.
Half-day price: $2,350
Full-day scope
A full-day scan is better when the project needs a broader review across several dimensions of engineering and process integrity. It allows more substantial artifact review, more complete consideration of how process expectations map to actual project behavior, and more developed guidance on where corrective attention is likely to have the greatest value.
Typical full-day activities may include:
-
Broader review of requirements, plans, architecture materials, verification artifacts, or process documents.
-
Examination of whether current practices appear likely to support defensible development and later review.
-
Identification of higher-risk disconnects between process, implementation, and evidence.
-
More developed recommendations for stabilizing the effort and reducing future rework.
Full-day price: $3,600
This engagement is particularly useful when a team suspects that the project may be drifting out of alignment, but does not yet know where the most consequential weaknesses are.