• 정보과학회 논문지
• /
• 제42권7호
• /
• pp.878-888
• /
• 2015

소프트웨어 프로젝트 계획은 각 작업의 공수를 예측하고, 적절한 인력을 할당한 뒤 일정을 산출하는 과정을 포함한다. 프로젝트의 규모가 커질수록 가능한 개발 계획의 경우의 수가 많아지기 때문에 관리자가 합리적인 결정을 내리기 어렵다. 이를 지원하기 위해 프로젝트 계획 생성 기법들이 제안되어왔다. 제안된 대부분의 기법들은 전체 프로젝트 일정의 최소화를 계획 생성의 가장 중요한 목표로 사용한다. 하지만 일정 최소화를 달성하는 계획은 개발되는 소프트웨어의 품질을 고려하지 못하기 때문에 이러한 부분을 함께 반영한 프로젝트 계획 생성이 필요하다. 본 연구에서는 합리적인 프로젝트 계획을 생성하기 위하여 소프트웨어 프로젝트 계획에 따른 소프트웨어 품질 점수를 정의하고 동시에 전체 일정 목표를 고려할 수 있는 프로젝트 계획 생성 기법을 제안한다. 관리자는 본 기법을 사용하여 전체 소프트웨어 개발 프로젝트에 요구되는 기한 안에 해당 소프트웨어의 품질을 최대하는 계획을 생성할 수 있다.

• Journal of Information Technology Applications and Management
• /
• 제13권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
• /
• 제11권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.

• 한국IT서비스학회지
• /
• 제10권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.

• 소프트웨어공학소사이어티 논문지
• /
• 제26권4호
• /
• pp.77-92
• /
• 2013

소프트웨어 프로젝트 계획 생성 과정은 (1)프로젝트를 수행하기 위한 작업 구조(WBS)를 작성하고, (2)각 작업에 필요한 공수를 예측한 뒤, (3)작업에 인력을 할당하여, (4)전체 일정을 예측하는 과정으로 이루어진다. 프로젝트의 규모가 커질수록 가능한 작업 구조, 공수, 인력 할당의 조합의 수가 급격히 많아지며 이에 따라 프로젝트 계획 생성 과정의 복잡도가 매우 높아지게 된다. 따라서 이를 지원하기 위한 프로젝트 계획 생성 지원 기법이 필요하다. 본 연구에서는 실무 전문가 그룹과의 논의를 통해 소프트웨어 프로젝트 계획 생성 지원 기법에서 고려해야 할 여러 실무 요구사항들을 도출했다. 도출된 실무 요구사항을 고려하여 개발된 프로젝트 계획 생성 지원 도구 APP(Automatic Project Planner)는 개발 조직의 과거 지식 데이터를 활용한 공수 예측을 지원하며, 실무 이슈가 고려된 자동 인력 할당을 제공한다. 본 도구를 통해 합리적이고 현실적인 프로젝트 계획의 기반을 마련할 수 있다.

• 한국정보시스템학회지:정보시스템연구
• /
• 제16권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.

• 지식경영연구
• /
• 제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.

• Asia pacific journal of information systems
• /
• 제6권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.

• 정보처리학회논문지D
• /
• 제13D권1호
• /
• pp.87-96
• /
• 2006

본 논문은 프로젝트 환경과 특성을 고려하여, 소프트웨어 개발 경로를 커스터마이징 하는 방법을 설계한 것이다. 개발 경로 선정 기준은 ISO/IEC TR 15721 Information Technology Guide for ISO/IEC 12207(Software Life Cycle Processes), ISO/IEC 15504 Information technology - Process assessment의 프로세스 내용에 기반 한 10개의 영역 특성이다. 10개의 영역 특성은 프로젝트 환경과 특성을 반영한 것이며, 프로젝트 개발 경로 선정 항목들을 정의한다. 프로젝트 환경과 특성 항목인 10개 영역 특성 항목을 이용하여 소프트웨어 개발 프로세스를 선정하는 알고리즘을 제시한다. 본 논문에서 제안한 소프트웨어 개발 경로를 커스터마이징 하는 방법을 평가하기 위하여 소프트웨어 개발 경로를 커스터마이징 하는 방법을 반영한 개발 경로 선정 시스템을 가지고 웹 기반 시스템 개발 프로젝트를 적용한다. 그러나 입증된 수작업 프로젝트 경로 프로세스와 시스템에서 출력된 프로젝트 경로 프로세스가 차이가 난다 차이가 나는 주원인은 산출물이 서로 합쳐졌거나, 명칭이 바뀌었기 때문이다. 효과로는 소프트웨어 개발 프로젝트 환경과 특성에 적합한 경로 프로세스를 용이하게 선정한다.

• International Journal of Computer Science & Network Security
• /
• 제22권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.