Code and Unit Test

Purpose:

Enable Projects to implement the agreed system design by coding as per standards and configuring the implemented system to the software and hardware as given in Standards Bill of Maternal.
 
Development team develops the code and unit tests for implementing the system.
 
When outsourcing, the supplier takes the complete responsibility to code, implement, conduct unit tests, configure and integrate the system at the Supplier’s location before delivering to the organization.

Objective:

Code and Unit Test Procedure involves implementing the system as per the agreed design by ensuring that effective methods and standard programming guidelines are followed. This procedure also expects the source code be unit tested and identified bugs have been resolved and issues before the system is integrated and configured for the defined hardware and software.

Description:

Development Team or Supplier(s) shall develop the Source Code and conduct unit testing of the code.
 
The Project Manager shall conduct regular progress reviews to ensure that the project is on schedule by tracking the project schedule, risks, constraints and dependencies.

Inputs:

  • Customer Requirements
  • Product Requirements
  • System Design Document
  • Requirements Traceability Matrix
  • <?>

Outputs:

  • Updated Requirements Traceability Matrix with references to Unit Test Cases and Integration Test Cases
  • Delver system packaged with unit tested source code, Unit Test Cases, Build Procedures and updated RTM.

Controls:

<?>

Task Instructions:

Develop Source Code and Conduct Unit Testing

    1. The Project Manager and Supplier(s) shall ensure that the Development Team and Supplier(s) development team has studied and understood the Customer and Product Requirements, and System Design Document before starting to code.
    2. Development Team and Supplier(s) shall code and/or configure the system.
    3. The Development Team or Supplier(s) shall ensure that the software adheres to the organizational Standards and the agreed system design. The coding standards include:
      • Programming language standards
      • Naming conventions for files, components and variables
      • Code and comment format
    4. The software components shall be assigned unique names to ensure that they can be identified and traced to requirements.
    5. The Development Team or Supplier(s) shall identify and reuse software code as agreed with the Project Manager.
    6. Development Team or Supplier(s)shall conduct Unit Tests on the software modules. Developing and unit testing the code is a cyclical process and involves the following steps:
      • Code – Develop the code as per the design
      • Unit Test –Test the developed unit independently
    7. The cycle shall be continued until the developed code satisfies the unit testing pass criteria and all paths are covered through testing. The Development Team or Supplier(s) shall ensure that new problems are not introduced while fixing problems identified during the previous cycle of testing.
It is expected that the Development Team or Supplier(s) conducts code review to identify and detect defects early in the life cycle, which reduces maintenance and support costs of the system. The reviews shall ensure that the code is complaint to the coding standards, the design document, and that code compiles without compiler errors.
Develop Integration Test Cases
    1. Development Team or Supplier(s) shall develop the Integration Test Cases for the developed code.
    2. Each test case shall be assigned a unique ID and shall be documented. The required test stubs and test drivers shall be developed as necessary to test the sequence of the system integration and development.

Update Requirements Traceability Matrix

    1. Development Team or Supplier(s) shall update the Requirements Traceability Matrix (RTM) to provide bi-directional traceability by tracing the test cases, test stubs, and test drivers to the design and code components.

Peer Review

    1. The Development Team or Supplier(s) shall ensure that the code and test cases are reviewed before using the same.
  1.