• Journal of KIISE
• /
• v.42 no.7
• /
• pp.878-888
• /
• 2015

Software project planning includes several processes for estimating the effort required to complete software project tasks, allocating human resources to tasks, and creating a project plan. Because software planning is becoming more complicated as the size of software projects grow, it is difficult for project managers to decide on a reasonable project plan. To help them, many automatic software project planning approaches have been proposed. The approaches all focus on minimizing project duration. But if the plan is simply to minimize the duration, without considering software quality, the plan can harm the eventual software quality. In our research to create a reasonable project plan, we consider software quality as well as duration of the project, by defining a software quality score. The project manager can plan the project to maximize software quality for a specific project duration.

• Journal of Information Technology Applications and Management
• /
• v.13 no.4
• /
• pp.237-255
• /
• 2006

This study was exploratively performed to demonstrate the management behavior of the public software project in korea. In this study, 167 auditing reports on the public software project which were carried out during $1999{\sim}2003$, were employed and surveyed. Survey reveals that quality management was the most neglected in process of software project management relative to other 12 management areas. And configuration management, risk management, time management, and scope management follow up in order in its vulnerability in software project management.

• Journal of Information Technology Applications and Management
• /
• v.11 no.4
• /
• pp.103-120
• /
• 2004

Identifying validated risk factors in software risk management is imperative for project managers. Although validated risk lists were provided by previous researchers, risk list associated with software project performance areas was not provided as yet. This paper represents a first step toward understanding risk lists by various project performance areas (time, cost, and quality) to help project managers alleviating the possibility of software project failure. Four simultaneous exploratory surveys were conducted with 29 experienced software project managers. Three different risk factor ranking sets for each project performance area were compared with, the risk ranking, which was provided without clarifying specific project performance areas. The risk lists and their corresponding perceived importance were different from previous research results. This implies that identifying risk factors for specific project performance areas can provide additional information for project managers. We concluded by discussing implications of our finds for both research and improving risk management practice.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.191-204
• /
• 2011

Recently, many software companies are trying to improve the software quality and project outcome with more costs and efforts in development time. In the software convergence and integration environments, it is required efforts to gain high quality of software. In other words, it is required to utilize software engineering knowledge and technology for higher software quality and better software project productivity. The Software development productivity can be varied by software process capability according to building a framework for software development, selection and use of appropriate technology, human resource management. Software process capability will influence software project outcome which is the general opinion. This study provides empirical evidence about software engineering efforts and investment approach to lead software project performance. We measured the software engineering efforts by SW engineering level and analyzed the corelation between software engineering level and schedule deviation. And, we verified that this performance is affected by the size of software company. As a result, software process capability is important to build a infrastructure and develop systematically software project. The higher software engineering level can lead to improved software project performance.

• Journal of Software Engineering Society
• /
• v.26 no.4
• /
• pp.77-92
• /
• 2013

To plan a software project, the manager (1)make a work breakdown structure (WBS), (2) estimate efforts for each task, (3) assign employee to each task, and (4) estimate overall schedule. When software project becomes complicated, the possible combination of WBS, effort, and employee assignments dramatically becomes larger. Software planning tool can help software project managers to deal with this complexity. In this research, we discuss with a group of experts who work in software industry, to elicit practical requirements that should be considered in the software planning technique. Considering these requirements, we develop a software project planning tool APP (Automatic Project Planner) which provide effort estimation based on historical knowledge data and automatic human resource allocation. Our technique can be the basis of reasonable and practical software project planing.

• The Journal of Information Systems
• /
• v.16 no.4
• /
• pp.243-268
• /
• 2007

It is critical to manage risks to complete IS(Information Systems) projects successfully. Identifying risk factors would be the first step for the project risk management. Previous research has discussed the issue with various points of view, such as different risk factors based on project types and roles involved in their projects. This paper empirically explored how people perceive different risk factors by project development methodology, between self-developing IS using programming language like C, Visual Basic and adapting software package already developed by software venders like ERP, CRM packages. There are researches regarding project risk factors for project management in the several point of views. And there are also researches regarding comparison between self-developing and adapting software packages methodology in IS project. However, there are no study on project risk factors comparison between self-developing IS using programming language and adapting software packages already developed by software venders in IS project. This research can be differentiated from previous ones, because it was considered both point of project risk management and development methodology in IS project. This research results implied meaningful messages to enterprise company to be planned IS projects and people who involved in IS projects. They should consider and need to prepare differently according to each development methodology for preventing project risks. It makes them reduce project risks in each case and complete successfully IS projects. Especially, if they have no experiences for implementing software packages, they can forecast the project risks and prepare them in advance.

• Knowledge Management Research
• /
• v.18 no.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.

• Asia pacific journal of information systems
• /
• v.6 no.1
• /
• pp.241-267
• /
• 1996

The problems like exceeding estimated cost, late due-date, expensive maintenance, insuffiency of experts and low productivity are becoming emphasized related with the software development. In order to overcome these problems and to develop the highly qualified software within the limited resources, a project management tool is used. The purpose of this study is to develop a conceptual model of the project management system which can plan, analyze and control the software development projects effectively. The model is constructed with plan and track management system, cost management system and operation management system for the efficient project management. It is named by LSD-PMS : Large-scale Software Development Project Management System. We reviewed 5 cases of project management. LSD-PMS is evaluated and reviewed by the project managers in the field. It is proved that LSD-PMS is a tool which can help project managers develop software successfully given budget and time schedule. In the future, this system should be further developed as an integrated model with system implementation tools such as CASE products.

• The KIPS Transactions:PartD
• /
• v.13D no.1 s.104
• /
• pp.87-96
• /
• 2006

This paper focused on the method for customizing software development path, considering the project environments and characteristics. he selection standard of development path is composed of ten items, based on the process of ISO/IEC TR 15721 Information Technology Guide for ISO/IEC 12207 (Software Life Cycle Process) and ISO/IEC 15504 Information technology - Process assessment. The ten items were reflected the project environments and characteristics, at the same time the items conduct the adjustment item of selecting project development path. An algorithm for selecting software development path through items of the project environments and characteristics is presented. To test the algerian in this paper, a system for selecting development path, which reflected algorithm was developed. The development project for web-based system were also adopted to the system for selecting development path. In addition, provened hand-worked project path process differed from machine-worked project path process. The reason why it differs is that outputs were mixed or their names were changed. The effect is to select easily software development route suitable for project environment and characteristics.

• International Journal of Computer Science & Network Security
• /
• v.22 no.3
• /
• pp.229-235
• /
• 2022

The process of correcting, upgrading, and improving software products after they have been handed over to the consumer is known as software maintenance. Offshore software maintenance outsourcing (OSMO) clients benefit from cost savings, time savings, and improved quality software through OSMO. In most circumstances, the OSMO vendor makes a lot of money but not in all the cases. Especially, when the OSMO project offer is not properly assessed. An efficient outsourcing contract might yield successful outcomes for outsourced projects. But before sending a detailed proposal to bid on the OSMO project the vendor must have to assess the client's project (business offer) requirements. The purpose of this study is to find out common trends within the assessment of a OSMO project. A case study approach along with semi-structured interviews from eight companies concluded ten common practices and several roles. Among these practices, four (code structure, requirements, communication barriers and required infrastructure) were consistent amongst the responses .The findings, limitations and future work are discussed.