This is a Masterer's thesis which discribes how to apply "Use Case Points Method" in estimating object-oriented software development cost. The method is based on the Function Point Analysis (FPA) and MK II Function Point Analysis. The thesis also discusses how Use Cases can be sized in alternative ways, and how to best write Use Cases for estimating purposes. An extension of the Method providing simpler counting rules is also proposed.
Type of Material:
A master's thesis in PDF format.
Research in cost estimation of software projects. After-class reading assignment for software development courses.A good supportive document that could be used in research of best teaching practices and design.
Adobe Acrobat Reader because it is a PDF file.
Identify Major Learning Goals:
1. The development of the Use Case for cost estimation of software projects. 2. Investigation of Use Case Points Method by applying the method to two industrial projects and ten students' projects. 3. Evaluation of the Method. 4. Proposal of alternating approaches to assigning complexity to arrive a correct measure. 5. This PDF thesis file would be best used in research for developing case use methodology for enterprise systems.
Target Student Population:
Prerequisite Knowledge or Skills:
Software development and cost analysis. Basic conceps on Object-Oriented Design.
This is a complete Master's thesis. It discusses the problem of Object-Oriented Software Estimation, introduces the "Use Case Points Method", and then discusses how the Method should be applied in cost estimation. Two case studies and 10 students' projects are used to test the method, and then according to the test, several alternative ways on how to best use the method is proposed and a conclusion is drawn. The article is well organized and is useful for both beginners who want to learn how to estimate software projects cost and for researchers who want to study estimation methods. Faculty often struggles with the concern of expensive software being needed to teach a topic vs. the need to balance their university's budgets. This study concludes that fancy software may not be necessary. The findings indicate that there is no obvious gain in investing in expensive commercial tools for estimating object-oriented software.
Quite a lengthy document (147 pages) to wade through. The user will need to reference other materials to fully understand the content.
Potential Effectiveness as a Teaching Tool
This paper may be used as a reading assignment in a software engineering course. It can also be used in students projects on software cost estimation as well as the thesis could be used as a research document in a systems analysis class discussing the system's development life cycle and case tools.
It's not a tutorial for software development. Students will need to possess knowledge in software development, software cost estimation, and Object-Oriented Design to fully understand the material.The paper is lengthy in discussion.
Ease of Use for Both Students and Faculty
The paper is contained in one PDF file.The document can be easily viewed in Adobe Acrobat Reader.
It's a long paper.
Search by ISBN?
It looks like you have entered an ISBN number. Would you like to search using what you have
entered as an ISBN number?
Searching for Members?
You entered an email address. Would you like to search for members? Click Yes to continue. If no, materials will be displayed first. You can refine your search with the options on the left of the results page.