Checklist: Implementation

Display viewsDisplay views
Expand All SectionsExpand All Sections    Collapse All SectionsCollapse All Sections
CollapseRelationships  
Related Elements
Back to topBack to top
CollapseMain Description  

Appropriate divergence from the quality criteria described here could be worthy of a comment in the implementation so that developers examining the code in the future know why the exception occurred.

Back to topBack to top
CollapseCheck Items  
Expand All Check ItemsExpand All Check Items Collapse All Check ItemsCollapse All Check Items
ExpandThe implementation conforms to the architecture and design  
  • Is the implementation structured as specified in the design?
  • Are all of the functions in the design implemented?
  • Are all of the interfaces in the design implemented according to their specifications?
  • Does the implementation adhere to all design and architectural constraints?
ExpandThe implementation is testable  
  • Can you test the expected behavior at the unit level?
  • Is the code written in a way that all paths can be exercised?
ExpandThe implementation is correct  
  • Does the implementation pass all of the developer tests?
  • Does the implementation support the acceptance criteria of the test cases?
  • Is all code executable (no dead code areas)?
ExpandThe implementation is understandable  

Is the logic clearly specified?  Have comments been used sparingly to add clarity, and not to make up for unclear code?

ExpandThere is no redundancy  

Is there no redundancy in the implementation? (Identify candidates for refactoring.)

Back to topBack to top

This program and the accompanying materials are made available under the
Eclipse Public License V1.0, which accompanies this distribution.

EPF Copyright.