Concepts from the ISO/IEC 12207 standard can help the software director and the business in general to achieve greater success with their employees

4. Concepts from the ISO/IEC/IEEE 12207 standard can help the software director and the business in general to achieve greater success with their employees

6. IEEE Standard 1062, Recommended practice for software acquisition

8. Software Engineering by IAN Sommerville

10. SW design

11. SW construction

12. SW testing

13. SW maintenance

15. As wide as the World Wide Web

16. transportation of all kinds

17. financial markets

19. Produce quality products that satisfies user needs

20. Meet committed costs

21. Meet the planned schedules

24. money,

25. technology,

26. quality,

27. business.

29. Money

30. Technology

31. Quality

34. Lack of physical constraints

35. Inadequate systems engineering

36. Changing requirements

37. Co-ordination of intellect-intensive teams

38. Insufficient technical staff

39. Lack of project management skills

42. Cost & schedule estimation - difficult

43. Projects function - not planned

44. CM, QA, computing facilities

45. Planning viewed as “non-productive”

48. Quality

49. Time

51. BUT IN MANY OTHER WAYS IT IS DIFFERENT - IN MORE WAYS THAN MOST PROFESIONAL MANAGERS EXPECT ”

52. “ .. the demand for software has grown at such an explosive rate, it now far outweighs the resources we have to produce it. ….. desperately needed software is not being developed…….. “

53. “ An interaction of factors has caused this ‘software gap’: accelerated demand for software, increased complexity of systems,labor shortages, and lack of adequate science and technology to support robust development. “

55. Complexity is growing

56. Keeping up with new techniques & procedures ?

59. Tailored for any organization or project

60. High level process architecture

61. An ‘inventory’ of processes from which to choose

62. For the first time a world wide agreement on what activities make up a software project

64. Cohesion: One process for one major function

65. Responsibility: One process for one party

67. Iterative,

68. Rapid Application Development,

69. Incremental

71. Organization policy & methods

72. Legal Needs

73. Time

74. Process Standard

76. Project Plan

77. Contract Start Project

78. Project Processes

79. Major Parties

81. 1. Initiation

82. 2. RFP ( tender) preparation

83. 3. Contract preparation and update

84. 4. Supplier monitoring

85. 5. Acceptance and completion

86. Organizational processes PROJECT LIFE CYCLE Employed by organization to establish and implement an underlying structure of .. Processes and personnel, and continuously improve the structure and processes MANAGEMENT IMPROVEMENT INFRASTRUCTURE TRAINING

88. Planning

89. Execution and control

90. Review and evaluation

93. tailor the SEE top the needs of the project

94. develop a SEE that supports project team members

96. Management & Infrastructure process standards IEEE Std 982.1 - Standard dictionary of measures to produce reliable software IEEE Std 1045 - Software productivity metrics IEEE Std 1058 - Software project management plans IEEE Std 1045 - Recommended practice for the adoption of CASE tools ISO/IEC 14102 - Guidelines for the evaluation and selection of CASE tools Above Standards provide the detail of what to do

97. Supporting processes PROJECT LIFE CYCLE Documentation Verification Configuration Management Validation Quality Assurance Joint Review Problem Resolution Audit

99. identify quality standards, methods and tools

100. identify resources and responsibilities

101. establish and guarantee independence of those..

102. perform the QA activities

105. control modifications

106. record and report status

107. ensure completeness of items

108. control storage handling , release and delivery “The purpose of configuration management is to establish and maintain the integrity of the work products of a process or product”.

111. 3. Risk management, with problem tracking

112. 4. Incremental development

115. 8. Software quality assurance and standards

116. 9. Peer reviews (walk through and inspections)

117. 10. Independent verification and validation

118. 11. Software engineering assessments and capability evaluation

119. Implement the 11 techniques above rigorously on a software IT project - every chance for success

121. Certified software practitioners

124. with an adequate level of competence

126. It demands good PM practices

127. A basis for establishing a mature and successful process

128. A road map for process and project improvements