Software Verification and Validation (CS608)
Assignment # 01
Total marks = 20
Jun 01, 2020
Please carefully read the following instructions before attempting assignment.
RULES FOR MARKING
It should be clear that your assignment would not get any credit if:
• The assignment is submitted after the due date.
• The submitted assignment does not open or file is corrupt.
• Strict action will be taken if submitted solution is copied from any other student or from the internet.
You should concern the recommended books to clarify your concepts as handouts are not sufficient.
You are supposed to submit your assignment in .doc or docx format.
Any other formats like scan images, PDF, zip, rar, ppt and bmp etc. will not be accepted.
• Testing phases
No assignment will be accepted after the due date via email in any case (whether it is the case of load shedding or internet malfunctioning etc.). Hence refrain from uploading assignment in the last hour of deadline. It is recommended to upload solution file at least two days before its closing date.
If you people find any mistake or confusion in assignment (Question statement), please consult with your instructor before the deadline. After the deadline no queries will be entertained in this regard.
For any query, feel free to email at [email protected]
Question No. 1. (Marks 16.5)
In the following table, scenarios are given for different testing techniques. Fill the table with the names of relevant testing technique.
|Sr. No.||Test scenario||Testing technique|
|1||Testing performed on every module of the software||Unit testing|
|2||To test the interfaces between components considering particular APIs used in that interface||Integration testing|
|3||To test the system completely against specified requirements||System testing|
|4||Stubs used as lower modules in testing with the modules already developed||Top-down integration testing|
|5||Test the system for acceptability||Acceptance testing|
|6||Product tested by the users||Beta testing|
|7||To test the lower modules and testing lower modules with upper modules that rely upon them To test the lower modules and group of lower and upper modules that rely upon each other||Bottom-up integration testing|
|8||To ensure that each class of the software is working properly||Unit testing|
|9||Test all the modules of the system completely||System testing|
|10||Check all bugs before the release of the product for everyday users||Alpha testing|
|11||Test the business requirements in accordance with the system||Acceptance testing|
Question No. 2. (Marks 3.5)
Write a short note on the quality of the software and the possible ways for the improvement of software quality.
This question will be rewarded on the basis of quality of research and the writing (contents, grammar, spelling, formatting).
Software quality is defined as the attributes of software fulfilled while designing the software that is maintaining its cost, user requirements/expectations, proper working and functionality of software, time to build a product, to make a bug free software.
Attributes of software quality
The quality of software depends on various attributes:
Improvement of software quality
To improve software quality, various processes needs to be maintained:
• There should be proper planning for the project development to achieve good quality.
• Inspections and reviews must be conducted while the product is being developed.
• Defects in the product must be identified and removed before software deployment.
• Fixing the defects will lead to low budget.