SIX SIGMA
Case Study 2: Why Six Sigma Efforts Do Not Apply to Software
Due Week 8 and worth 150 points
Read the case study titled, “Why Six Sigma Efforts Do Not Apply to Software” located in Chapter 9 of the textbook and consider a situation where you are working for a large software development company that is considering applying the Six Sigma quality constraints to the software it produces.
Write a five to six (5-6) page paper in which you:
- Explain the Six-Sigma quality constraints and provide a justification as to why the software development company should consider it.
- Compare and contrast quality control processes for both hardware and software.
- Examine the arguments presented in the case study and evaluate their applications to control the quality of software produced in the organization. Six Sigma
- Propose a testing strategy for a software development project that ensures high quality of the software delivered. Six Sigma
- Describe the idiosyncrasies of software, and explain why software needs a different set of rules for testing and for quality control as opposed to those used in hardware.
- Use at least three (3) quality resources in this assignment. Note: Wikipedia and similar Websites do not qualify as quality resources.
Six Sigma
Your assignment must follow these formatting requirements:
- Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
- Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment Six Sigma page length.
The specific course learning outcomes associated with this assignment are:
- Compare and contrast testing techniques and concepts to include functional, performance, acceptance, and installation.
- Use technology and information resources to research issues in software engineering.
- Write clearly and concisely about advanced software engineering topics using proper writing mechanics and technical style conventions.
Grading for this assignment will be based on answer quality, logic / organization of the paper, and language and writing skills. Click here to view the rubric for this assignment.
Six Sigma
ORDER THIS PAPER HERE
| Points: 150 | Case Study 2: Why Six-Sigma Efforts Do Not Apply to Software | |||
| Criteria |
Unacceptable Below 70% F |
Fair 70-79% C |
Proficient 80-89% B |
Exemplary 90-100% A |
|
1. Explain the Six Sigma quality constraints and provide a justification as to why the software development company should consider it. Weight: 15% |
Did not submit or incompletely explained the Six Sigma quality constraints and did not submit or incompletely provided a justification as to why the software development company should consider it. | Partially explained the Six Sigma quality constraints and partially provided a justification as to why the software development company should consider it. | Satisfactorily explained the Six Sigma quality constraints and satisfactorily provided a justification as to why the software development company should consider it. | Thoroughly explained the Six Sigma quality constraints and thoroughly provided a justification as to why the software development company should consider it. |
| 2. Compare and contrast quality control processes for both hardware and software. Weight: 15% |
Did not submit or incompletely compared and contrasted quality control processes for both hardware and software. | Partially compared and contrasted quality control processes for both hardware and software. | Satisfactorily compared and contrasted quality control processes for both hardware and software. | Thoroughly compared and contrasted quality control processes for both hardware and software. |
|
3. Examine the arguments presented in the case study and evaluate their applications to control the quality of software produced in the organization. Weight: 15% |
Did not submit or incompletely examined the arguments presented in the case study and did not submit or incompletely evaluated their applications to control the quality of software produced in the organization. | Partially examined the arguments presented in the case study and partially evaluated their applications to control the quality of software produced in the organization. | Satisfactorily examined the arguments presented in the case study and satisfactorily evaluated their applications to control the quality of software produced in the organization. | Thoroughly examined the arguments presented in the case study and thoroughly evaluated their applications to control the quality of software produced in the organization. |
|
4. Propose a testing strategy for a software development project that ensures high quality of the software delivered. Weight: 15% |
Did not submit or incompletely proposed a testing strategy for a software development project that ensures high quality of the software delivered. | Partially proposed a testing strategy for a software development project that ensures high quality of the software delivered. | Satisfactorily proposed a testing strategy for a software development project that ensures high quality of the software delivered. | Thoroughly proposed a testing strategy for a software development project that ensures high quality of the software delivered. |
|
5. Describe the idiosyncrasies of software, and explain why software needs a different set of rules for testing and for quality control as opposed to those used in hardware. Weight: 15% |
Did not submit or incompletely described the idiosyncrasies of software, and did not submit or incompletely explained why software needs a different set of rules for testing and for quality control as opposed to those used in hardware. | Partially described the idiosyncrasies of software, and partially explained why software needs a different set of rules for testing and for quality control as opposed to those used in hardware. | Satisfactorily described the idiosyncrasies of software, and satisfactorily explained why software needs a different set of rules for testing and for quality control as opposed to those used in hardware. | Thoroughly described the idiosyncrasies of software, and thoroughly explained why software needs a different set of rules for testing and for quality control as opposed to those used in hardware. |
| 6. 3 references Weight: 15% |
No references provided | Does not meet the required number of references; some or all references poor quality choices. | Meets number of required references; all references high quality choices. | Exceeds number of required references; all references high quality choices. |
|
7. Clarity, writing mechanics, and formatting requirements Weight: 10% |
More than 6 errors present | 5-6 errors present | 3-4 errors present |
0-2 errors present
|