I will discuss in the blog, concepts related with portfolio management and control, reflecting objective criteria for portfolio prioritization, ROI and projects control ESTIMATION METHODSWe are going to start discussing estimations Methods for Software Development projects. Each one is applicable to specific project phase and development characteristic. At first, we are going to see, one method that is used in the very beginning of project, during requirement gathering phase.Function Point AnalysisThe Basis of Function Point analysisis the breakdown of complex systems in small pieces.Elementary operations and how datamoves through the borders of system is the core in this method.Data in motion: Handledby transactional functions or transactions. Externalinputs Data being moved from outside applications borders to inside ofapplication domain. Externaloutput take data from resting position to outside application border.Data in rest: Maintainedby the proper application is called internal logical file. Maintainedby other application is called external interface file. FPA is not recommended for: MaintenanceEFFORT. Performancesolutions.The amount FP remains the same,regardless of who develops de Software or the language software is developed. Productivity: The definition ofproductivity is the output-input ratio within a time period with dueconsideration forquality.Productivity= outputs/inputs (within a time period, quality considered)SoftwareProductivity = Function Points / Inputs Effectiveness v. Efficiency: Productivityimplies effectiveness and efficiency in individual and organizationalperformance.Effectivenessis the achievement of objectives. Efficiency is the achievement of the endswith least amount of resources. Function Points are the outputof the software development process. Function points are the unit of software.Function Points remain constant regardless who develops the software or whatlanguage the software is developed in. Function Point Counting Process: The Process starts counting information containing in thetransactions and the number of files referenced by them.Steps for evaluationof transactional function points.T1. Application documentation andtransactionrules are used to identify transactions. T2. The applicationdocumentation and transactionrules are used to determinetype of transaction (externalinput, external output, orexternal inquiry). T3. With the help ofapplication documentation(data model and transactionmodel) and transaction rules the numberdata elements and file type referenced are determined. T4. Each identified transaction isassigned a value of low, average or high based upon type, dataelements, and files referenced. T5. A distinct numerical value isassigned based upon type and value (low, average, or high). T6. All transactions are summed tocreate a transaction unadjusted function point count. Stepsfor evaluation of Files:Applicationdocumentation and file rulesare used to identify files. F2. The applicationdocumentation (transactionmodel and data model) is usedto determine type of file(either external interface fileor internal logical file). F3. With the help ofapplication documentation(data model) and file rules thenumber data elements and record element types are determined. F4. Each identified file isassigned a value of low, average or high based upon type, dataelements and record types. F5. A distinct numerical value isassigned based upon type and value (low, average, or high). F6. All files are summed tocreate a file unadjusted function point count. Independence andDependence: Since the rating of transactionsis dependent on both information contained in the transactions and the numberof files referenced, it is recommended that transactions are counted first. Atthe same time the transactions are counted a tally should be kept of all FTRs(file types referenced) that the