Timeline for Quality Assurance=inspections, reviews..?
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 7, 2012 at 10:55 | vote | accept | John V | ||
Nov 21, 2012 at 21:40 | comment | added | JustinC | Indication of other industries was more of acknowledgement that for some organizations there is a great deal of overlap among what they produce. Groups that produce hardware (and associated control/interface software), or provisioning systems/services, or are highly regulated (health care, finance, energy, defense) will probably encounter a greater stringency for an 'engineered' manufacturing-based outlook to QA, while groups who are public web-dev/e-com oriented (for example) might not see that same push. | |
Nov 21, 2012 at 21:28 | comment | added | John V | Of course this is meant for software development only. I do not know how it is in other industry branches. | |
Nov 21, 2012 at 21:23 | comment | added | JustinC | From my experience, this is probably a more formal view of the actors and their stories. In an industry-wide view of how it is applied, its probably blurred a bit to where there is little distinction. The distinction is probably more industry prevelant when more tangible, physical products are involved; or when adopting engineering-like standards for development like CMM or ISO9000/9001 etc. Depending on scale, and process certification aims, the distinction may be superficial; in practice though, someone with an SQA hat does vastly different things than a product tester or build master. | |
Nov 21, 2012 at 20:43 | history | edited | John V | CC BY-SA 3.0 |
added 352 characters in body
|
Nov 21, 2012 at 20:20 | review | First posts | |||
Nov 21, 2012 at 20:41 | |||||
Nov 21, 2012 at 20:01 | history | answered | John V | CC BY-SA 3.0 |