As an example, of the practical implementation of this approach, this section provides an outline of the testing regime that will be applied for the development of the Client Software (Workstream 2).

[Instructions on what to include in this section: In this section, you need to include a practical overview of the steps that you will apply within the precedingtesting regime to conduct the testing of the Client Software. This does not need to be too long (typically no more than one to two pages of text). Make the discussion of the issues as practical as possible. For instance, you should include aspects such as these:

• Unit Testing. The client software is being developed by StreamTech, who are located in Sydney. They will, therefore, be responsible for coordinating practical aspects of the testing. However, EdMI in Perth is managing all of the testing and will also need to be able to monitor the development and testing directly (without having to fly over to Sydney all the time, as this would add a lot of costs to the project). Therefore, you would need to consider a range of issues that will include:
  • Hardware. StreamTech/EdMI are going to need hardware for their development environment and test environments.
    • This means that specification/design will need to be conducted early, so the specific requirements can be determined.
    • The equipment would then need to be ordered, but you would need to think about how much equipment is needed and to which sites it needs to be delivered. Is it just Sydney? Additionally, do we need hardware for every one of the operating systems listed in the Section 5 blue text? Alternately, can we use techniques such as the application of emulations or partitions, to help minimise costs? This is an important question to consider early.
    • Our test teams would then need to conduct unit testing once the equipment is delivered to site. These tests must be defined in line with the specification/design work that was implemented. In addition to the standard functional testing, which non-functional tests will be required? This is where the preceding section within the QMP will help, so you can describe specific types of testing that would be written into the test plans.
  • Software. For this assignment, you can assume that StreamTech will be doing all of their client software development at their Sydney site, which will simplify unit testing of the software to a great extent. However, they would still need to set up (if they don't already have it) an Integrated Development Environment (IDE) and a series of standardised methods for controlling code management/unit testing (e.g. checking-in/out software blocks, so the code base is coordinated to avoid untested software moving on to integration testing - remember this has to take into account reworks of code blocks when problems are identified in testing).

Please note that the preceding listing does not include all of the factors that you would take into account. Additionally, it would be upsetting to just see the same information included in your team's QMP response. What is expected is that you will think about these issues and provide a relatively short and focussed description of the approach that would be taken. Just as importantly, when considering these issues, think about:

• who will conduct the testing at each stage;
• when will the testing be carried out (think carefully about some of the preceding issues);
• where will the testing be conducted; and
• how will the testing be managed and coordinated