REVISION HISTORY

S. Version / Date of Revised Sections Remarks

No. Revision no. release
1. Release No. 2 07/08/98 • Entry criteria is
added for Unit
,Integration ,System
testing.
• Tasks are modified
for System testing.
2. Release No. 3 30/10/98 • Validation criteria is
added.
• Template is
removed.
• Inputs are modified
for System testing .
• Tasks are modified
for System testing.
• Exit criteria is
modified
3. Release No. 4 01-02-01 • Responsibilities of
QA/Development
team defined for
Quick release SDLC
4. Release No. 5 24 Oct 2002 • Step for Defect
Logging & Test
Result Preparation
added under Unit &
Int Testing.
Rev No. 2.0 Header not to be changed 02-01

CODING AND TESTING: This process can further be divided in the

following three sub processes.

1. CODING AND UNIT TESTING

PURPOSE To implement the software design and

prove that the modules created fulfill the
functionality of their design.

ENTRY CRITERIA Approved Internal / Functional Specification.

INPUTS Internal / Functional Specification.

TEAM Development Team.

USERS QA

TASKS Following tasks to be done:

1. Identify and set the development
environment.
2. Study the Internal Specification.
3. Develop the source program code as
per Design.
4. Prepare Unit Test Cases.
5. Ensure traceability of Internal
Specification to code by mentioning the
Specifications ID in relevant file /
function headers. Minimal Commenting
is required in Runtime Compiled Src
Code; external registers for comments
should be maintained in these cases.
6. Compile and Build Executable Program.
7. Carry out the Unit Testing. Verification of
Test case execution can be done, If
required.
8. Log defects in Defect Database.
9. Prepare Test Result (Test Point Matrix).
Test Result may be Appended to
Executed Test case sheet.
10. Fix the Bugs, if any.
11. Initiate modifications in design
document.
12. Make sure that all relevant
documentation is also updated.
13. Ensure test/ retest of modified code.
14. Repeat steps 4 to 13 if necessary.

Process Description of Coding and Testing 2

Rev No. 2.0 Header not to be changed 02-01

REFERENCES Coding standards, Test plan, Test results

template etc.

OUTPUT Modules ready for integration and Unit test

results.

VALIDATION CRITERIA Review and approval of unit test cases and

results by the Team Leader Development.

EXIT CRITERIA Bug free units of all the tested modules.

2. INTEGRATION TESTING

PURPOSE To combine individual software modules

together so that they represent clearly
identifiable functions that fulfill functional
specifications or act in support of functional
specifications. These functional Groups of
modules can then be pieced together and
tested as according to integration testing
plan.

ENTRY CRITERIA Successful completion of unit testing.

INPUTS Internal / Functional Specification.

TEAM Development Team.

USERS Development Team and Quality Assurance

Group.

TASKS Following tasks are to be done:

1. Link units that make identifiable function.
2. Create Functional level test cases.
3. Run Functional level test cases.
4. Fix bugs.
5. Repeat steps 2 to 5 if necessary.
6. Build a system from functions.
7. Test the integrated functions. Verification
of Test case execution can be done, If
required.
8. Log defects in Defect Database.
9. Prepare Test Result (Test Point Matrix).
Test Result may be appended to
Executed Test case sheet.
10. Fix bugs.
11. Repeat steps 2 to 10 if necessary.
12. Make a QA test point matrix.

Process Description of Coding and Testing 3

Rev No. 2.0 Header not to be changed 02-01

13. Deliver the product/modules for system

testing.

REFERENCES Test plan and test result template.

OUTPUT Product ready for system testing and Test

results.

VALIDATION CRITERIA Review and approval of test cases and test

results.

EXIT CRITERIA Bug free modules.

Process Description of Coding and Testing 4

Rev No. 2.0 Header not to be changed 02-01

3. SYSTEM TESTING

PURPOSE To determine the degree to which the

software meets its functional and
performance requirement.

ENTRY CRITERIA Reviewed code and completion of unit and

integration testing.

INPUTS External Specifications, baselined product,

Release Notes.

TEAM QA

USERS Development Team.

TASKS Following tasks are to be done:

1. Make the test plan according to external
specification.
2. Make the test cases for all type of
testing applicable.
3. Mention the environment in case of
performance testing and stress testing.
4. Install software product on system test
hardware.
5. Execute each test case. Verification of
Test case execution can be done, If
required.
6. Log defects in Defect Database.
7. Prepare Test Result (Test Point Matrix).
Test Result may be appended to
Executed Test case sheet.
8. Fix the Bugs, if any.
9. Initiate modifications in design
document.
10. Make sure that all relevant
documentation is also updated.
11. Ensure test/ retest of modified code.
12. Repeat steps 2 to 11 if necessary

REFERENCES Test plan and Test results template.

Process Description of Coding and Testing 5

Rev No. 2.0 Header not to be changed 02-01

OUTPUT Test results.

VALIDATION CRITERIA Review and approval of Test plans and test

results by team leader QA and GH
development.

EXIT CRITERIA This step is complete when the software

product has passed all system-level tests.

For Quick Release SDLC following is applicable to all Three Levels of

Testing

 Prepare all the test cases in any scratch pad/ any file, but there should
be some tracking technique (as decided by Configuration manager) for
traceability of the files.
 Compile all the scratch pads documents at the time decided by the
project head/project leader and create a Final test plan for Testing.
 Formal Review of Test Plan
 Execute the test cases and report results.

Process Description of Coding and Testing 6