CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 2 2020 Page 1 of 4
ITECH7409 Software Testing
Overview
Assignment 2 (Group) – Software Test Document
This assignment is a group assessment, where one submission is made per group and all
individuals in the group receive the same grade. There should be 2-3 students in each group.
For any software development, testing activities need to be fully documented.
The IEEE 829-2008 Standard prescribes a set of documents that cover the various stages of testing,
including:
Master Test Plan (MTP): provides an overall test planning and test management document for
multiple levels of test
Level Test Plan (LTP): 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.
Level Test Design (LTD): details test cases and the expected results as well as test pass criteria.
Level Test Case (LTC): specifies the test data for use in running the test cases identified in the
Level Test Design.
Timelines and Expectations

Minimum time expectation: at least 10 hours
Learning Outcomes Assessed

K3. 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

S1. Analyse and critically evaluate software requirements and proposed solutions
CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 2 2020 Page 2 of 4
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

A2. Carry out the process of software testing and writing reports detailing the results;
A3. Implementation of project management principles with respect to softwaretesting
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 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 test plan
• 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 test cases
• refer to rubric for other requirements
Note: It is not necessary to include Section 4 or Appendix A as suggested in slide 23, as it will
not be possible to conduct testing of the Online Backstage Management System software in
this assignment.
CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 2 2020 Page 3 of 4
Marking Criteria/Rubric
Student ID: Student name:
Student ID: Student name:
Student ID: Student name:

1 https://federation.edu.au/current-students/learning-and-study/online-help-with/guides-to-your-assessments
CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 2 2020 Page 4 of 4
Submission
Your assignment should be completed according to the Guides to your assessments
https://federation.edu.au/ data/assets/pdf_file/0018/190044/General-Guide-to-Writing-and-Study-Skills.pdf
You are required to provide documentation, in Word format, which includes:
• a front page – indicating your name, a statement of what has been completed and
acknowledgement of the names of all people (including other students and people outside of
the university) who have assisted you and details on what parts of the assignment that they
have assisted you with
• list of references used (APA style)
Once Turnitin has assessed your work as having satisfactory authorship, using the link provided
in Moodle, please upload your report in one Word file or as directed by your lecturer.
Name your Word file in the following manner:
<StudentID1_StudentID2_>.docx
You might be asked to demonstrate, discuss or modify your work.
Feedback
Assessment marks will be made available in fdlMarks, feedback to individual students will be
provided via Moodle or as direct feedback during your tutorial class
Academic Misconduct
To submit your assessment task, you must indicate that you have read and understood, and comply
with, the Federation University Australia Academic Integrity and Student Plagiarism policies and
procedures
http://policy.federation.edu.au/learning_and_teaching/compliance/academic_integrity/ch02.php.
You must also agree that your work has not been outsourced and is entirely your own except where
work quoted is duly acknowledged. Additionally, you must agree that your work has not been
submitted for assessment in any other course or program.
Federation University General Guide to Referencing:
The University has published a style guide to help students correctly reference and cite information
they use in assignments. A copy of the University’s citation guides can be found on the university’s
web site. It is imperative that students cite all sources of information. The General Guide to
Referencing can be purchased from the University bookshop or accessed online at:
https://federation.edu.au/library/guides/referencing

The post ITECH7409 Software Testing appeared first on My Assignment Online.