Use-Case Points for Software Size Estimation

Use-Case Points for Software Size Estimation
Slide Note
Embed
Share

This presentation delves into the use of use-case points for estimating software size in IT project management. It covers the process, benefits, resources used, rationale for topic selection, software effort estimation, defining a use case, and concluding insights.

  • Software Size Estimation
  • Use-Case Points
  • IT Project Management
  • Effort Estimation
  • Requirements Engineering

Uploaded on Mar 17, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. Use-Case Points for Estimating Software Size EECS/IT811: IT Project Management Sairath March 21, 2019

  2. Organization Introduction Conclusions 2

  3. Resources used Multiple journal article A book chapter A conference proceedings article A case study All resources shared with Professor Saiedian (on class website) 3

  4. Why I chose the use-case point topic? Addresses two topics Scope management Managing the scope of a project Managing the requirements engineering process Effort estimation is an essential part of that process Use-case point estimation is also a popular cost and effort estimation 4

  5. Software effort estimation Objective: estimate the most realistic amount of efforts to complete a project There are many methods Expert judgment Size-based models Function points Feature points Use case points COCOMO 5

  6. What is a use case? A popular approach to collecting the requirements A user-centered approach: a specific situation in which a product or service could potentially be used by a user 6

  7. Conclusions Summarize the work (1-3 slides) Provide takeaways Questions and feedback are welcome 7

More Related Content