Reference no: EM133693225
Software Testing
Assignment - Software Test Document
Overview
This assignment is a group assessment, where one submission is made per group and all individuals in the group receive a grade that reflects their contribution. There should be 3-4 students in each group.
For any software development, testing activities need to be fully documented.
The ISO-IEC-IEEE 29119-3 Standard prescribes a set of documents that cover the various stages of testing, including:
Test plan (project test plan): provides an overall test planning and test management document for multiple levels of test.
Test plan (level test plan): provides for each level of testing, the scope, approach, resources,and schedule of the testing activities. It lists items being tested, the features to be tested, the tasks to be performed, the personnel responsible for each task, and the associated risk(s) need to be identified.
Test model specification: details test cases and the expected results as well as test pass criteria.
Test case specification: specifies the test data for use in running the test cases identified in the test model specification.
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.
Learning Outcome 5: Analyse and critically evaluate software requirements and proposed solutions. S2. Apply complex decision making to select appropriate testing techniques.
Learning Outcome 6: Write professional level management, planning, quality assurance and testing documentation for a software system.
Learning Outcome 7: Apply effective testing techniques to software systems of varying scales and test levels.
Learning Outcome 8: Work in a team to evaluate and implement appropriate methods for determining quality and reliability in software systems.
Learning Outcome 9: Undertake quality assurance processes.
Learning Outcome 10: 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.
Learning Outcome 12: 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)
Administrator documentation
User documentation
Requirements
Each group will need to develop a Software Test Document. The document will describe, in as much detail as possible, a full testing suite for the Online Backstage Management System.
In addition, each member of the group should produce a video in which they describe and explain their contribution. The video should be in mp4 format and 5-7 minutes duration.
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 below:
This format incorporates features of:
Project test plan.
Level test plans for unit, integration and system testing levels that should relate to the requirements traceability matrix.
Test model specifications for unit, integration and system testing with details of the specific test data for each of the test cases.