The TCF is refines the UFP by considering fourteen other parameters like high transaction rate, throughput, the response time requirement etc. Where UFP stands for unadjusted function point.Īfter calculation of the unadjusted function point (UFP), the technical complexity factor (TCF) is computed. UFP= (Number of inputs)*4 + (Number of outputs) * 5 + (Number of inquiries) * 4 + (Number of files) * 10 + ( Number of Interfaces) * 10.
FP metric defines that the size of a software product depend upon the number of basic functions that the software performs along with the number of files and the number of interfaces.īesides using the number of input and out put data values, function point metric computes the size of a software product in units of function points (FPs) using other characteristics of the product as shown below. The concept of the function point metric is that the size of a software product is directly dependent of the number of different functions and features it supports. It is difficult to accurately estimate the LOC in the final product from the problem specification.įunction point approach can be used to easily estimate the size of a software product directly from the problem specification. LOC metric measures the lexical complexity of a program and does not address the more important and subtle issues of logical or structural complexity. LOC metric penalizes use of higher-level programming languages. LOC measure correlates poorly with the quality and efficiency of the code. where as LOC only focuses on coding part.
A good problem size measure should consider the overall complexity of the problem and the effort need to solve it that is it need to consider the total effort needed to specify design, coding, testing etc. Shortcomings of LOC approach: LOC gives a numerical value of problem size that can vary widely with individual coding style. Function Point.ġ0 Lines of code: To determine the LOC at the very beginning of a project, the project manager divides the whole project into modules and each module into sub module and so on until the size of the different leaf-level modules can be approximately predicted. Broadly two types of metrics are widely used to estimate the size of a product. Delivery, installation and maintenance plan.Ī project size is a measure of the problem complexity in terms of the effort and time required to develop the product. Project tracking and control plan: Miscellaneous Plans Process tailoring. Management reporting.Ĩ Software Project Management Plan Document continued. Effort, resource, cost and project duration estimation.ħ Software Project Management Plan Document continued. Project Estimation: Historical data used. Organization of the SPMP ducument: Introduction: Objectives. SPMP document is prepared by the project manager after the completion of the project planning. Miscellaneous plans such as quality assurance plan, configuration management plan etc.ĥ Precedence ordering among project planning activities.Įffort Estimation Cost Estimation Size Estimation Scheduling Duration Estimation Project staffingĦ Software Project Management Plan Document: Risk identification, analysis and abatement planning. Scheduling man power and other resources.
Estimating some basic attributes of the project like cost, duration and effort. Team building.Ĥ Project Planning: Project planning consists of the following essential activities. Tracking and controlling the progress of the project. Good communication skills and the ability to get work done. Good grasp of the latest software project management techniques. Good qualitative judgment and decision making capabilities.
Managerial report writing.ģ Skills necessary for software project management: Job Responsibilities of a software project manager: Project proposal writing. 2 Introduction: The main job of software project management is to enable a group of software engineers to work efficiently towards successful completion of the project.