Synopses & Reviews
Assessment and Control of Software Risks represents a cross-disciplinary effort which applies a format used in medical writing to software engineering. The book Control of Communicable Diseases in Man, published by the U.S. Public Health Service, was organized in alphabetical order, and listed all known communicable diseases starting with actinomycosis and ending with yellow fever. The format and idea of Control of Communicable Diseases in Man is the basis for this book. Obviously the contents for Assessment and Control of Software Risks are not identical to the former, since software engineering is not medicine. However, its structure is similar. This book assumes that readers are already familiar with the basic terminology of software, and have access to a reasonably capable source of books and journals. Although this book has a large glossary, the terms defined are primarily those which come up during assessment sessions and are troublesome or ambiguous.
This handbook summarizes more than 50 of the major problems of building and maintaining software projects, and outlines the prevention/control “therapies” available. KEY TOPICS: Considers in depth the software-related risks in the domains of methodologies, tools, organization structures, skills and specialization, client relations, and sociological issues. For software managers and software professionals in software engineering, software quality assurance, and related software areas.
Summarizes more than 50 of the major problems associated with building and maintaining software projects. It considers software-related risks in the fields of methodologies, tools, organization structures, skills and specialization, client relations, and sociological issues.
Table of Contents
1. The Most Common Software Risks.
2. The Most Serious Software Risks.
3. Artificial Maturity Levels.
4. Canceled Projects.
5. Corporate Politics.
6. Cost Overruns.
7. Creeping User Requirements.
8. Crowded Office Conditions.
9. Error-Prone Modules.
10. Excessive Paperwork.
11. Excessive Schedule Pressure.
12. Excessive Time to Market.
13. False Productivity Claims.
14. Friction Between Software and Senior Management.
15. Friction Between Software Developers and Clients.
16. High Maintenance Costs.
17. Inaccurate Cost Estimating.
18. Inaccurate Sizing of Deliverables.
19. Inadequate Assessments.
20. Inadequate Compensation Plans.
21. Inadequate Configuration Control and Project Repositories.
22. Inadequate Curricula (Software Engineering).
23. Inadequate Curricula (Software Management).
24. Inadequate Measurement.
25. Inadequate Package Acquisition.
26. Inadequate Research and Reference Facilities.
27. Inadequate Software Standards.
28. Inadequate Risk and Value Analysis.
29. Inadequate Tools and Methods (Project Management).
30. Inadequate Tools and Methods (Quality Assurance).
31. Inadequate Tools and Methods (Software Engineering).
32. Inadequate Tools and Methods (Technical Documentation).
33. Lack of Reusable Code. Lack of Reusable Data.
34. Lack of Reusable Designs (Blueprints).
35. Lack of Reusable Documentation.
36. Lack of Reusable Plans and Historical Data (Templates).
37. Lack of Reusable Test Plans, Test Case, and Test Data.
38. Lack of Specialization. Long Service Life of Obsolete Systems.
39. Low Productivity.
40. Low Quality.
41. Low Status of Software Personnel and Management.
42. Low User Satisfaction.
43. Malpractice (Project Management).
44. Malpractice (Technical Staff).
45. Missed Schedules.
46. Poor Organization Structures.
47. Poor Technology Investments.
48. Silver Bullet Syndrome.
49. Slow Technology Transfer.
50. Glossary of Software Assessment and Management Terms.