I need this assessment by Wednesday afternoonPage 1 of 7 ITECH7409 Software Testing Assignment 1...

Question

I need this assessment by Wednesday afternoon

Page 1 of 7 ITECH7409 Software Testing Assignment 1 Individual Research on Software Testing and Standards Overview According to Standards Australia: “Standards are published documents setting out specifications and procedures designed to ensure products, services and systems are safe, reliable and consistently perform the way they were intended to. They establish a common language which defines quality and safety criteria.” There are several standards, international and national, that relate specifically to software testing. Standards formalize industry best practice and they are agreed upon by professionals in the industry in which the standards apply to. This assignment is an investigation into those standards. The purpose of the assignment is to help you to:- • improve your research and comprehension skills • develop a good understanding of professional industry standards for software testing • appreciate the value of various processes and methods used in industry to test and evaluate software systems Timelines and Expectations Marks and Percentage Value of Task: 100 marks 10% Due: Thursday, May 7, 2020 @16:00 (Week 7) Minimum time expectation: 10 hours Page 2 of 7 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; 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 A1. Develop and maintain plans for scheduling quality assurance tasks including software testing; Assessment Details You will need to: • locate a research paper related to software testing that refers to at least one standard. • research, comprehend and analyse each document (both the paper and the chosen standard) to find relevant details to answer a set of questions, and • prepare a written summary report of findings Page 3 of 7 As a suggestion, commence your search for a research paper at the Federation University website. There is a QuickSearch link on the library home page: There is also a listing of Databases A-Z (http://libguides.federation.edu.au/az.php ) which is a link for Australian Standards Online. Requirements: Questions for the standard: • What is the standard name? • Who holds the copyright for the standard? • Amongst the acknowledged contributors to the document, which universities were involved (if any)? • What is the scope or intent of the standard? • What are key terms and understandings needed for the Type your query here http://libguides.federation.edu.au/az.php Page 4 of 7 standard to be understood and applied? • In your own words, what does application of the standard result in? Or, in other words, what does the standard do? • Finally, what specific relevance to software testing is the standard? Discuss the paper and how it relates to the standard. For example: does the paper suggest how to improve the standard? Does the paper highlight issues in applying the standard? Attached is a sample paper (Wichmann and Cox, 1992) which refers to the ANSI1/IEEE2 Standard 8293 and ANSI/IEEE Standard 1008. Although this paper is somewhat outdated, it serves to illustrate the task for this assignment. Prepare a report of no more than 1,500 words answering all questions. The report should have the following structure. • an introduction to standards and a brief description of the research paper and chosen standard • responses to questions for the standard • listing and a discussion of commonalities and differences between the two documents • a conclusion summarizing the report findings 1 American National Standards Institute 2 Institute of Electrical and Electronic Engineers 3 Current versions of both these standards are available online at Federation University library Page 5 of 7 Marking Criteria/Rubric Student ID:_______________ Student Name: ________________________________ Assessment component Mark 1. Introduction 20 2. Responses to questions 20 3. Listing and discussion of commonalities and differences between the research paper and the chosen standard 20 4. Conclusion 20 5. Spelling, grammar and report presentation 20 Total 100 Final /10 Comments Submission Your assignment should be completed according to the guides for your assessments: https://federation.edu.au/library/student-resources/guides-to-your-assessments You are required to provide documentation, contained in an appropriate file, which includes a front page indicating: • the title of the assignment • the course ID and course name, • student name and student ID • a statement of what has been completed • acknowledgement of the names of all people (including https://federation.edu.au/library/student-resources/guides-to-your-assessments Page 6 of 7 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 • a list of references used (APA style) Using the link provided in Moodle, please upload your report as a Word file. Name your Word file in the following manner: _.docx e.g. Aravind_ADIGA_30301234.docx Also, upload a copy of the standard used by the research paper. 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). http://federation.edu.au/students/learning-and-study/online-help-with/plagiarism Page 7 of 7 Footer CRICOS Provider No. 00103D 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 References Wichmann, B. A. and M. G. Cox (1992). "Problems and strategies for software component testing standards." Software Testing, Verification and Reliability 2(4): 167-185. https://federation.edu.au/library/guides/referencing Timelines and Expectations Learning Outcomes Assessed Assessment Details Requirements: Marking Criteria/Rubric Submission Feedback Plagiarism: References

itech7409-assignment-1-2020-07-partners-lvy4ibkl-onrcqph0.pdf

Akriti · Accepted Answer

Abhijit A. Sawant, Pranit H. Bari, P. M. Chawan / International Journal of Engineering Research and Applications 
(IJERA)          ISSN: 2248-9622      www.ijera.com 
Vol. 2, Issue 3, May-Jun 2012, pp.980-986 
980 | P a g e  
 Software Testing Techniques and Strategies 
Abhijit A. Sawant
1
, Pranit H. Bari
2
 and P. M. Chawan
3
 
 Department of Computer Technology, VJTI, University of Mumbai, INDIA
Abstract 
This paper describes Software testing, need for software 
testing, Software testing goals and principles. Further it 
describe about different Software testing techniques and 
different software testing strategies. Finally it describes 
the difference between software testing and debugging.
Keywords— Debugging, Software Testing Goals, 
Software Testing principles, Software Testing Techniques, 
Software Testing strategies 
I. INTRODUCTION 
Software testing refers to process of evaluating the software 
with intention to find out error in it. Software testing is a 
technique aimed at evaluating an attribute or capability of a 
program or product and determining that it meets its quality. 
Software testing is also used to test the software for other 
software quality factors like reliability, usability, integrity, 
security, capability, efficiency, portability, maintainability, 
compatibility etc. 
For many years now we are still using the same testing 
techniques .some of which is crafted method rather than good 
engineering methods. Testing can be costly but not testing 
software can be even more costly. Software testing aims at 
achieving certain a goals and principles which are to be 
followed.
1.1. Need for Software testing 
Software development involves developing software against a 
set of requirements.  Software testing is needed to verify and 
validate that the software that has been built has been built to 
meet these specifications. If not we may probably loose our 
client. So in order to make it sure, that we provide our client a 
proper software solution, we go for testing [1]. Testing 
ensures that what you get in the end is what you wanted to 
build. We check out if there is any problem, any error in the 
system, which can make software unusable by the client. This 
helps in the prevention of errors in a system.
1.2.  Goals for software testing  
Goals are the output of the software process. Software testing 
has following goals. [2]
1) Verification and validation
Testing can also be used for verifying that the product or the 
software works as desired and validate whether the software 
fulfills condition laid down
2) Priority Coverage 
Testing should be performed in efficient and effective manner 
within the budget and schedule limits.
3) Balanced 
Testing process must balance the requirements, technical 
limitation and user expectation.
4) Traceable 
Documents should be prepared of both success and failures of 
testing process. So no need to test same thing again.
5) Deterministic 
We should know what we are doing, what we are targeting, 
what will be the possible outcome.
1.3. Testing principles  
Principle is the rule or method in action that has to be 
followed. Different testing principles are as follows: [2]
1) Test a program to try to make it fail 
Testing is the process of executing a program with the intent 
of finding errors. We should expose failures to make testing 
process more effective.
2) Start testing early 
This helps in fixing enormous errors in early stages of 
development, reduces the rework of finding the errors in the 
initial stages.
3) Testing is context dependant  
Testing should be appropriate and different for different 
points of time.
4) Define Test Plan 
Test Plan usually describes test scope, test objectives, test 
strategy, test environment, deliverables of the test, risks and 
mitigation, schedule, levels of testing to be applied, methods, 
techniques and tools to be used. Test plan should efficiently 
meet the needs of an organization and clients as well.
5) Design Effective Test cases 
Abhijit A. Sawant, Pranit H. Bari, P. M. Chawan / International Journal of Engineering Research and Applications 
(IJERA)          ISSN: 2248-9622      www.ijera.com 
Vol. 2, Issue 3, May-Jun 2012, pp.980-986 
981 | P a g e  
 Test case must be specified in a way that is measurable so 
