LlosengCh11E2

LlosengCh11E2 - Object-Oriented Software Engineering...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
© Lethbridge/Laganière 2005 Chapter 11: Managing the Software Process 2 11.1 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 . ..
Background image of page 2
© Lethbridge/Laganière 2005 Chapter 11: Managing the Software Process 3 What is Project Management? Directing Being a technical leader Reviewing and approving decisions made by others Building morale and supporting staff Monitoring and controlling Coordinating the work with managers of other projects Reporting Continually striving to improve the process
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
© Lethbridge/Laganière 2005 Chapter 11: Managing the Software Process 4 11.2 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.
Background image of page 4
© Lethbridge/Laganière 2005 Chapter 11: Managing the Software Process 5 The opportunistic approach Think of Idea for Improvement Modify Until Satisfied First Prototype
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
© Lethbridge/Laganière 2005 Chapter 11: Managing the Software Process 6 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.
Background image of page 6
© Lethbridge/Laganière 2005 Chapter 11: Managing the Software Process 7 The waterfall model
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 11: Managing the Software Process 8 The waterfall model The classic way of looking at software engineering that accounts for the importance of requirements, design and quality assurance. The model suggests that software engineers should work in a series of stages. Before completing each stage, they should perform quality assurance (verification and validation).
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 52

LlosengCh11E2 - Object-Oriented Software Engineering...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online