Your SlideShare is downloading. ×
0
Introduction to IEEE 12207  <ul><li>Information technology - Software life cycle processes
Scope: Management of Software Development Projects </li></ul><ul><li>IT project management ISO/IEC 12207
IT software projects  have a poor success record  </li><ul><li>YET !  The problems can be solved with this standard.  </li...
Concepts from the ISO/IEC/IEEE 12207 standard can help the software director and the business in general to achieve greate...
Knowledge from Standards & books: <ul><ul><ul><li>IEEE Standard 12207:2008, Information Technology - Software Life Cycle P...
IEEE Standard 1062,  Recommended practice for software acquisition
IEEE Standard 1058,  Standard for software project management plans </li></ul><li>Books </li><ul><li>Software engineering ...
Software Engineering by IAN Sommerville </li></ul></ul></ul>
Professionalism and Economics <ul><li>SW requirements
SW design
SW construction
SW testing
SW maintenance </li></ul>
IT and software  <ul><li>Just about every modern product or service depends on software </li><ul><li>Software intensive pr...
As wide as the World Wide Web
transportation of all kinds
financial markets </li></ul></ul></ul>
Software competence <ul><li>Companies dependent on IT projects need to  master the software technology to stay competitive
Produce quality products that satisfies user needs
Meet committed costs
Meet the planned schedules </li></ul>
Known Disadvantage <ul><li>70 - 80 % of companies do not have a process able to support the demands of  project control  <...
What is software engineering? <ul><li>Software engineering is concerned with applying scientific principles and management...
money,
technology,
quality,
business. </li></ul></ul></ul>
Software Engineering <ul><li>Business
Money
Technology
Quality
Time </li></ul><ul>Profit Budget Platform & Domain Reliability Schedule </ul>
Why are software projects difficult ? <ul><li>Invisible product
Lack of physical constraints
Inadequate systems engineering
Upcoming SlideShare
Loading in...5
×

IEEE 12207

7,334

Published on

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

