Date post: | 19-Dec-2015 |
Category: |
Documents |
View: | 214 times |
Download: | 1 times |
The Miner…..1950’s - Lord Robens, Chairman of the
NCB, concerned at the high absenteeism, asked a miner: “Why do you regularly work 4 shifts in stead of the regulation 5?”
The miner replied: “I’ll tell you why; because I can’t quite manage on the money I earn in three.”
We all know how frustrating poor quality can be…
Quality Assurance and Maintenance Tools
CS616 - Spring 2004
Team 4
Team Members
• Thomas McKee (Team Leader)
• Sanjukta Nayak • Aditya Prakash
Chandra• Jae Sohn
Scope of Project
• Establish Quality Assurance (QA) measures and tools for the current student projects
Scope of Project
• Three parts: • Set of metrics – help to
monitor student software project quality.
• Web-based database - store project information.
• Interactive forms -integrate metrics chosen in the first portion of the project to judge project quality.
The History of QualityGuild Halls - standards (materials, products, practices,
conditions).
Industrialization - supervisors - growing responsibility for
quality - formal quality inspection.
Post WW1 - sophistication - stats, societies, standards
(military, civil, international).
Post WW2 - Japanese adopt and adapt quality methods
Quality - Definition
“The totality of features and
characteristics of a product or service
that bear on its ability to satisfy stated or
implied needs.”- ISO 8402
Quality Assurance is what we do to achieve this
SQA: Quality Software
People Process
ManagementDiscipline
SQA
“Success” v “Failure”
Quality Assurance helps us avoid failure !
Content
Within budget
On
time
Success
Failure Failure
Failure
Software failuresthe statistics
Successful16%
Challenged53%
Cancelled31%
Source: The Standish Group
Why is it so hard to succeed?
So…
“If we fail to plan, we plan to fail….”anon.
“Someone once said: “You cannot inspect
quality into a product.”
- “he meant that you must build it.”
Is this how you started your project?
Five common solutions to software
development problems • Solid Requirements• Realistic Schedules• Adequate Testing• Following
Requirements• Communication
Conclusions
• Set project milestones to perform a mock Formal Technical Review meeting for each project.
Conclusions
• Issue the software metrics at the beginning of the project.
Conclusions
• A forum for knowledge sharing should be created and utilized. The reliance on standardized technology will ensure that this forum will remain relevant in the future and have greatest benefit.
Conclusions
• At least one more milestone for code delivery in each semester should be established so that the QA team has more time to evaluate systems.
• This will also allow the QA team to find problems early and thus reduce the time required to fix them.
• It should be emphasized to the class that this milestone is a “soft” milestone in which a fully working system is NOT expected.
• This is merely an opportunity for QA to see the system and hopefully uncover faults early.
Software Demonstration
Home