A practical authoring sequence that uses the model as intended.
From feature idea to review
Recommended sequence
- 1 Create or open a project and choose a short key prefix for generated feature keys.
- 2 Build the parent-child feature hierarchy and order siblings to match the architecture.
- 3 Write feature intent, assign an owner and priority, and capture dependencies and open questions.
- 4 Add requirements as small testable statements and mark their functional, performance, safety, or interface type.
- 5 Document architecture, interfaces, expected behavior, reset/error behavior, and performance constraints.
- 6 Describe the verification strategy, assertions, coverage, exclusions, and concrete scenarios.
- 7 Link each scenario to the requirements it verifies and resolve validation findings before review.
Independent stage status
Specification, design, and DV each use not-started, draft, in-review, approved, in-progress, complete, or blocked. A feature can therefore show that specification review is complete while design or DV planning is still underway.
Scenario methods
| Method | Use |
|---|---|
| Simulation | Dynamic tests, scoreboards, protocol stimulus, and coverage. |
| Formal | Property proof or bounded exploration. |
| Emulation | Long-running or software-driven scenarios on acceleration platforms. |
| Inspection | Review evidence that is not produced by an executable test. |