Addressing integration during software development
A style of software development like an agile methodology should address some critical issues. One of them is continuously testing as the integration of the software module progresses. It could be summed as:
- As the programmer implements an engineering task, the integration plan with the rest of the system should be established and executed at the time.
The objective is to prevent the software going sour by maintaining comprehensive lists of tests and integration changes. For example this can happen several times in a working day. This should conform to a quality baseline. In fact integration is so important that integration and testing goes side by side. Integration immediately follows development. When a test case breaks during integration, debug the test case, fix the code, and re-run the whole set of test cases again. Every time a task is completed, integrate and build the system. This is one way to reduce the cost of integration.