Implementation

Bread Crumbs: Home - SW_Dev_Proc - Impl
Implementation is the creation of source code from the design artifacts. Implementation involves peer reviewing source code and addressing all review findings. Implementation also requires the use of build tools to create binary files that are executable on the target. Implementation also encompasses unit-testing the source code as it is being developed and fixing defects as they are discovered.

The final output of the implementation phase of the software development process are unit-tested binaries that build without warnings.
Implementation Activity PNG Source code creation should be performed in accordance with the project coding standard. Although the coding activity is sometimes regarded as the most important part of the entire software development process, it is in fact a translation from non-executable design information into executable artifacts, the source code files (via build tools which translate the human-readable source code into machine-readable binary). All source code should be peer reviewed according to a checklist. This includes unit test source code as well (test harness code, test driver code, stub code, etc.). PSP (Personal Software Process) metrics should be recorded to provide data for analysis so that process improvements can be made. When building source code, project toolsets are used and errors are recorded. The errors will be recorded as part of the metrics data collected. Unit tests are structural, white box tests that should attempt to provide maximum execution path coverage including off-nominal (error) paths.

No part of this work should be produced or used without the permission of the authors: Michael Turner and Dr. Sharon A White.