that testing results are unambiguous.
6) Test for valid as well as invalid Conditions 
 In addition to valid inputs, we should also test system for 
invalid and unexpected inputs/conditions
7) Testing must be done by different persons at different 
levels 
Different purpose addressed at different level of testing so 
different person should perform testing differently using 
different testing techniques at different level.
8) End of Testing 
Testing has to be stopped somewhere. The testing can be 
stopped when risk is under some limit or if there is limitation. 
II. SOFTWARE TESTING TECHNIQUES 
In this Section the focus is mainly on the different software 
testing Techniques. 
Software Testing Techniques can be divided into two types:-
2.1. Manual testing (static testing) 
It is a slow process and laborious where testing is done 
statically .It is done in early phase of life cycle. It is also 
called static testing. It is done by analyst, developer and 
testing team. 
Different Manual testing Techniques are as follows:- 
A) walk through 
B) Informal Review 
C) Technical Review 
D) Inspection
2.2. Automated Testing (Dynamic testing) 
In this tester runs the script on the testing tool and testing is 
done. Automated testing is also called dynamic testing. 
Automated testing is further classified into four types 
A)  Correctness testing 
B)  Performance testing 
C)  Reliability testing 
D)  Security testing 
 
Fig 1:-Further classification of Automated software Testing
2.2.1. Correctness Testing 
Correctness is the minimum requirement of software. 
Correctness testing will need some type of oracle, to tell the 
right behaviour from the wrong one. The tester may or may 
not know the inside details of the software module under test. 
[3] Therefore either white box testing or black box testing can 
be used. 
Correctness testing has following three forms:- 
1) White box testing 
2) Black box testing 
3) Grey box testing
 
