Capability Pattern: Build by Feature | |
 |
A per-feature activity to produce a completed client-valued function (feature). |
|
Relationships
Description
Starting with the design package, the development class owners implement the items necessary for their class to support the
design for this feature. The code developed is then unit tested and code inspected - the order of which is determined by
the Chief Programmer. After a successful code inspection, the code is promoted to the Build. |
Properties
Event-Driven |  |
Multiple Occurrences |  |
Ongoing |  |
Optional |  |
Planned |  |
Repeatable |  |
Key Considerations
Entry Criteria:
-
The Design by Feature process has completed. That is, the design package has successfully been inspected.
Exit Criteria:
The result of the process is
-
Class(es) and/or method(s) that have been successfully code inspected.
-
Class(es) that have been promoted to the build.
-
The completion of a client-valued function (feature)
|
|