It is the management process for the creation of a system or software, which contains a set of activities, one of which is the estimate, estimate is to look at the future and accept some uncertainty resigned. Although the estimate is more an art than a science, is an important activity that should not be done carelessly. There are useful techniques for estimating time costs. And since the estimate is the basis of all other project planning activities and serves as a good guide for Systems and Software Engineering.
In estimating we consider not only the technical process used in the project, but takes into account the resources, costs and planning. The project size is another important factor that can affect the accuracy of the estimates. As the size increases, rapidly growing interdependence between various software elements. The availability of historical information is another element that determines the risk of the estimate.
Millennium Project Planning
The purpose of Software Project Planning is to provide a framework that allows the manager to make reasonable estimates of resources and time planning costs. These estimates are made within a limited time frame at the beginning of a software project, and should be updated regularly as the project progresses. Estimates should also define the best case scenario, and worst case, so that the results of the project can be limited. The planning objective is achieved through a process of discovery of information leading to reasonable estimates (Wasson, 2006).
Activities associated with the software project.
Scope of the Software
This is the first activity undertaken during project planning software. At this stage it must evaluate the function and performance allocated to software for the Computer System Engineering to establish a scope of project that is not ambiguous, and incomprehensible to managers and technicians. Describes the function, performance, constraints, interfaces and reliability functions are evaluated in the field and in some cases are refined to give more details before the start of the estimate. Restrictions include performance requirements and processing response time, identify the boundaries of the software caused by external hardware, by available memory and other existing systems (Wasson, 2006).
The area is defined as a pre-requisite for the estimation and there are some elements that should be taken into account such as: Obtaining the necessary information for the software. To this analyst and meet customer expectations on the project and agree on the points of interest for its development.
Resources
The second task of the software development planning is to estimate the resources required undertaking the software development effort, this simulates a pyramid where the tools (hardware and software) are based infrastructure provides support to the effort development, second level of the pyramid is the reusable components. And in the highest part of the pyramid is the primary resource, people (human resources) (Siau, Erickson, 2009).
Each resource is specified by four characteristics:
Description of Appeal.
Availability reports.
Chronological date on which the resource is required.