Plan driven development plan driven or plan based

This preview shows page 9 - 16 out of 53 pages.

Plan-driven development Plan-driven or plan-based development is an approach to software engineering where the development process is planned in detail. Plan-driven development is based on engineering project management techniques and is the ‘traditional’ way of managing large software development projects. A project plan is created that records the work to be done, who will do it, the development schedule and the work products. Managers use the plan to support project decision making and as a way of measuring progress.
Plan-driven development pros and cons The arguments in favor of a plan-driven approach are that early planning allows organizational issues (availability of staff, other projects, etc.) to be closely taken into account, and that potential problems and dependencies are discovered before the project starts, rather than once the project is underway. The principal argument against plan-driven development is that many early decisions have to be revised because of changes to the environment in which the software is to be developed and used.
Project plans In a plan-driven development project, a project plan sets out the resources available to the project, the work breakdown and a schedule for carrying out the work. Plan sections Introduction objectives, constraint Project organization the team, the people and their roles Risk analysis possibilities, the likelihood to arise, the strategies Hardware and software resource requirements Work breakdown activities, milestone and deliverables Project schedule time and allocation of people Monitoring and reporting mechanisms
Project plan supplements Plan Description Quality plan Describes the quality procedures and standards that will be used in a project. Validation plan Describes the approach, resources, and schedule used for system validation. Configuration management plan Describes the configuration management procedures and structures to be used. Maintenance plan Predicts the maintenance requirements, costs, and effort. Staff development plan Describes how the skills and experience of the project team members will be developed.
The planning process Project planning is an iterative process that starts when you create an initial project plan during the project startup phase. Plan changes are inevitable. As more information about the system and the project team becomes available during the project, you should regularly revise the plan to reflect requirements, schedule and risk changes. Changing business goals also leads to changes in project plans. As business goals change, this could affect all projects, which may then have to be re-planned.
The project planning process
Project scheduling Project scheduling is the process of deciding how the work in a project will be organized as separate tasks, and when and how these tasks will be executed.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture