Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.

CS611 Assignment No 03 Fall 2020 Solution & Discussion Due Date: 03-02-2021

Assignment No. 03
Semester: Fall 2020

CS611 –Software Quality Engineering

Total Marks: 20

Due Date: 03rd February, 2021

Assignment Objective:

  • To know about importance of software requirements

To know about  Cost vs Quality

Software requirements

Software completeness

Software defects

  • Uploading instructions:
  • Your assignment must be in .doc or .docx format (Any other formats like scan images, PDF, bmp, etc will not be accepted).
  • Save your assignment with your ID (e.g. bc020200786.doc).
  • No assignment will be accepted through email.

 

Rules for Marking:

It should be clear that your assignment will not get any credit if:

·       The assignment is submitted after due date.

·       The submitted assignment does not open or file is corrupted.

·       Your assignment is copied from internet, or from any other student

      (Strict disciplinary action will be taken in this case).

 

Assignment

 

Question-I                                                                                       Marks: 10

In your video lectures and handouts few examples of “Pre-release defect” are discussed. You have to provide two more examples of Pre-release defect other than discussed in the video lectures and handouts. Also provide proper justification that how these examples should be classified as Pre-release defect.

 

Question - II:                                                                                Marks: 10

Continuing the above scenario:   In your video lectures and handouts few examples of “Post-release defect” are discussed. You have to provide two more examples of Post-release defect other than discussed in the video lectures and handouts. Also provide proper justification that how these examples should be classified as Post-release defect.

Views: 724

Replies to This Discussion

Share the Assignment Questions & Discuss Here.... 

Stay touched with this discussion, Solution idea will be uploaded as soon as possible in replies here before the due date.

CS611-Assignment-3-Solution-Fall-2020

Click on the below link to download the file

CS611-Assignment-3-Solution-Fall-2020.docx

CS611 –Software Quality Engineering

Assignment No 3

(Solution File)

Question-1                                                                                                                

 Assume you are working as software quality engineer at a company named ABC.inc. Assume you are working on software named “Grocery Management System” for a super store named Super Mart. The Grocery Management System have different coding modules for tackling different Grocery groups such as toiletries, cosmetics, cloth, frozen items and food items etc. The Grocery management System also has a discount module which is triggered on specific occasions such as black Friday, Eid and Independence Day.  Due to weak QA a coding bug in discount module is not identified in the testing phase. Since the error is triggered only on specific occasions hence the whole system is working until discount occasion is triggered.

Which type of defect is it? Also support your claim with solid reasons.

 

Solution:

 

Pre-Release Defects

Pre-release defects are defined as ‘Dormant Defects’ which have potential to create problem to users and customers. These inactive defects are triggered on a specific situation or may occur in a low priority area where the concentration of QA activities is low and they might not get specific attention until they are triggered. The following example would help in establishing a better understanding of the concept.

 

Post-Release Defects

            Post-release defects are those who appear in production or at customer site. The software supplier company has to pay for its pocket to fix those post-release defects. Post-release defects have higher cost of fixing as compared to other defects because of multiple installation of the product and the defect has to be fixed at every place. Besides financial loss, company image, trust on the company, reputation, market position all of them will be negatively impacted.

 

Stakeholders in Defect Lifecycle The most important factor in defect resolution is that the decision regarding any defect must be accepted by all stakeholders. For example, if it's decided that certain defect is not to be fixed in current release, then all stakeholders must agree to that. Usually minor defects with very less impact are deferred to the next release with mutual consent and even in some cases the reported one also but can be reclassified as ‘not a bug’ if the situation demands so. The key point is that all the decision regarding defects must be made with mutual consent of all stakeholders.

  • Defect Prevention - Error Source Removal: Defect Prevention is the process of addressing root causes of defects to prevent their future occurrence.
  • Default Detection: it’s a process to detect and remove defects as early/many as possible through various approaches like QA, code reviews, code inspection and design review.
  • Default Containment: it measures the amount of defects that any QA team was able to find as a portion of total defects i.e. found by QA, appeared as run-time error. The focus of this activity is to reduce/eliminating escaping defects.

 

Question - 2:                                                                                                             

 

Assume you are working as tester for a company named ABC.inc. You are working on a web application named Virtual university LMS which have the URL www.vulms.vu.edu.pk. You are required to write a test case for the login functionality of the web application. The required  data and test case sample is given below.

Test case ID                TC1

Test case Scenario      To check the login function with data provided

Web application          www.vulms.vu.edu.pk

Test data                     User name =admin

                                    Password=admin

 

 

Solution:

 

Project Name

Virtual university LMS

Module Name (In case of product)

NA

Test Case ID

Test Scenario

Test Steps

Test Data

Expected Results

Actual Results

Pass/Fail

Comments

TC1

To check the login function with data provided

i. Go to site www.vulms.vu.edu.pk

User name =admin

User should Login into application

As Expected

pass

 

ii. Enter User Id

Password=admin

iii. Enter Password

 

iv. Click Login Butten

 

 

 

 

RSS

Looking For Something? Search Below

VIP Member Badge & Others

How to Get This Badge at Your Profile DP

------------------------------------

Management: Admins ::: Moderators

Other Awards Badges List Moderators Group

© 2021   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service