CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem XXXXXXXXXXPage 1 of 5 ITECH XXXXXXXXXXSoftware Testing Assignment 2 (Group) - Software Test Document Overview This assignment is a group assessment,...

1 answer below »
i want this on 30 may at 3 0 clock.



CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 1 2019 Page 1 of 5 ITECH7409 Software 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 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 Marks and Percentage Value of Task: 20 marks 20% Due: Thu, May 30, 2019 - 16: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 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 CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 1 2019 Page 2 of 5 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) • 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 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 1 2019 Page 3 of 5 Marking Criteria/Rubric 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. Gantt Chart /10 6. Budget /10 7. Report /20 Total /70 Final /20 Comments CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 1 2019 Page 4 of 5 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) 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:.docx 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 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 Your support material must be compiled from reliable sources such as the academic resources in Federation University library which might include, but not limited to: the main library collection, library databases and the BONUS+ collection as well as any reputable online resources (you should confirm this with your tutor). 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 https://federation.edu.au/__data/assets/pdf_file/0018/190044/General-Guide-to-Writing-and-Study-Skills.pdf http://federation.edu.au/students/learning-and-study/online-help-with/plagiarism CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem 1 2019 Page 5 of 5 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 https://federation.edu.au/library/guides/referencing ITECH7409 Software Testing Your assignment should be completed according to the Guides to your assessments 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 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 ha... 35Thttp://federation.edu.au/students/learning-and-study/online-help-with/plagiarism35T
Answered Same DayMay 27, 2021ITECH7409

Answer To: CRICOS Provider No. 00103D ITECH7409 Assig 2 Sem XXXXXXXXXXPage 1 of 5 ITECH XXXXXXXXXXSoftware...

Amit answered on May 30 2021
140 Votes
Title of the assignment: Software testing
Student name:
Student ID:
Professor’s name:
Course title: ITECH7409 (Assignment – 2)
Date: 5/29/2019
Table of Contents
1.    Introduction    3
2.    Test plan for OBMS application    3
3.    Test cases for OBMS application    5
4.    Gantt chart for testing OBMS application    8
5.    Req
uired budget estimation    8
6.    Reported events during testing OBMS    9
7.    References:    10
1. Introduction
The activities performed for checking the actual results of any application by matching them with the expected results are called software testing. The possible defects in the application are mainly identified by software testing. The interested properties of software and associated components are mainly tested. The requirements missing from actual implementation and possible gaps are identified with software testing. The automated tool based testing and manual testing both are possible for the application like OBMS. The verification of developed AUT is mainly carried out in performed software testing [Arcuri, 2018]. The software testing is mainly carried out in following categories:
· Functional testing
· Non functional testing, and
· Maintenance testing.
Each testing category contains different types of testing in it. These testing are carried out for the required measures of applications. The mainly used testing in these categories are maintenance testing, regression testing, usability testing, scalability testing, volume testing, load testing, interoperability testing, globalization testing, unit and integration testing.
2. Test plan for OBMS application
For OBMS application, the development of test plan is most important. This developed document for OBMS application will define the testing activities and their possible scope. The used resources in testing and their schedule are effectively maintained in test plan. The developed test cases, their tasks, features, appointed testers, independence degree and contingency plan for identified risks is maintained in test plan [Briand et al, 2016]. A specific template for execution of test cases is followed in test plan. The test plan is mainly based on the CMP (configuration management plan) and PP (Project plan).
    Sr. No.
    Features which are tested
    Features not tested
    Tools and testing environment
    1.
    The testing of all developed features for OBMS application and provided functions must be tested.
    The tester can ignore the load testing of possible users to OBMS application.
    The audience based testing environment with automated tools is used for testing OBMS.
    2.
    The tester must test the user inputs to this OBMS application and required outcomes to users.
    The tester can ignore the system behavior while testing the user input.
    The automated tools working in client environment provides testing of user input to OBMS application.
    3.
    The tester must test all SRS functionalities in OBMS application.
    The assigned rules in SRS can be ignored while making testing of OBMS application.
    The OBMS application must work on developed SRS specification and required functions also provide the expected results. ...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here