| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 6<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 7<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 4 Abbreviated terms 5 Explanatory note on terms 5.1 The term risk 5.2 The term control <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6 Risks 6.1 General <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 6.2 Product-related risks 6.2.1 General 6.2.2 Risk 01: The quality of the software is reduced because of modifications to it 6.2.3 Risk 02: The quality of the software is reduced because of modifications to the environment in which it runs <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.3 Project-related risks 6.3.1 General 6.3.2 Risk 03: Planned functionality is not completed on time because of underestimation of the amount of work involved 6.3.3 Risk 04: The product is not delivered on time and within budget because the scope is changed <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 6.3.4 Risk 05: The software does not meet the requirements laid down because the team does not have the required expertise 6.3.5 Risk 06: The product does not offer the right functionality because of inadequate management of the work <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6.3.6 Risk 07: The product lacks the right non-functional properties because functional requirements were given too much priority 6.3.7 Risk 08: Misunderstandings occur because the communication between stakeholders is poor <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 6.3.8 Risk 09: Custom software does not (demonstrably) meet obligations because development, use and maintenance were not sufficiently auditable 6.3.9 Risk 10: The product is not delivered on time because a great deal of time was needed to set up for software development <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 7 Controls 7.1 General 7.2 Project-related controls 7.2.1 General <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.2.2 Project preparation <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 7.2.3 Project execution <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 7.2.4 Completion of development and\/or maintenance <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 7.3 Organization-related controls 7.3.1 Control 16: Supporting teams with specialist knowledge and tools <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 7.3.2 Control 17: Continuous risk management <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | Annex A (informative) Overview of risks and controls <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | Annex B (informative) Assessment tool <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Software engineering. Controlling frequently occurring risks during development and maintenance of custom software<\/b><\/p>\n |