Published in: Design, Technology, Business
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total Views
7,334
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
240
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Transcript of "IEEE 12207"

  1. 1. Introduction to IEEE 12207 <ul><li>Information technology - Software life cycle processes
  2. 2. Scope: Management of Software Development Projects </li></ul><ul><li>IT project management ISO/IEC 12207
  3. 3. IT software projects have a poor success record </li><ul><li>YET ! The problems can be solved with this standard. </li></ul></ul>
  4. 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
  5. 5. Knowledge from Standards & books: <ul><ul><ul><li>IEEE Standard 12207:2008, Information Technology - Software Life Cycle Processes
  6. 6. IEEE Standard 1062, Recommended practice for software acquisition
  7. 7. IEEE Standard 1058, Standard for software project management plans </li></ul><li>Books </li><ul><li>Software engineering project management, Edited by R. Thayer, IEEE Computer Society, 1997.
  8. 8. Software Engineering by IAN Sommerville </li></ul></ul></ul>
  9. 9. Professionalism and Economics <ul><li>SW requirements
  10. 10. SW design
  11. 11. SW construction
  12. 12. SW testing
  13. 13. SW maintenance </li></ul>
  14. 14. IT and software <ul><li>Just about every modern product or service depends on software </li><ul><li>Software intensive products/services include: </li><ul><li>As local as embedded software
  15. 15. As wide as the World Wide Web
  16. 16. transportation of all kinds
  17. 17. financial markets </li></ul></ul></ul>
  18. 18. Software competence <ul><li>Companies dependent on IT projects need to master the software technology to stay competitive
  19. 19. Produce quality products that satisfies user needs
  20. 20. Meet committed costs
  21. 21. Meet the planned schedules </li></ul>
  22. 22. Known Disadvantage <ul><li>70 - 80 % of companies do not have a process able to support the demands of project control </li></ul>
  23. 23. What is software engineering? <ul><li>Software engineering is concerned with applying scientific principles and management skills to develop software intensive systems and products for use by society within the constraints of: </li><ul><ul><li>Time,
  24. 24. money,
  25. 25. technology,
  26. 26. quality,
  27. 27. business. </li></ul></ul></ul>
  28. 28. Software Engineering <ul><li>Business
  29. 29. Money
  30. 30. Technology
  31. 31. Quality
  32. 32. Time </li></ul><ul>Profit Budget Platform & Domain Reliability Schedule </ul>
  33. 33. Why are software projects difficult ? <ul><li>Invisible product
  34. 34. Lack of physical constraints
  35. 35. Inadequate systems engineering
  36. 36. Changing requirements
  37. 37. Co-ordination of intellect-intensive teams
  38. 38. Insufficient technical staff
  39. 39. Lack of project management skills </li></ul>
  40. 40. Project Failure Reasons <ul><li>Major Issues </li></ul>PLANNING CONTROL
  41. 41. Project Failure Reasons PLANNING: <ul><li>Software requirements - not clear
  42. 42. Cost & schedule estimation - difficult
  43. 43. Projects function - not planned
  44. 44. CM, QA, computing facilities
  45. 45. Planning viewed as “non-productive” </li></ul>
  46. 46. Project Failure Reasons CONTROL: <ul><li>poor methods for tracking progress
  47. 47. poor indicators to measure </li><ul><li>Productivity
  48. 48. Quality
  49. 49. Time </li></ul></ul>
  50. 50. Quotes <ul><ul><li>“ IN MANY WAYS, MANAGING A COMPUTER PROGRAMMING PROJECT IS LIKE MANAGING ANY OTHER UNDERTAKING - IN MORE WAYS THAN MOST PROGRAMMERS BELIEVE.
  51. 51. BUT IN MANY OTHER WAYS IT IS DIFFERENT - IN MORE WAYS THAN MOST PROFESIONAL MANAGERS EXPECT ”
  52. 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. 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. “ </li></ul></ul>
  54. 54. ‘Interim Report to the President’, August, 1998 <ul><li>Software remains a major cause of system failures
  55. 55. Complexity is growing
  56. 56. Keeping up with new techniques & procedures ? </li></ul>
  57. 57. Software engineering foundation Two types of software projects ( IEE12207) <ul><li>Development </li><ul><li>Developing or modifying a software-intensive system to meet contractual requirements (satisfies user needs ) </li></ul><li>Acquisition </li><ul><li>Contractually obtaining from a group ( supplier), a software-intensive system for use by another group (user) </li></ul></ul>
  58. 58. What is IEEE 12207 ? <ul><li>The major world-wide standard for software related processes activities and tasks
  59. 59. Tailored for any organization or project
  60. 60. High level process architecture
  61. 61. An ‘inventory’ of processes from which to choose
  62. 62. For the first time a world wide agreement on what activities make up a software project </li></ul>
  63. 63. 12207 Concepts <ul>Process Architecture <ul><li>Modular: Handle all types of projects
  64. 64. Cohesion: One process for one major function
  65. 65. Responsibility: One process for one party </li></ul></ul>
  66. 66. Defining the project strategy <ul><li>The first step is to choose/tailor a project life cycle by choosing the appropriate set of processes defined in ISO/IEC 12207 </li><ul><li>Waterfall,
  67. 67. Iterative,
  68. 68. Rapid Application Development,
  69. 69. Incremental </li></ul></ul>
  70. 70. Initiation - selecting a project <ul><li>Requirements
  71. 71. Organization policy & methods
  72. 72. Legal Needs
  73. 73. Time
  74. 74. Process Standard
  75. 75. Life Cycle Model </li></ul><ul><li>Project Life Cycle
  76. 76. Project Plan
  77. 77. Contract </li></ul>Start Project
  78. 78. Project Processes
  79. 79. Major Parties
  80. 80. The Acquisition Process <ul><li>Defines the activities of the acquirer,the organization that acquirers a system, software product or software service
  81. 81. 1. Initiation
  82. 82. 2. RFP ( tender) preparation
  83. 83. 3. Contract preparation and update
  84. 84. 4. Supplier monitoring
  85. 85. 5. Acceptance and completion </li></ul>
  86. 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
  87. 87. Management process <ul>Activities: <li>Initiation and scope definition
  88. 88. Planning
  89. 89. Execution and control
  90. 90. Review and evaluation
  91. 91. Closure </li></ul><ul>“ The purpose of the management process is to organize, monitor and control the initiation and performance of any processes or functions within the organization to achieve their goals and the business goals of the organization in an effective manner” </ul>
  92. 92. Infrastructure process <ul>Objectives: <li>establish and maintain a well-defined software engineering environment (SEE)
  93. 93. tailor the SEE top the needs of the project
  94. 94. develop a SEE that supports project team members
  95. 95. implement a defined and deployed strategy for reuse </li></ul><ul>“ The purpose of the infrastructure process is to maintain a stable and reliable infrastructure that is needed to support the performance of any other process. .. May include hardware, software, methods, tools, techniques, standards, facilities for development, operation, or maintenance.” </ul>
  96. 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. 97. Supporting processes PROJECT LIFE CYCLE Documentation Verification Configuration Management Validation Quality Assurance Joint Review Problem Resolution Audit
  98. 98. Quality Assurance (QA) <ul>Objectives : <li>identify, plan and schedule QA activities
  99. 99. identify quality standards, methods and tools
  100. 100. identify resources and responsibilities
  101. 101. establish and guarantee independence of those..
  102. 102. perform the QA activities
  103. 103. apply organizational quality management systems </li></ul><ul>“ The purpose of the quality assurance process is to provide assurance that work products and processes comply with their specified requirements and adhere to their established plan”. </ul>
  104. 104. Configuration Management Objectives: <ul><li>identify, define and control all relevant items
  105. 105. control modifications
  106. 106. record and report status
  107. 107. ensure completeness of items
  108. 108. control storage handling , release and delivery </li></ul>“The purpose of configuration management is to establish and maintain the integrity of the work products of a process or product”.
  109. 109. Making a Project a Success Planning <ul><li>1. Requirements engineering </li><ul><li>documented
  110. 110. traceability </li></ul><li>2. Task, cost and schedule determination based on requirements
  111. 111. 3. Risk management, with problem tracking
  112. 112. 4. Incremental development </li></ul>
  113. 113. Making a Project a Success Control 5. Work packages with visible progress measurement <ul><ul><li>WBS, Work package specifications
  114. 114. Earned value tracking </li></ul><li>6. Software metrics; </li><ul><li>size, efforts, schedule, quality </li></ul><li>7. Software configuration management
  115. 115. 8. Software quality assurance and standards
  116. 116. 9. Peer reviews (walk through and inspections)
  117. 117. 10. Independent verification and validation
  118. 118. 11. Software engineering assessments and capability evaluation </li></ul>
  119. 119. Implement the 11 techniques above rigorously on a software IT project - every chance for success
  120. 120. Outlook for the future <ul><li>Range of team skills on software projects: </li><ul><li>Licensed Software Engineers
  121. 121. Certified software practitioners
  122. 122. Skilled software workers </li></ul><li>A stable Software Engineering Model
  123. 123. A doubling of software workers </li><ul><li>10 today to 50 or 100 in the future
  124. 124. with an adequate level of competence </li></ul></ul>
  125. 125. Conclusions <ul><li>12207 provides a reference point for all types of IT projects containing software
  126. 126. It demands good PM practices
  127. 127. A basis for establishing a mature and successful process
  128. 128. A road map for process and project improvements </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×