CS611 Assignment 1 Solution and Discussion

[zaasmi]

Re: CS611 Assignment 1 Solution and Discussion

Assignment No. 01

Semester: Spring 2020

CS611 –Software Quality Engineering Total Marks: 20

Due Date: 1st June 2020

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

Suppose you are working as a software developer in a company. It’s the responsibility of developer to develop good quality software by ensuring that your developed software fulfills all user requirements and work efficiently. Keep these points in your mind and answer the following questions.

 You know that Good requirements have several useful properties, such as being consistent, necessary, and unambiguous. Write any five reasons why is the completeness of the requirements so important?

Question - II: Marks: 10

Continuing the above scenario why is defect-free software important and writes any five steps by which you ensure that your software becomes defects-free.

[zaasmi]

@zaasmi said in CS611 Assignment 1 Solution and Discussion:

Question - II: Marks: 10
Continuing the above scenario why is defect-free software important and writes any five steps by which you ensure that your software becomes defects-free.

Defect-free software is important because

• Delivering defect-free software reduces support costs.
• Delivering defect-free software reduces programming costs.
• Delivering defect-free software reduces development time.
• Delivering defect-free software can provide a competitive advantage

To ensure that my software is defect-free, I will follow the following steps.

1. Will ensure that my collected requirements are accurate and complete
2. Will Trace Every Line of Code When Written
3. Will get time-to-time feedback from client
4. Will perform testing by completing each module
5. Will do proper communication with team members to avoid bugs in software

[zaasmi]

@zaasmi said in CS611 Assignment 1 Solution and Discussion:

Question-I Marks: 10
Suppose you are working as a software developer in a company. It’s the responsibility of developer to develop good quality software by ensuring that your developed software fulfills all user requirements and work efficiently. Keep these points in your mind and answer the following questions.
 You know that Good requirements have several useful properties, such as being consistent, necessary, and unambiguous. Write any five reasons why is the completeness of the requirements so important?

Acceptance and Satisfaction: Missing or incomplete requirements can cause customers to reject systems and users to be dissatisfied with the systems, even if they pass acceptance testing. Customers want to know that what they are buying will be adequate to meet the users’ needs. This is primarily a requirements validation issue.
Development Cost and Schedule: Because requirements are used to estimate system development cost and schedule, missing or incomplete requirements mean that these costs and schedules will be underestimated. One large study implicated incomplete requirements as the cause of 12.3% of cost overruns and failed projects [Standish 1994].
Development: Missing or incomplete requirements ensure that the architecture, design, implementation, and tests that are derived from them will be: ⎯ Incomplete themselves and/or ⎯ Incorrect because the architects, designers, implementers, or testers will make incorrect guesses or assumptions.
Verification: Incomplete requirements are often ambiguous and therefore unverifiable.
Safety: Perhaps the most important aspect of requirements completeness has to do with safety because over time more and more software-intensive systems have been given safety-related responsibilities.