1 / 30

Use Case Point Estimation

Use Case Point Estimation. Nguyen Mai Himanshu Saxena Lucas Grossi. Precarious Eclipse. Technical Risks are addressed too late. Scope is poorly defined, will change effecting progress of project. Expert judgments are used invariably. Data from delivered project is seldom used. .

tariq
Télécharger la présentation

Use Case Point Estimation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Use Case Point Estimation Nguyen Mai Himanshu Saxena Lucas Grossi Use Case Point Estimation

  2. Precarious Eclipse Technical Risks are addressed too late. Scope is poorly defined, will change effecting progress of project. Expert judgments are used invariably. Data from delivered project is seldom used. The Problem [3] Use Case Point Estimation

  3. Potential Solution – Our Perspective Use Case Point Estimation

  4. Agenda Use Case Point Estimation

  5. Use cases tries to provide an approximate answer to the right question. – which according to John Tukey is far better than exact answer to approximate question. • Can provide estimates earlier in SDLC. • Before architectural decisions are made • Before implementation. • Use Cases provide user-specific perspective to requirements and have been a successful way to explore the requirements. • Use case models are used in OO analysis for capturing and describing functional requirements of a system. Use Cases Use Case Point Estimation

  6. Describe the typical interactions between the users of a system and the system itself. • Specify a form of requirements of what the system has to do (remember, only what, not how). • Rules: • related to at least one actor • has an initiator (i.e. an actor) • leads to a relevant result (a result with “business value”) Use Cases

  7. Use Case Point Estimation – Process Use Case Point Estimation

  8. The UCP equation is composed of four variables: • - Unadjusted Use Case Point (UUCP) • - The Technical Complexity Factor (TCF) • - The Environment Complexity Factor (ECF) • - The Productivity Factor (PF) UCP = UUCP * TCF * ECF * PF • UUCP is the sum of Unadjusted Actor Weight (UAW) and Unadjusted Use Case Weight (UUCW). UUCP = UAW + UUCW Use Case Point Estimation [4] Use Case Point Estimation

  9. Unadjusted Actor Weight Actor initiates an interaction with the system to accomplish some goals. Does not represent the physical people or systems, but their role. Use Case Point Estimation

  10. Unadjusted Use Case Weight Based on the total number of activities contained in all the use case scenarios does not represent the physical people or systems, but their role. Use Case Point Estimation

  11. Technical Complexity Factor - TCF Use Case Point Estimation

  12. Technical Complexity Factor (TCF) Each factor is given a perceived complexity value from 0 to 5 according to its impact Technical Total Factor is computed as the sum of all the weights multiplied by their corresponding perceived values Technical Complexity Factor (TCF): TCF = 0.6 + (0.01*Technical Total Factor) Use Case Point Estimation

  13. Environment Complexity Factor - ECF Reflects the development team’s experience ECF = 1.4 + (-0.03*Environment Total Factor) Environment Total Factor is the sum of each factor weight multiplied by the perceived value Use Case Point Estimation

  14. Productivity Factor (PF) Convert the UCP number into meaningful value in terms of man-hours required. The value may range from 16 to 30 man-hour/UCP. Use Case Point Estimation

  15. Sales scenario Case Study

  16. Component Manipulation Scenario

  17. PC Manipulation Scenario

  18. Use Case Actors Use Case Weights Results Use Case Point Estimation

  19. Technical Complexity Factor - TCF Use Case Point Estimation

  20. Use Case Point Estimation

  21. Use Case Point Estimation

  22. Factors Estimate • Technical Complexity Factor • TCF = 0.6 + (0.01 x Total Technical Factors) • TCF = 0.6 + (0.01 x 35) • TCF = 0.95 • Environmental Complexity Factor • ECF = 1.4 + (-0.03 x Total Environmental Factors) • ECF = 1.4 + (-0.03 x 22.5) • ECF = 0.725 • Unadjusted Use Case Points • UUCP = UAW + UUCW • UUCP = 19 + 125 • UUCP = 144 Use Case Points • UCP = UUCP x TCF x ECF • UCP = 144 x 0.95 x 0.725 • UCP = 99.18 use case points • Estimate = UCP x PF • Estimate = 99.18 x 20 • Estimate = 1983.6 man hours PC – Geek Final Results Use Case Point Estimation

  23. Understandability • Easy to learn and quick to apply. • Versatile and extensible for different flavors of development and testing projects. • Well Suited • When the complexity of the system resides in the interaction between the actor and system. • Objected Oriented Applications / Systems. • Development time is too short. e.g. Web Applications. • Management intends to have an early project estimate for planning. Positives Use Case Point Estimation

  24. Use Cases have some limitations. E.g. flight reservation system, UCPM will be unsuitable for such applications. • Many variations in Use Case specifications formalities and styles • Syntax and Semantics to describe Use Case Models and scenarios are incomplete and not precise. • Heuristics and rules are still missing which define the right degree of detail imperative for correct estimation. • There is no use case point standard. Therefore, it is difficult to use case point values across companies. Drawbacks Use Case Point Estimation

  25. Results Lessons Learnt • Promising Results for UCPM. • Use Case can be used successfully in conjunction with expert estimates. • TCF and ECF can be reused across similar projects. Industrial Case Study [5] Use Case Point Estimation

  26. What is EF Benefits EF is to use the past experiences and since we believe that the effort estimates of old projects in more accurate definitions of new estimates. • With experience we will develop sensible heuristics. • The availability of data from previous projects will contribute to the accuracy of estimates • Reuse of TCF and ECF as they remain constant across similar projects. Experience Factory [6] Use Case Point Estimation

  27. Experience Base Support Analyze Package Use Case Point Estimation

  28. There is no secret formula which will work for everything. • UCPM has the potential to become a mature and widely accepted estimation tool like FP. • It can have significant impact when used with other estimates like expert knowledge. • Further Studies are required for precision of UCPM in different kinds of projects. • Improvements in dimension of solving the problem areas can help making it a success. Conclusions Use Case Point Estimation

  29. [1]Presentation, Gem-Up Consulting.www.gem-up.com • [2] Webpage, Microsoft Office Project, http://office.microsoft.com/en-us/project/HA010211801033.aspx • [3]Presentations, Lamri Ltd, www.lamri.com • [4]Article, Project Estimation With Use Case Points .Clemmons. • [5]Paper, estimating Software Development Effort Based on Use Cases – Experiences from Industry. • [6]Paper, Experience Factory to Improve Software Development Effort Estimation.Koloski References Use Case Point Estimation

  30. Questions. Use Case Point Estimation

More Related