The first step in the project estimate (estimated) is to link demand and software product size. You can vary according to article
This requirement, graphics analysis model, prototype or user interface design to estimate the size of the product. Although not finished
Good metrics, but here, some common metrics are given:
• How many function points and feature points (Jones 1996B), or the number of 3 - D function points (Whitmire 1995). • The number, type, and complexity of the graphical user interface (G u i) element. • The number of rows used to achieve specific requirements. • The number of object classes or the measurement of other object-oriented systems (Whitmire 1997). • Single tonable demand (Wilson 1995).
Valicity and uncertain demand will definitely cause uncertainty in software size estimates, causing your work
Quantity and progress schedule estimate estimate. Because the uncertainty of demand is inevitable because the uncertainty in the project is inevitable, so
In progress arrangements, temporary events should be included and the budget funds should be budget funds to accommodate additional requirements and possible overrun.
