Table of Contents:

Exercise

  • 1. Explain the concept of use case point (UCP). It is better than FP with the reference of effort estimation? (Yes /No). Justify your answer.
  • 2. Consider a project with the following functional units:
    • • Number of external interfaces = 10.
    • • Number of internal files = 12.
    • • Number of external enquiries = 13.
    • • Number of external outputs = 24.
    • • Number of external inputs = 50.

It is assumed that all the element weighting factors are simple and all complexity adjustment factors are average. The project is developed using C language. Estimate the effort required to develop the software.

  • 3. If there is an additional requirement for very high level of reliability and a high volume database is needed, then what percentage of the effort will be incremented or decremented in the previous question?
  • 4. Consider the following use case diagram:

For the use case shown in Figure 2.3, Passenger is a complex actor while others are simple. All the use cases in which Passenger is an active actor

Use case diagram for Passenger Service System

FIGURE 2.3 Use case diagram for Passenger Service System.

have average transaction and the rest use cases have simple transactions. The Assigned Value for all the Technical and Environmental Factors is 3. Calculate the Unadjusted Use Case Points (UUCP) for using the RMS. Also, calculate the total effort for developing passenger service system (PSS) if 12 man-hours per use case point will be used.

5. Consider the project with following parameters:

Class Type

Number of Classes

NEM

NSR

PDT

3

3

3

4

6

6

4

8

10

HIT

5

6

8

7

II

4

5

5

7

6

7

5

6

DMT

2

3

2

3

3

2

0

TMT

2

3

3

6

8

Assume all the technical factors have average influence. Estimate the effort using CPI.

References

Bohem, B. (1981). Software engineering economics. Englewood Cliffs, NJ: Prentice-Hall, Inc.

Chen, H. C. (1995). Machine learning for information-retrieval. Neural netw'orks, symbolic learning and genetic algorithms. Journal of the American Society for Information Science. 46(3), 194-216.

Construx Software Inc. Retrieved from http://www'.construx.com/estimate.

Fairley, Richard E. (1992). Recent Advances in Software Estimation Techniques. Woodland Park, CO: Management Associates.

International Software Benchmarking Standards Group (ISBSG). Software estimation.

Jones, C. (1996, March). Software estimating rules of thumb. Computer, Vol 29, pp. 116-118.

Kitchenham, B. (1997). Counterpoint: The problem with function points. IEEE Software, 14(2), 29.

Shepperd, Martin, Schofield, Chris, & Kitchenham, Barbara (1996). Effort estimation using analogy. IEEE Proceedings of ICSE. Berlin, Germany

Smith, J. (1999). The estimation of effort based on use cases. Rational Software(International Software White Paper).

Somerville, I. (2001). Software engineering (6th ed.). Reading, MA: Addison-Wesley Publishers Limited.

 
Source
< Prev   CONTENTS   Source   Next >