tailieunhanh - Lecture Object-oriented software engineering - Chapter 11: Managing the software process

This chapter includes contents: What is project management? software process models, cost estimation, building software engineering teams, project scheduling and tracking, contents of a project plan, difficulties and risks in project management. | Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process What is Project Management? Project management encompasses all the activities needed to plan and execute a project: Deciding what needs to be done Estimating costs Ensuring there are suitable people to undertake the project Defining responsibilities Scheduling Making arrangements for the work continued . © Lethbridge/Laganière 2005 What is Project Management? Directing Being a technical leader Reviewing and approving decisions made by others Building morale and supporting staff Monitoring and controlling Co-ordinating the work with managers of other projects Reporting Continually striving to improve the process © Lethbridge/Laganière 2005 Software Process Models Software process models are general approaches for organizing a project into activities. Help the project manager and his or her team to decide: What work should be done; In what | Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process What is Project Management? Project management encompasses all the activities needed to plan and execute a project: Deciding what needs to be done Estimating costs Ensuring there are suitable people to undertake the project Defining responsibilities Scheduling Making arrangements for the work continued . © Lethbridge/Laganière 2005 What is Project Management? Directing Being a technical leader Reviewing and approving decisions made by others Building morale and supporting staff Monitoring and controlling Co-ordinating the work with managers of other projects Reporting Continually striving to improve the process © Lethbridge/Laganière 2005 Software Process Models Software process models are general approaches for organizing a project into activities. Help the project manager and his or her team to decide: What work should be done; In what sequence to perform the work. The models should be seen as aids to thinking, not rigid prescriptions of the way to do things. Each project ends up with its own unique plan. © Lethbridge/Laganière 2005 The opportunistic approach © Lethbridge/Laganière 2005 The opportunistic approach is what occurs when an organization does not follow good engineering practices. It does not acknowledge the importance of working out the requirements and the design before implementing a system. The design of software deteriorates faster if it is not well designed. Since there are no plans, there is nothing to aim towards. There is no explicit recognition of the need for systematic testing and other forms of quality assurance. The above problems make the cost of developing and maintaining software very high. © Lethbridge/Laganière 2005 The waterfall model © Lethbridge/Laganière 2005 The waterfall model The classic way of looking at . that accounts for the importance of requirements, .