Estimated Value of Software Developer Productivity at the Software Implementation Stage Using Function Points
Most Software Development Processes (SDP) project failures occur due to errors in estimating cost, time, and effort during the planning phase. This happened because the planning carried out still relied on the intuition and experience of the programmer. One approach that can be taken to plan the right SDP is to know the value of SDP productivity. The focus of this research is to determine the value of productivity based on the differences in programmers’ skills. The case study is conducted to determine the productivity value of the web-based software that has been built, namely McDelivery. The productivity value is calculated based on the ratio of software size to the effort. Software size is obtained through the calculation of the Application Function Point Count (APFC). Meanwhile, the effort is obtained through expert judgment to determine the time needed by the development team at the junior, middle, and senior software developers to implement software functionality in person-day to the form of program code. The result shows that the productivity value of SDP is directly proportional to the level of ability of the programmers. These productivity values can be used as a solution option to calculate the estimated time, cost, and even the availability of programmers that are adjusted to the conditions faced in planning software development
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution-ShareAlike International License (CC-BY-SA 4.0) that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
Copyright without Restrictions
The journal allows the author(s) to hold the copyright without restrictions and will retain publishing rights without restrictions.
The submitted papers are assumed to contain no proprietary material unprotected by patent or patent application; responsibility for technical content and for protection of proprietary material rests solely with the author(s) and their organizations and is not the responsibility of the ULTIMATICS or its Editorial Staff. The main (first/corresponding) author is responsible for ensuring that the article has been seen and approved by all the other authors. It is the responsibility of the author to obtain all necessary copyright release permissions for the use of any copyrighted materials in the manuscript prior to the submission.