CRICOS Provider No. 00103D
ITECH XXXXXXXXXXSoftware Testing
Assignment 2 (Group) - Software Test Document
Overview
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
3-5 students in each group.
For any software development, testing activities need to be fully documented.
The IEEE XXXXXXXXXXStandard 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
esponsible 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
Marks and Percentage Value of Task: 20 marks 20%
Due: Thu, June 4, XXXXXXXXXX:00 (Week 11)
Minimum time expectation: at least 10 hours
Learning Outcomes Assessed
K1. Critically evaluate software requirements as inputs toward testing of
the final solution
K2. Analyse and critically evaluate appropriate tools and techniques to
support the testing process
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
Page 2 of 4
CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem XXXXXXXXXX
K4. 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. Ca
y 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)
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.
Page 3 of 4
CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem XXXXXXXXXX
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
elate 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
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.
Marking Criteria/Ru
ic
Student ID: Student name:
Student ID: Student name:
Student ID: Student name:
Assessment component Mark
1. Summary – including completed tasks & who did what /4
2. Test plan - including requirements traceability matrix /8
3. Test Cases – in as much detail as practicable – and prioritized /8
4. Documentation presentation – at a suitable time in lecture or tutorial /10
5. Gannt chart – including Critical Path Analysis /20
6. Budget – include personnel details: e.g. name, role, contact details,
salaries, pay rates
20
Total /70
Final /20
Comments
Page 4 of 4
CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem XXXXXXXXXX
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)
Federation University General Guide to Referencing:
The University has published a style guide to help students co
ectly 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
ookshop or accessed online at:
https:
federation.edu.au/li
ary/guides
eferencing
Before making your final submission, run your report through Turnitin – when this is
acceptable, make your final submission.
Using the link provided in Moodle, please upload the following in one Word file as
directed by your lecturer. Name your Word file in the following manner:
StudentID1_StudentID2_ >.docx
Feedback
Assessment marks will be made available in fdlMarks, feedback to individual students will
e provided via Moodle or as direct feedback during your tutorial class
Plagiarism:
Plagiarism is the presentation of the expressed thought or work of another person as
though it is one's own without properly acknowledging that person. You must not allow
other students to copy your work and must take care to safeguard against this happening.
More information about the plagiarism policy and procedure for the university can be
found at:
http:
federation.edu.au/students/learning-and-study/online-help-with/plagiarism
https:
federation.edu.au/__data/assets/pdf_file/0018/190044/General-Guide-to-Writing-and-Study-Skills.pdf
https:
federation.edu.au/li
ary/guides
eferencing
http:
federation.edu.au/students/learning-and-study/online-help-with/plagiarism