obsidian/Main
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2025-01-10 15:34:48

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-10 15:34:48 +01:00
parent ab41e06b07
commit a2f7956ccd
9 changed files with 81 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
5 Media/0 Books/Software Project Survival Guide by Steve McConnell.md
View File

@@ -572,6 +572,39 @@ Usually developers cannot wear both the developers' hat as well as the tester's
- Start system testing as soon as you have the first executable software
- Use a requirements traceability matrix to ensure all requirements are covered.
- test cases as rows
- requirements as columns
- every row and column need at least one mark, else they are useless
- Automate the testcases. The more critical the software is, the more testers per developers are needed.
> [!Quote] Testing vs Quality Assurance
> Testing is a means of discovering the quality level of a software system, not a means of assuring software quality.
##### Beta Testing
Release of software to a selected group of testers.
##### Other
![[Pasted image 20250110145533.png]]
![[Pasted image 20250110145548.png]]
Have measurable criteria for software releases.
> [!question] Survival Check
> - 👍🏼 Project has a written, approved Quality Assurance Plan.
> - 💣 Project isn't following the written plan.
> - 👍🏼 Quality assurance is initiated in parallel with requirements work.
> - 👍🏼 Defect tracking software is placed online at requirements development time, and defects are tracked from the beginning of the project.
> - 👍🏼 Developers review all designs and code before the designs and code are considered "done."
> - 💣 No designs or code have failed their reviews, suggesting that reviews are superficial.
> - 💣 Developers don't source trace and unit test their own source code prior to submitting it for review, which gives rise to an unwieldy number of defects that have to be tracked from reviews onward.
> - 👍🏼 The Quality Assurance Plan calls for an independent quality assurance group.
> - 💣 No funding is available for an independent quality assurance group.
> - 👍🏼 The Quality Assurance Plan contains measurable criteria that are used to determine whether the software is ready to be released.
## Architecture
- [ ]
---
## Steps towards the Software release