Estimation Techniques That Are Used by Different Projects
Order ID:89JHGSJE83839 Style:APA/MLA/Harvard/Chicago Pages:5-10 Instructions:
Estimation Techniques That Are Used by Different Projects
The Estimating Problem
Subscribe 1Q)How many different estimating techniques were discussed in the case?
ans)there are multiple estimation techniques that are used by different projects in different organizations. They are
1.Source line of Code(SLOC): it is used to measure the size of a software program by counting the number of lines in the text of the programs source code we need to divide the problem into modules and each module into sub modules, and so on until the sizes of the different leaf-level modules can be approximately predicted.two major types of SLOC measures.
1.Physical SLOC: it is a count of lines in the text of the programs source code including commentlines
2.Logical SLOC: attempts to measure the number of executable statements eg:KLOC.i.e. 1000 lines of code
2.Function Point(FP): Function count measure functionally from user point of view. The base of the function count is what the user requests and what user receives in return from the system.
Quantitative (Objective): measure and industry data is available as basis of comparison. 5 key components
1.External input 2. External output 3.External inquiries 4.Internal logical files 5.External interface files
3.Use Case Point: An estimation method that provides the ability to estimate an applications size and effort from its use cases.
UCP analyzes the use case actors, scenarios and various technical and environmental factors and abstracts them into an eqation.
UCP = TCP*ECF*UUCP*PF eg: UCP = 1.07*0.62*264*20 = 3503 hours
Technical complexity factor(TCF)
Environment Complexity factor(ECF)
Unadjusted use case points (UUCP)
Productivity Factor(PF)
4.Story Point:A story point is a relative measure of complexity instead of effort of a user story in agile estimation and planning. if the second story is twice as complex as previous one we give it a value of twice points.
Planning poker(Scrum):cards of 0,1/2, 1,2,3,5,8,13,20,50 used by the team for discussing the size.
the planning Game(xp): each story(written on index cards) is given an estimate of 1,2 or 3 weeks. This process is repeated continuously throughout the project.
RUBRIC
Excellent Quality
95-100%
Introduction 45-41 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Literature Support
91-84 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Methodology
58-53 points
Content is well-organized with headings for each slide and bulleted lists to group related material as needed. Use of font, color, graphics, effects, etc. to enhance readability and presentation content is excellent. Length requirements of 10 slides/pages or less is met.
Average Score
50-85%
40-38 points
More depth/detail for the background and significance is needed, or the research detail is not clear. No search history information is provided.
83-76 points
Review of relevant theoretical literature is evident, but there is little integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are included. Summary of information presented is included. Conclusion may not contain a biblical integration.
52-49 points
Content is somewhat organized, but no structure is apparent. The use of font, color, graphics, effects, etc. is occasionally detracting to the presentation content. Length requirements may not be met.
Poor Quality
0-45%
37-1 points
The background and/or significance are missing. No search history information is provided.
75-1 points
Review of relevant theoretical literature is evident, but there is no integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are not included in the summary of information presented. Conclusion does not contain a biblical integration.
48-1 points
There is no clear or logical organizational structure. No logical sequence is apparent. The use of font, color, graphics, effects etc. is often detracting to the presentation content. Length requirements may not be met
You Can Also Place the Order at www.collegepaper.us/orders/ordernow or www.crucialessay.com/orders/ordernow Estimation Techniques That Are Used by Different Projects