scholarly journals Meningkatkan Akurasi Perkiraan Waktu Proyek Perangkat Lunak Dalam COCOMO II Dengan Mengubah Nilai Parameter

Author(s):  
Rahmi Rizkiana Putri ◽  
Weny Mistarika Rahmawati

Good management of software projects can be obtained through accurate time estimates. When estimating less accurate time it will affect the lack of effective management of the software project and the entire process during project development. Barry Boehm, an inventor of COCOMO, has developed the COCOMO 1 cost driver that has an effect on the accuracy of the estimated time results. But if you only use the COCOMO II cost driver, it is still far from the accuracy of the desired results. Therefore it is necessary to change the values of parameters C and D for estimated time. Changes in parameter values are done by decreasing the initial gradation by 0,1 so that the approximate results become more optimal and close to the original values. Based on the implementation of the proposed method, the results show that the error decreases to% when compared to using only the COCOMO I and COCOMO II cost drivers without changing parameter values. So that the accuracy of the estimated project time can increase.

Author(s):  
Luz María Hernández-Cruz ◽  
Margarita Castillo-Téllez ◽  
Diana Concepción Mex-Álvarez ◽  
José Ramón Cab-Chan

Agile project management is an iterative approach that allows you to plan and guide project processes that require special speed and flexibility to achieve project success. It is for this reason that today professionals must master the basic concepts of this work as disciplinary or professionalizing competence. The objective of the study lies mainly in compiling recent research, including the last three years, in relation to Agile Software Project Management, its current situation and its application in practice. The study shows the implementation of the methodology proposed by Kitchenham for the systematic literature review (RSL) analyzing 40 scientific publications, concluding that the agile management of software projects allows efficient and effective management with the application of a standard o priority methodology and with the unavoidable use of software tools of specific use for it.


Author(s):  
Fabrizio Fioravanti

One of the emerging techniques that is becoming increasingly popular for managing software project is eXtreme Programming (XP) (Beck, 1999, 2000; Williams, 2000). XP surely changes the way in which we develop and manage software, as all the other methodologies related to the Agile Manifesto do (Agile Alliance, 2001; Boehm, 2002; Cockburn, 2001; Highsmith, 2001; Rakitin, 2001). XP has been the methodology that I have adopted in recent years to develop and manage software projects — before modifying it in order to create my own methodology, ADPD (Agile and Defined Project Development), which is described in Chapter XI. In order to understand ADPD, it is necessary to acquire all the possible knowledge about XP, since ADPD is XP 80% and recognizes quite all the values of this revolutionary technique for developing and managing software projects. The most interesting feature of XP consists in the fact that it is human oriented (Brooks, 1995). XP considers the human factor as the main component for steering a project toward a success story. On the other hand, it is important to notice that XP is guided by programming rules, even if its more interesting aspects deal with the values that are the real guides for the design, development, and management processes.


Author(s):  
Aravindhan K

Cost estimation of software projects is risky task in project management field. It is a process of predicting the cost and effort required to develop a software applications. Several cost estimation models have been proposed over the last thirty to forty years. Many software companies track and analyse the current project by measuring the planed cost and estimate the accuracy. If the estimation is not proper then it leads to the failure of the project. One of the challenging tasks in project management is how to evaluate the different cost estimation and selecting the proper model for the current project. This paper summarizes the different cost estimation model and its techniques. It also provides the proper model selection for the different types of the projects.


Author(s):  
Muhammad Aliyya Ilmi ◽  
Fajar Pradana ◽  
Widhy Hayuhardhika Nugraha Putra

Reducing the risk of failure in working on software projects is one of the successes for the company. It can be done by implementing project planning management properly. One important aspect of project management planning is scheduling. Scheduling includes recording human resources and tasks in the project. The Kanban method is one of the methods used to overcome problems in controlling project schedules. This study aims to develop a project scheduling system that applies the Kanban method. In this research, project management and scheduling system will be developed using the Kanban method. This system expected to be able to assist companies in handling projects. Kanban was chosen because it can easily respond to project changes, easily implemented, and company needs. In this study, unit testing was performed on the system's three main features and tested the validity of the system's 49 functional requirements. The usability test produces a value of 76. Based on the validation and usability test results, it can be concluded that the system is included in the acceptable category.


