Question

What are two (2) main limitations of empirically based software estimation models? Name three (3) such models. Outline three (3) particular limitations of function point based estimation.

Answer 1

limitations of empirically based software estimation models

a. Models neglect requirements and all documentation work.
b. It neglect customer knowledge, skills and cooperation,
c. It more clear the impact of security view.
d. It neglect hardware issues

Models

1. COCOMO:

Cocomo (Constructive Cost Model) is a regression model dependent on LOC, i.e number of Lines of Code. It is a procedural cost gauge model for software projects and frequently utilized as a procedure of dependably anticipating the different parameters related with making a project, for example, size, effort, cost, time and quality. It was proposed by Barry Boehm in 1970 and depends on the investigation of 63 projects, which make it a standout amongst the best-reported models.

The key parameters which characterize the quality of any software products, which are additionally a result of the Cocomo are fundamentally Effort and Schedule:

Effort: Amount of work that will be required to finish an undertaking. It is estimated face to face months units.

Schedule: Simply implies the measure of time required for the finishing of the activity, which is, obviously, corresponding to the effort put. It is estimated in the units of time, for example, weeks, months.

Function Point Analysis

FPA gives standardized technique to functionally size the software work product. This work product is the yield of software new advancement and improvement projects for consequent discharges. It is the software which is migrated to the production application at project usage. It quantifies functionality from the clients point of view for example based on what the client demands and gets consequently.

Function Point Analysis (FPA) is a technique or set of principles of Functional Size Measurement. It surveys the functionality conveyed to its clients, in light of the client's outside view of the functional requirements. It quantifies the consistent view of an application not the physically executed view or the internal technical view.

The Constructive Systems Engineering Cost Model

The Constructive Systems Engineering Cost Model (COSYSMO) was made by Ricardo Valerdi while at the University of Southern California Center for Software Engineering. It gives a gauge of the quantity of individual months it will take to staff systems engineering assets on equipment and software projects. At first created in 2002, the model currently contains an adjustment informational index of in excess of 50 projects given by real aviation and safeguard organizations, for example, Raytheon, Northrop Grumman, Lockheed Martin, SAIC, General Dynamics, and BAE Systems.

Like its antecedent COCOMO, COSYSMO processes effort (and cost) as a function of framework functional size and modifies it dependent on various ecological components identified with systems engineering.

limitation FP

1. It needs abstract assessments with a great deal of judgment included.

2. Numerous effort and cost models depend on LOC, so function points should be changed over.

3. Less research information is accessible on function points when contrasted with LOC.

4. It is performed after production of plan particulars.

5. It has low exactness of assessing as an emotional judgment is included.

6. As the expectation to learn and adapt is very long it is difficult to pick up profiency.

7. It is a time expending strategy.