Re: [agile-testing] The Whole Team approach
- quoteGood point, I have wondered that myself before - is manufacturing QC similar to software QC? One of my coworkers is an industrial engineer, I will ask him. It seems like quality values would translate from one industry to another. Maybe the feedback loop in a machine shop is quicker? If you don't size the part exactly right, it gums up the works right away?unquoteQC in Manufacturing:Conceptually is the same as in software engineering.Their Specification:1. Independent part drawings and tolerances, surface finish defined by various associations such as API, IEEE, SAE, DIN, etc2. Assembly drawings and specifications for RPM, vibrations, torque, etc for a gearbox, for example.3. Metallurgical properties are defined wrt standards such as SAE, DIN, etcMethodology of testing:Destructive and non-destructiveDestructive: Metal is broken to check metallurgical properties, tensile strengths, etcNon-destructive testing: using eddy current, ultrasonic etc to check whether the metal has inside cracks without damaging the partQA and QC:QA: The quality assurance plan is defined upfront and submitted to customers about how the quality will be achieved and what standards will be referenced.QC: Randomly parts are picked for testing. records are maintained using SPC, process is controlled if the charts show that dimensions are moving out of the tolerance zoneInspections:Done by outside agencies appointed by customers or as agreed in QA plan. For example, Boiler inspector will come and pick any part randomly and ask teams to carry out tests in front of him/her.The difference that I find in QC of software engineering and manufacturing is that there is never a uncertainty over the specification. Specs are drawings or standards written by governing bodies and mostly very clear. If you have the drawings, and start making a car, nobody will end up in producing a bike or a car that has only one door.Concepts like "working software" are not applicable there.Pressures to produce high-quality product:very high.In my opinion, if at all we have to compare software engineering with manufacturing, the right analogy will be comparing SE with design activity in manufacturing and not the manufacturing itself. Design activity is a mental process and mistakes in assumptions, choosing right standards, tolerances, loads, environmental conditions, etc will affect the final product. and therefore, design activity is more comparable with software development and testing process.STRG
Check out the all-new face of Yahoo! India. Click here.
- --- In firstname.lastname@example.org, Kim Gräsman <kim.grasman@...> wrote:
> ... the idea of standardized work is good, I think. ChecklistsThanks for your comments Kim. I was thinking that many of the
> are a great way of capturing monotone work, if it can't be
> automated with any reasonable effort.
checklist items should be automated too. With better build tools (for
instance: ant/Maven instead of Make) deployment is now more
automatable than it was in the past when I was using those checklists.
-- Bob Clancy