Reference no: EM132897167

ITECH7409 Software Testing - Federation University Australia

Learning Outcome 1: Critically evaluate software requirements as inputs toward testing of the final solution

Learning Outcome 2: Analyse and critically evaluate appropriate tools and techniques to support the testing process

Learning Outcome 3: Develop a good understanding of selecting and applying measures and models used for testing that are compliant with the appropriate professional industry standards such as the ACS and IEEE

Learning Outcome 4: Critically reflect on the outcomes of software testing and propose strategies for improving quality and performance outcomes in the software process

S1 Analyse and critically evaluate software requirements and proposed solutions

S2 Apply complex decision making to select appropriate testing techniques

S3 Write professional level management, planning, quality assurance and testing documentation for a software system

S4 Apply effective testing techniques to software systems of varying scales and test levels

S5 Work in a team to evaluate and implement appropriate methods for determining quality and reliability in software systems

S6 Undertake quality assurance processes

A1 Develop and maintain plans for scheduling quality assurance tasks including software testing

A2 Carry out the process of software testing and writing reports detailing the results;

A3 Implementation of project management principles with respect to software testing

Assessment Details

Commence your assignment task by reading the case study documents for the Online Backstage Management System (OBMS). The documents are:

• Software Requirements Specification(SRS)
• Software Architecture Design Document(SADD)
• Administratordocumentation
• User documentation

Requirements:

Each group will need to submit a Software Test Document. The document will describe, in as much detail as possible, a full testing suite for the Online Backstage Management System.

The testing suite should include descriptions of the unit, integration and system testing levels and contain a detailed requirements traceability matrix.

To create the Software Test Document, groups should use the format shown in the sample Software Test Documentation shown in Lecture 5, slide 23, as this format incorporates features of:

• master testplan
• level test plans for unit, integration and system testing levels that should relate to the requirements traceability matrix
• level test designs for unit, integration and system testing with details of the specific test data for each of the testcases

Attachment:- Software Testing.rar