2014 ◽  
Vol 9 (2) ◽  
pp. 101
Author(s):  
Alusyanti Primawati ◽  
Dewi Mustari

The software is an intermediary between system hardware computer with user as human. Based on the emerging software projects because of the importance of the functions already affects many functions in various aspects. Software projects that have become this need ultimately require management actions to manage the process in the project. Project management is necessary for the success of the project. Bereau Information System PT. X is one part of a company that provides software for functional PT. X. Analysis results from the concept of software project management information systems Bureau at PT. X when the process of designing application systems information accounting PT. X aims to answer how concept of project management Information Systems Bureau in designing the Accounting Information System applications. The methods used in this research is the study of the library with a general empirical approach based on experience and theories related to project management especially in software projects. The conclusions obtained that the activity of the management software on System Information Bureau is in compliance with the application of existing theory, but science is constantly evolving so as to do the development management activities after conducting evaluation regularly for the maintenance of long-term software project.


2020 ◽  
Vol V (IV) ◽  
pp. 48-59
Author(s):  
Ashfaq Ahmad ◽  
Nisar Ahmad ◽  
Nadia Malik

Effective control of risk factors ensures the performance of projects in any industry. Risk factors can influence software projects of any size and type. This research aims to identify and examine different risk factors associated with projects in the software industry. The relationship between Software Project Risks (SPRs) and Perceived Project Performance (PPP) measures is determined. This study is based on a survey approach, and a questionnaire is used to record opinions and responses from 199 software professionals working in the Pakistan software industry. The results showed that the association between SPRs and PPP measures is statistically significant, and there exist a positive relationship. It is concluded that an increase in understanding of SPRs can increase PPP measures used to evaluate the software project. The results will help researchers and professionals in understanding the impact of different risk factors on software projects' perceived performance.


Author(s):  
Nuthan Munaiah ◽  
Steven Kroh ◽  
Craig Cabrey ◽  
Meiyappan Nagappan

Software forges like GitHub host millions of repositories. Software engineering researchers have been able to take advantage of such a large corpora of potential study subjects with the help of tools like GHTorrent and Boa. However, the simplicity in querying comes with a caveat: there are limited means of separating the signal (e.g. repositories containing engineered software projects) from the noise (e.g. repositories containing home work assignments). The proportion of noise in a random sample of repositories could skew the study and may lead to researchers reaching unrealistic, potentially inaccurate, conclusions. We argue that it is imperative to have the ability to sieve out the noise in such large repository forges. We propose a framework, and present a reference implementation of the framework as a tool called reaper, to enable researchers to select GitHub repositories that contain evidence of an engineered software project. We identify software engineering practices (called dimensions) and propose means for validating their existence in a GitHub repository. We used reaper to measure the dimensions of 1,994,977 GitHub repositories. We then used the data set train classifiers capable of predicting if a given GitHub repository contains an engineered software project. The performance of the classifiers was evaluated using a set of 200 repositories with known ground truth classification. We also compared the performance of the classifiers to other approaches to classification (e.g. number of GitHub Stargazers) and found our classifiers to outperform existing approaches. We found stargazers-based classifier to exhibit high precision (96%) but an inversely proportional recall (27%). On the other hand, our best classifier exhibited a high precision (82%) and a high recall (83%). The stargazer-based criteria offers precision but fails to recall a significant potion of the population.


Author(s):  
Izzat Alsmadi ◽  
Saqib Saeed

Typical traditional software development models are initially designed for company-style software project teams. They also assume a typical software project that has somewhat clear goals, scope, budget, and plan. Even Agile development models that are very flexible in considering previous project parameters assume somewhat stable team and project structures. However, in recent years, the authors have noticed expansion in software projects that are developed in a very illusive flexible team, scope, budget, and plan structures. Examples of such projects are those projects offered in open competition (also called crowd sourcing) structure for software developers to be part of. In typical open competition projects, initial, high level project ideas are submitted to the public through the Internet. The project initiators give their initial requirements, constraints, and conditions for successful products or submissions. Teams can be organized before or through the competition. Submission and evaluation of deliverables from teams are subjected to project initiator evaluation along with evaluation teams organized through the open competition host. This chapter investigates all traditional project characteristics. The authors elaborate on all those elements that should be modified to fit the open competition agile structure. They use several case studies to demonstrate management issues related to managing software projects in open competitions.


Sign in / Sign up

Export Citation Format

Share Document