Assessment and control of software risks
著者
書誌事項
Assessment and control of software risks
(Yourdon Press computing series)
Yourdon Press, c1994
大学図書館所蔵 全7件
  青森
  岩手
  宮城
  秋田
  山形
  福島
  茨城
  栃木
  群馬
  埼玉
  千葉
  東京
  神奈川
  新潟
  富山
  石川
  福井
  山梨
  長野
  岐阜
  静岡
  愛知
  三重
  滋賀
  京都
  大阪
  兵庫
  奈良
  和歌山
  鳥取
  島根
  岡山
  広島
  山口
  徳島
  香川
  愛媛
  高知
  福岡
  佐賀
  長崎
  熊本
  大分
  宮崎
  鹿児島
  沖縄
  韓国
  中国
  タイ
  イギリス
  ドイツ
  スイス
  フランス
  ベルギー
  オランダ
  スウェーデン
  ノルウェー
  アメリカ
注記
Glossary: p. 542-619
内容説明・目次
内容説明
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. MARKET: For software managers and software professionals in software engineering, software quality assurance, and related software areas.
目次
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.
「Nielsen BookData」 より