Fig 2:- Different form of Correctness testing [3]
Abhijit A. Sawant, Pranit H. Bari, P. M. Chawan / International Journal of Engineering Research and Applications 
(IJERA)          ISSN: 2248-9622      www.ijera.com 
Vol. 2, Issue 3, May-Jun 2012, pp.980-986 
982 | P a g e  
1) White box testing  
White box testing is highly effective in detecting and 
resolving problems, because bugs can often be found before 
they cause trouble.[5] White box testing is the process of 
giving the input to the system and checking how the system 
processes that input to generate the required output.White box 
testing is also called white box analysis, clear box testing or 
clear box analysis.[5] White box testing is applicable at 
integration, unit and system levels of the software testing 
process.[3] White box testing is considered as a security 
testing method that can be used to validate whether code 
implementation follows intended design, to validate 
implemented security functionality, and to uncover 
exploitable vulnerabilities.
Some Different types of white box testing techniques are as 
follows:- 
1)  Basis Path Testing 
2)  Loop Testing 
3)  Control Structure Testing
Advantages of white box testing:- 
1) All independent paths in a module will be exercised at 
least once. 
2) All logical decisions will be exercised. 
3) All loops at their boundaries will be executed. 
4) Internal data structures will be exercised to maintain their 
validity. 
5) Errors in hidden codes are revealed. 
6) Approximate the partitioning done by execution 
equivalence. 
7)  Developer carefully gives reason about implementation. 
 
Disadvantages of white box testing:- 
1) Missed out the cases omitted in the code. 
2) As knowledge of code and internal structure is a 
prerequisite, a skilled tester is needed to carry out this 
type of testing, which increases the cost. 
3)  And it is nearly impossible to look into every bit of code 
to find out hidden errors, which may create problems, 
resulting in failure of the application.
2) Black box testing  
Black box testing is testing software based on output 
requirements and without any knowledge of the internal 
structure or coding in the program.[5]  
Basically Black box testing is an integral part of „Correctness 
testing‟ but its ideas are not limited to correctness testing 
only. The goal is to test how well the component conforms to 
the published requirement for the component.

Page 1 of 7 ITECH7409 Software Testing Assignment 1 Individual Research on Software Testing and Standards Overview According to Standards Australia: “Standards are published documents setting out...

Answer To: Page 1 of 7 ITECH7409 Software Testing Assignment 1 Individual Research on Software Testing and...

Answer To This Question Is Available To Download

Related Questions & Answers

Submit New Assignment