• Asia pacific journal of information systems
• /
• 제16권3호
• /
• pp.143-158
• /
• 2006

Identifying risk factors in software risk management is imperative for project managers. The purpose of this paper is to provide software project risk factors validated by statistical analysis, and thus to help project managers alleviating the possibility of software project failure. Factor analysis with data collected from 264 Korean project managers and consultants identified 12 categories and 46 risk factors. T-test results showed that project managers and participants had statistically different perception on 3 risk factors among those 46 risk factors. We concluded by discussing implications of our findings and future research directions.

• 플랜트 저널
• /
• 제6권2호
• /
• pp.56-61
• /
• 2010

In this paper, an integrated management software is developed to promote the business competitive power. The interoperability among the software accounts for an ever growing performance of petrochemical plant project. If the interoperability is built up, company has taken advantages of quality, schedule, cost, and safety by active communication. The advantage of an integrated management software is examined in three aspects. In efficiency aspect, It takes advantage of the saving about the various information and the standard of project performance procedure. In quality, the integration gave aid to a quality improvement through team collaboration and data management within project life cycle. In cost, poor communications between systems waste 30% of project costs. If information could be inputted once and used by all, reductions in delivery time up to 40% were possible. Therefore, 10% savings of engineering cost was also possible.

• 한국IT서비스학회지
• /
• 제7권3호
• /
• pp.129-144
• /
• 2008

The uncertainty of software projects makes a big gap between the initial schedule/expense and the final one. Moreover, it is difficult for a project manager to reschedule and re-budget for reflecting the effects of changes in the software development. In this paper, we suggest EVM (Earned Value Management) to control the schedule and the expenses of an on-going software development project. In order to apply EVM to a software project, we consider turnkey contracts and propose the way to calculate the earned value for the software development. Finally, we illustrate our method with the case of N-company. We expect our EVM help to analyze and to predict the final schedule and the expense of a software development project.

• 한국IT서비스학회지
• /
• 제8권1호
• /
• pp.125-142
• /
• 2009

The Ministry of Information and Communication announced "The Guideline for Management of Software Project" in October 2006. The public employees(acquirer) have to manage software projects with this guideline. The guideline was based on the International standard(ISO/IEC 12207) and IEEE standard(IEEE/EIA 12207), and was developed by considering the domestic software industry environment. The guideline can help to establish a software acquisition process for appropriate management of software projects, and the process can increase the management productivity of software projects. This study provides the explanation about the guideline with terms of 5W1H(who(user), what(summary), when(time to apply), where(domain of application), why(objective), how(method of use)) for understanding of the guideline.

• 한국경영과학회지
• /
• 제18권3호
• /
• pp.129-149
• /
• 1993

The high level of activity in the development and maintenance of computer software makes the scheduling of software projects an importnat factor in reducing operating costs and increasing competitiveness. Software activity is labor intensive. Scheduling management of hours of software work is complicated by ther interdependencies between the segments of work, and the uncertainties of the work itself. This paper discusses issues of scheduling in software engineering management, and presents a modular decomposition model for software project scheduling, taking advantage of the facility for decomposition of a software project into relatively independent work segment modules. Modular decomposition makes it possible to treat scheduling as clustering and sequencing in the context of integer programming. A heuristic algorithm for the model is presented with some computational experiments.

• 대한안전경영과학회:학술대회논문집
• /
• 대한안전경영과학회 2005년도 춘계학술대회
• /
• pp.129-135
• /
• 2005

This paper proposes the interated and balanced project management system for software and IT by considering BSC, MBNQA, ISO 9001, Six Sigma, CMM and SPICE. This system can be extended to assess the various project management practices.

• 지식경영연구
• /
• 제18권2호
• /
• pp.45-63
• /
• 2017

In the success of an IT project, the role of S/W developer in carrying out the project is critical and crucial. However, compared to its importance, there is only a few studies on the role of human resources in software engineering field, mainly focusing on technology. Based on regulatory focus theory, this study examines how the effect of technology recency on developer's intention to participate in the IT project changes depending on the regulatory focus of the software developer. As a result of the experiment, it was confirmed that there is a difference in the effect of technology recency on project participation intention according to the condition of developer's regulatory focus. This study is meaningful because it extends regulatory focus theory to software engineering field and made theoretical contribution to the research field of behavioral software engineering. In practical, it was possible to suggest a way to improve the intention of the developer to participate in the project, by understanding the software developer in the IT project, considering the software developer propensity and project characteristics.

• Journal of Construction Engineering and Project Management
• /
• 제1권2호
• /
• pp.28-36
• /
• 2011

Risk management is popularly and widely used in various industries to handle uncertainty that can negatively affect their businesses. While in the current Information-Technology oriented age, software packages are designed to assist in carrying out risk management processes, the construction industry does not seem to have software that is tuned to its specific characteristics and processes. Therefore, this study first explores the types of software that are commonly used for risk management in the Singapore construction industry. Also, using one-sample t-test, it is tested if the software programs used in the construction industry have effectively catered the needs of the users. For the analysis, a survey questionnaire was developed and the representatives from 34 companies participated in the survey. Furthermore, this study also makes use of the current risk management framework defined in ISO31000 to design a risk management software algorithm that can suit the needs for the Singapore construction industry. The results from this study will contribute to identifying strategic areas, in terms of use of risk management software, on which the industry needs to focus, ultimately enhancing their performance of risk management.

• 디지털산업정보학회논문지
• /
• 제5권2호
• /
• pp.133-140
• /
• 2009

In the paper, we proposed the systematical and quantitative software risk management methodology based on risk analysis model. A software risk management consists of the basic risk management method(BRIMM) and the detailed risk management method(DRIMM). BRIMM is applied to unimportant phases or the phase which also the risk factor does not heavily influence to project. DRIMM is used from the phase which influences highly in project success or the phase where the risk factor is many. Fulfilling risk management combined two methods, we can reduce project's budget, term and resource's usage, and prevent risk with the optimum measures obtained by the exact risk analysis.

• International Journal of Computer Science & Network Security
• /
• 제22권8호
• /
• pp.249-259
• /
• 2022

Project management and deployment has gone through a long journey from traditional and agile to continuous integration, continuous deployment and continuous monitoring. Software industry benefited with the latest buzzword in the development process, DevOps that not only escalates software productivity but at the same time enhances software quality. But the implementation and assessment of DevOps practices is expository as there are no guidelines to assess and improvise DevOps application in software industries. Hence, there was a need to develop a hybrid model to assist software practitioners in DevOps implementation. The intention behind this paper is to implement the already proposed DevOps hybrid model using suggested tool chains including Jenkins, Selenium, GitLab, Ansible and Nagios automation tools through Jenkins project management environment and plugins. To achieve this implementation objective, a java application is developed with a web-based graphical interface. Further, in this paper, different challenges and benefits of Jenkins implementation shall also be outlined. The paper also presents the effectiveness of DevOps based Model implementation in software organizations. The impact of considering other automation tools and models can also be considered as a part of further research.