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

vault backup: 2025-01-10 09:31:48

Browse Source
This commit is contained in:
Claudio Fritsche
2025-01-10 09:31:48 +01:00
parent 95370d9e98
commit 1fa228de8d
5 changed files with 51 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -500,6 +500,19 @@ Tracking where team members spend their time will help with future planning.
### Requirements Development
> [!question] Survival Check - Requirements Development
> - 👍🏼 The project team identifies a set of key end users who can be trusted to shape the software.
> - 👍🏼 The developers create several versions of a basic prototype until they find one that the users are excited about.
> - 💣 Prototyping stops while users are still only lukewarm about the prototype.
> - 👍🏼 The developers extend the User Interface Prototype to elicit detailed requirements from users.
> - 💣 The prototype is not kept broad and shallow, and time is wasted providing deep functionality that will be rewritten for the final software.
> - 👍🏼 The project team develops a User Manual/Requirements Specification to use as the detailed requirements specification.
> - 👍🏼 The fully developed prototype is baselined and placed under change control.
> - 💣 The project team attempts to use the prototype code in the real software.
> - 👍🏼 A separate, non-user-interface requirements document is created, reviewed, and placed under change control.
### Quality Assurance
QA matters because it makes development easier and cheaper. If mistakes and defects are detected upstream they are 50-200 times cheaper, which is why a good quality assurance system pays out.
---
## Steps towards the Software release