Planning+Software+Quality

This page is for the work on Chapter 6: Planning for Software Quality

Owners of this page, please introduce yourself:

Something that you like to do: || Say something about your experience with software || What would you like to learn from this course? || How would you like to learn from this course? || 101-25-152 || Dynamic Web Develop || Three years experience for developing Software (In house) || Knowledge for manage in a Software Project Management || Learn, show practical knowledge || 102-15-159 || Programming ||  Software Design, Development & Implement with VB6, Database Management with MS SQL Server 2000 and Reporting with Crystal Report 8.5. Working with live project like Gulshan Club Election Software, Uttora Club Election Software, Amber Cotton Mills etc. Currently working on Dhaka Club Ltd Management Software that includes Accounts, Inventory, and Point of Sales Sale. || How to deployes a project in short time with completing all parts. All part of managing a software project. || Practical work, sharing knowledge etc. ||
 * Name/ID || Name a hobby or
 * Md. Masudur Rahman
 * Roni Shkder
 * Roni Shkder

Task 1: Summarise the chapter below in terms of bullets: (10 marks)


 * // Ans by 101-25-152 & 102-25-159 //**


 * __ Quality __**
 * According to customer- **The software you create lives up to expectations, is reliable, and does some incredible things the customer doesn’t expect.
 * According to project team **- The work is completed as planned and as expected, with few errors and fewer surprises.
 * According to managers- **The customer is happy and the project delivers on time and on budget.

As the project manager, your primary concern is satisfying the product scope. The product scope is the description of the software the customer expects from your project. In order to satisfy the product scope you must first have several documents:
 * __ Referring to the product scope __**


 * Product scope description document: **- This document defines what the customer expects from the project.
 * Project requirements document: **What types of functionality should customers be able to perform with the software? This document prioritizes the customers requirements.
 * Detailed design document: **This document specifies how the project team will create units that meet the project requirements, which in turn will satisfy the product scope.


 * Examining quality versus grade **Quality and grade is not the same thing. Low quality is always a problem, but low grade may not be. Quality, as you know, is the ability of software to deliver on its promises. Grade is the ranking or classification we assign to things. Within software developments we also have grades and quality issues. A quick, cheap software fix may be considered low grade, but it can still be a high-quality software solution because it satisfies the scope of the simple project. During the planning process, one goal of customer analysis is to determine the requirements for quality and grade.


 * Working with a Quality Policy **A quality policy is an organization-wide policy that dictates how your organization will plan, manage, and then control quality in all projects. This policy sets the expectations for your projects and acceptability. Quality policies fall under the big umbrella of quality assurance (QA). QA is an organization-wide program, the goal of which is to improve quality and to prevent mistakes.

ISO 9000-certified organization focuses on business-to-business dealing and ensures customer satisfaction. An ISO 9000-certified organization must ensure that it:  Establishes and meets the customer’s quality requirements.  Achieves customer satisfaction throughout the project.  Takes internal measures to continually improve performance.
 * Working ISO Programs **The International Organization for Standardization (ISO) is a worldwide body with 153 members. There are many different ISO programs, but the most popular is ISO 9000. An

1. Create constancy of purpose for improving products and services. 2. Adopt the new philosophy. 3. Cease dependence on inspection to achieve quality. 4. End the practice of awarding business on price alone; instead, minimize total cost by working with a single supplier. 5. Constantly strive to improve every process for planning, production, and service. 6. Institute training on the job. 7. Adopt and institute leadership. 8. Drive out fear. 9. Break down barriers between staff areas. 10. Eliminate slogans, exhortations, and targets for the workforce. 11. Eliminate numerical quotas for the workforce and numerical goals for management. 12. Remove barriers that rob people of pride of workmanship, and eliminate the annual rating or merit system. 13. Institute a vigorous program of education and self-improvement for everyone. 14. Put everybody in the company to work accomplishing the transformation.
 * Getting a Total Quality Management workout **In software development, TQM means that the entire team works to make the development of the software better, the process from start to completion better, and the deliverable better as well. TQM is largely based on W. Edwards Deming’s 14 Points for Quality:


 * Balancing Time, Cost, and Quality **The Iron Triangle of project management, as shown in Figure 1, requires that all three constraints of a project remain balanced in order for a project to be successful. This is because if the sides of the triangle are not kept in balance, quality is most likely to suffer. So, if your scope increases, then your time, cost, or both will also need to increase or quality will suffer.

Optimal quality, fun as it is, has two related costs for you to consider:  Cost of quality: This is the amount that you have to spend to achieve optimal quality. But don’t forget the cost of training or direct project expenses like hardware and software. Of course, you can’t forget to pay third parties, such as quality assurance testers and consultants like your business analyst.  Cost of nonconformance to quality: This is the cost assigned to wasted labor, wasted materials, and rework when your project team delivers poor and faulty code. This cost also ripples out to a loss of sales because of errors, returns, and unhappy customers who bought and relied on your software.
 * Examining optimal quality **Optimal quality describes how much quality is expected in return for the cost to achieve that level of quality. The optimal quality, in this instance, is how much quality should be built into the software while still allowing for a profit margin. Ideally, the cost of quality is much lower than the final profit margin.

i. Consider how changes may affect quality, and address this in your change control plan and your quality management plan. ii. Changes are not evil beings to be avoided. They are a necessary part of any project, and your process for dealing with them should be addressed in your change control plan.
 * Considering quality when making changes **One of the biggest influences on quality is changes to the project scope. The two points to consider regarding change control are: