Effort and Cost Estimation Using Cocomo II for “system Maintaining User Access Matrix Data for Perusahaan Xyz”
Essay Preview: Effort and Cost Estimation Using Cocomo II for “system Maintaining User Access Matrix Data for Perusahaan Xyz”
Report this essay
Effort and Cost Estimation using COCOMO II for “System Maintaining User Access Matrix Data for Perusahaan XYZ”Abstract— Estimates of essential software made by the developer to determine the effort of the application to be made in order not wrong to spend , no one uses the amount of resource , and that the application is completed on time . In this paper will be calculated effort to use Cocomo II Management System Data User Access Matrix at company XYZ , Applications UAM (User Access Matrix ) is designed to enable employees of Company XYZ to manage Data UAM , developers will be asked to fill out a questionnaire that had been prepared earlier , The application is already completed, the calculation effort is made to calculate SLOC using Unadjusted Function Point and use free tool . The result will see the difference in the effort of the two methods.Key Word— Cost estimation, COCOMO II , Unadjusted Function Point . Introduction The problems most often encountered by developers is the less precise estimate at the beginning to develop, including the problems of cost and resource overload or deficiency . Thus, the calculation of the cost becomes a very import xant thing in the development of a software product . This is because the software development process the developer should be careful in determining the cost and resource issues that will be used during the development . If the developer did well in the early estimation processing software , it can help the developer to divide the process of developing well .Before performing the cost estimate, the developer should be done is to estimate the effort for the manufacture of such software , this is because the effort is the main component that can affect the cost of the development process . There are several methods for estimating the effort , one of which is the Constructive Cost Model ( COCOMO ) . Because the software is to be calculated efforts have been completed , then the method to calculate SLOC is twofold using unadjusted Function Point ( UFP ) and using tools. The calculation of the estimated cost was conducted on a data management systems user access matrix in a company , this application is web based and uses ASP.NET , and SQL Server . This application has been created and will be compared to calculations using unadjusted Function Point ( UFP ) and tools for calculating and using COCOMO II SLOCnya to calculate the costs.TINJAUAN PUSTAKAIn this section explained how this research will be carried out and the explanation of the theory used in this study .COCOMO IICOCOMO or the Constructive Cost Model is a software cost estimation algorithm developed by Barry Boehm in 1981. This model uses regression formula basis , with parameters derived from historical data and the characteristics of the current projects .In 1981 , Barry Boehm design COCOMO to estimate the number of Person-Months in developing a software product . References in this model known as COCOMO 81. In 1990 , appeared a new estimation model called COCOMO II . In general, reference COCOMO before 1995 refer to the original COCOMO models of COCOMO 81 , then after that refer to COCOMO II . COCOMO estimation model has been used by thousands of project manager of a software project and based on the experience of hundreds of previous projects .
The COCOMO II consists of multiple attributes in a creation of the software that is 17 Effort Multipliers ( EMS ) , 5 Factors Scale ( SFS ) , Software Size ( SLOC ) , and estimates Effort . Effort Multiplier categorized into 4 parts:Product attributesRequired software reliability (RELY)Database size (DATA)Product complexity (CPLX)Developed for Reusability (RUSE)Documentation Match to Life-Cycle Needs (DOCU)Computer attributesExecution Time Constraint (TIME)Main Storage Constraint (STOR)Platform Volatility (PVOL)Personnel attributesAnalyst Capability (ACAP)Programmer Capability (PCAP)Personnel Continuity (PCON)Application Experience (APEX)Platform Experience (PLEX)Language and Tool Experience (LTEX)Project attributesUse of Software Tools (TOOL)Multisite Development (SITE)Required Development Schedule (SCED) COCOMO II formula for calculating Effort:[pic 1] (1)[pic 2] (2) Where the value of A = 2, 94; B = 0, 91After getting the value of Effort Multiplier and Scale Factor will be used SLOC values were obtained from the unadjusted function point.Unadjusted Function PointUnadjusted Function Point is a function point that has not provided additional input to be adjusted function point. Below is a description of each function point:Input: each input data from a user who used to run the application.Output: each of the output of the process is displayed to the user.Inquiry: every on- line input that generates direct response software.Internal Logical Files: each master file that is part of the application.External Interface: Each interface (means) external channel information from one system to another system. Of the value of Function Point or UFP will get value SLOC , calculated as follows : SLOC=(Value of SLOC/UFP)*UFP (3)SLOC value above based on an assessment of the weight of the SLOC for each UFPIn addition to a function point that should be identified next is the programming language that will be used. The programming language will determine estimates of the number of line of code based on the unadjusted function point.