Cambridge Technical Introductory Diploma in IT

(Unit 9 - LO3)

Be able to implement and test products (P4, P5, M3)

Be able to implement and test products (P4, P5, M3)

There are two aspects to this section; a requirement specification and the product that is shown to meet that specification.

3.1 Implementation

The implementation involves the actual creation of the product.

Unit testing

Unit testing needs to be carried out during the implementation. Although you will tend to test each function as you develop the product, you need to record these tests as part of your log. For example, if you are building a web page, you may test how it functions after you have added some Java Script code. This is a a "unit test". The evidence can come from a screenshot, photo or video, depending on your product. A completed test table contains the test and evidence.

Integration testing

Once several sections of your product have passed unit testing, you need to combine them into one sub-system. For example, if you are building a website with multiple pages, they will need joining together before carrying out integration testing. This tests that once joined, the units still function correctly together. Again, this needs to be recorded in your log. The diagram below shows how these units can be combined into sub-systems, and the sub-systems combined into the system.

Product testing

Once the final solution has been developed, it will need thorough testing to ensure that the sub-systems have been joined together successfully and that it covers all of the original requirements. Although these tests may have been planned by the designer in the design stage, they will need revisiting and revising to cover any changes made during implementation.

The table below shows an example of a partially completed test table where the first test did not work as planned but the second did. The evidence in this case is linked as well - this could be in the form of a screenshot, photograph or video for example.

Test number Test description Expected outcome Actual outcome / evidence Remedial action
1 Entering a valid username and password to the log in page The login success page is shown

The login failed page is shown.

Check the logic of the login page script and the database connection script.
2 Entering a valid username but invalid password to the log in page The login failed page is shown.

The login failed page is shown.

3 Entering an invalid username and password to the log in page The login failed page is shown.

The login failed page is shown.


The developer finally needs to test the product against the functional and non-functional requirements to ensure that all of the original requirements are met.

Using results of unit testing and integration testing to improve or enhance the product during implementation.

While creating and testing your solution, you are likely to come across problems or errors. (Sorry, may? You will!) This is to be expected. Errors are recorded in the implementation log, and as you can correct them and re-test, the results showing the corrections need adding. This demonstrates that you are improving the solution during the development.

Upon completion of testing (i.e. when the product is working), the results need to be analysed. This involves a discussion of the testing, identifying the positive ares that you have found, for example one element of the product may perform better than expected, or you may have succeeded in meeting a set of requirements. Areas of weakness need to be identified, along with any improvements to these weaknesses as well as enhancements.

An improvement involves building upon what you have already produced, e.g. you could make the product more user friendly or more efficient, or a process could be made shorter for the user.

An enhancement involves adding something extra to the product. This is something that you may not have identified in the design specification but would be beneficial to add.

Both the improvements and enhancements need to be described in the context of the product, and justified to show how they would improve or enhance the product, explaining what benefit this would be to the client.

Implementation log.

While building the solution, you will need to produce an implementation log to record the steps you took when creating the product. It can be completed as a table, an annotated copy of the implementation plan, a diary or any method that is appropriate for your product. (It may imvolve taking photographs or video of the product being built.)

Revisit the implemenation plan.

The final design solution required you to create an implementation plan could be presented as a Gantt or PERT chart. This should be revisited and updated during the implementation stage to include any changes that need to be or have been made. This is especially true with respect to deadlines for completion (milestones) as any delay can have an effect on other deadlines.

Additional resources that you may find useful: