Page 82 -

PA R T

Two

MANAGING

SOFTWARE PROJECTS

n this part of Software Engineering: A Practitioner’s Approach, we
consider the management techniques required to plan, organ-
Iize, monitor, and control software projects. In the chapters that
follow, you’ll get answers to the following questions:

• How must the people, process, and problem be managed
during a software project?

• What are software metrics and how can they be used to
manage a software project and the software process?

• How does a software team generate reliable estimates of
effort, cost, and project duration?

• What techniques can be used to formally assess the risks
that can have an impact on project success?

• How does a software project manager select the set of
software engineering work tasks?

• How is a project schedule created?
• How is quality defined so that it can be controlled?
• What is software quality assurance?
• Why are formal technical reviews so important?
• How is change managed during the development of
computer software and after delivery to the customer?

Once these questions are answered, you’ll be better prepared to
manage software projects in a way that will lead to timely delivery
of a high-quality product.

53