Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cost xpert

1,313 views

Published on

CostXpert, a project management tool.

Published in: Education, Technology
  • Be the first to comment

Cost xpert

  1. 1. GROUP MEMBERS: oAyesha Saeed oHuma Shabir oAmna Rehman oIqra Qasim oMadeha Arif
  2. 2. SUBJECT: SOFTWARE PROJECT MANAGEMENT Topic: Cost Xpert
  3. 3. INTRODUCTION By Ayesha Saeed
  4. 4. ESTIMATING SOFTWARE COSTS  More projects are doomed from poor cost and schedule estimates rather than from technical, political, or development team problems.  Software estimating can be a science, not just an art.  It really is possible to accurately and consistently estimate development costs and schedules for a wide range of projects.
  5. 5. ESTIMATING SOFTWARE COSTS      Time Cost Effort Risk Return on Investment  These project elements can describe a software development success or decry a project failure. They also frequently cause management nightmares.  Wide range of software cost estimating tools on the market to help with this process.
  6. 6. COST XPERT  Industry leading software cost estimation tool  Transform plans into concrete and quantifiable results  Cost Xpert is specially designed to help organization improve and manage processes, mitigate risks, and exceed bottom line expectations.
  7. 7. COST XPERT- ADVANTAGES  Easy to use for novices  Sophisticated features for advanced user  Integrates multiple estimating models  Most extensive options for project type, lifecycle and documentation standards  Interfaces with standard management and analysis tools
  8. 8. COMPETITIVE EDGE:  Cost Xpert Tool differentiates itself from competitors by integrating multiple estimation models into one user-friendly solution that provides the most accurate and comprehensive estimates possible.  Cost Xpert can be used to forecast any software development project, regardless of size or objective. The tool has been endorsed by both the private and public sector.
  9. 9. ALGORITHMIC COST MODELING  Cost is estimated as a mathematical function of product, project and process attributes whose values are estimated by project managers  The function is derived from a study of historical costing data  Most commonly used product attribute for cost estimation is LOC (code size)  Most models are basically similar but with different attribute values
  10. 10. COST XPERT EFFORT AND SCHEDULE CALCULATIONS Algorithmically, Cost Xpert started with the COCOMO models, Revised Enhanced Version of Intermediate COCOMO (REVIC) extensions, and then layered functionality on top of this base.
  11. 11. BY HUMA SHABBIR
  12. 12. COST EXPERT
  13. 13. PROJECT TYPE
  14. 14. PROJECT LIFECYCLE
  15. 15. FINANCIAL
  16. 16. LABOR RATES
  17. 17. LANGUAGES
  18. 18. ACTUALS
  19. 19. PROJECT INFO
  20. 20. PROJECT MEMO
  21. 21. BY AMNA RAHMAN
  22. 22. SLOC Lines of code (often referred to as Source Lines of Code, SLOC or LOC) is a software metric used to measure the amount of code in a software program.
  23. 23. FUNCTION POINTS Function Point Analysis is an objective and structured technique to measure software size on the basis of the functionality provided to the user.
  24. 24. EQUIVALENT FUNCTION POINTS Equiv Function Points=7.67*7 +46.83*10 +2*4 +27*5 +37.33*4 =814.31
  25. 25. EQUIVALENT SLOC For JAVA 2 estimated SLOC per Function Point=46 so Equivalent SLOC=46*814.31=37458.26=>37459 Lines of code
  26. 26. MEAN
  27. 27. EQUIVALENT POINTS Equiv Points=Mean Value * F.P Conversion Factor
  28. 28. STANDARD DEVIATION Std. Dev=Worst-Best 6
  29. 29. FUNCTION POINTS Function Point Analysis is an objective and structured technique to measure software size by quantifying its functionality provided to the user, based on the requirements and logical design. External interface files are files that the system creates for use by other applications, or that are created by other applications for input into this system.
  30. 30. FUNCTION POINTS Function Point Analysis is an objective and structured technique to measure software size by quantifying its functionality provided to the user, based on the requirements and logical design. Each table in a relational database would be an internal table.
  31. 31. FUNCTION POINTS Function Point Analysis is an objective and structured technique to measure software size by quantifying its functionality provided to the user, based on the requirements and logical design. External queries are functions you publish for external use (as in an API) or functions/messages from an external system that you will be using.
  32. 32. FUNCTION POINTS Function Point Analysis is an objective and structured technique to measure software size by quantifying its functionality provided to the user, based on the requirements and logical design. External outputs are reports and read only screens.
  33. 33. FUNCTION POINTS Function Point Analysis is an objective and structured technique to measure software size by quantifying its functionality provided to the user, based on the requirements and logical design. External inputs are data entry screens or dialogs.
  34. 34. INTERNET POINTS
  35. 35. DOMINO POINTS
  36. 36. UML-USE CASE POINTS Enter the best, worst and expected estimates of the number of Use Case scenarios that will be ultimately identified
  37. 37. UML CLASS METHOD Enter the best, expected and worst case estimate of the number of control classes. Control classes represent coordination and sequencing mechanisms.
  38. 38. MKII FUNCTION PTS This is a method for analysis and measurement of information processing applications based on end user functional view of the system. Data entities are logical data structures that contains information meaningful to the user. Count the Input Data Element, the Data entity Types Referenced, and the Output Data Element
  39. 39. OBJECT METRICS Enter the best, worst and expected estimates for the number of new objects (e.g. classes, components) in the system.
  40. 40. GUI METRICS Enter the best, worst and expected estimates for the number of GUI metrics used in the system. These include dialog boxes, menus, reports and windows.
  41. 41. CAPABILITY REQUIREMENTS Enter the best, worst and expected estimates for the number of new capability requirements.
  42. 42. BY MADIHA ARIF
  43. 43. BY IQRA QASIM
  44. 44. LIMITATIONS  Highly extensive estimates needs to be determined which can be complex and tedious.  For example lines of codes, number of queries & functions , working labor and working hours.  Difficult to predict at the start of project.
  45. 45. THANK YOU

×