• 한국정보과학회논문지:소프트웨어및응용
• /
• 제32권12호
• /
• pp.1164-1177
• /
• 2005

현재 소프트웨어 개발 공정이 복잡해짐에 따라 개발하는 소프트웨어의 요구사항 역시 복잡해지고 있으며 요구사항 관리에 많은 노력이 소요되고 있다. 그러나 소프트웨어의 요구사항을 처음부터 모두 정의하는 것은 사실상 불가능하며, 개발이 진행되면서 환경은 변하기 마련이다. 또한 요구사항 변경은 개발보다 많은 비용이 소요되므로 체계적인 변경 관리를 통해 변경에 민첩하게 대응하고 관리되어야 한다. 본 논문에서는 소프트웨어 프로덕트 라인에서 요구사항 변경 관리 프로세스를 기반으로 체계적인 요구사항 변경 관리 방법을 제시한다. 소프트웨어 프로덕트 라인(software product lines)에서 어플리케이션의 요구사항은 도메인 요구사항과 밀접하게 관련되어 있으므로 어플리케이션 공학(application engineering) 단계에서 요구사항 변경이 발생했을 경우 도메인 공학(domain engineering) 단계를 이용하여 변경을 분석하고 관리하는 방법을 제시한다. 이러한 일관된 변경 관리를 통해 변경 범위를 분석하고, 변경 대처방안을 제시함으로써 변경 처리 결정을 내리는데 도움을 주며 한번 요청된 변경이 완벽하게 처리되도록 도와주어 같은 변경의 반복 요청을 막을 수 있기 때문에 잠재된 변경 비용을 절약할 수 있다.

• 정보처리학회논문지B
• /
• 제12B권1호
• /
• pp.1-8
• /
• 2005

디지털기기 개발에 있어서 소프트웨어의 중요성이 높아지고, 규모가 커짐에 따라 소프트웨어의 위기를 해결하기 위한 소프트웨어형상관리의 필요성이 증가하고 있다. 그러나 일반적인 소프트웨어형상관리 시스템들은 영상처리 알고리즘 개발 환경의 특성 및 특징들을 수용하기에 부족하다. 영상처리 알고리즘 개발 환경은 컴파일러와 같은 기본적인 개발 도구 외에 컴포넌트(나 라이브러리)들을 인터액티브하게 조합하고 테스트 할 수 있는 시뮬레이션 환경을 통하여 테스트와 분석을 반복하면서 개발하는 특징을 가지고 있다. 뿐만 아니라, 시뮬레이션 과정 중에는 유사한 기능을 가진 알고리즘 중에 적합한 알고리즘을 빠르고 효과적으로 찾기 위한 방법이 필요하다. 본 논문에서는 이러한 영상처리 알고리즘 개발 환경에서 사용하는 시뮬레이션 도구를 체계적으로 지원해줄 수 있는 비주얼 워크스페이스 기반의 소프트웨어형상관리 방법과 이를 수용할 수 있는 소프트웨어형상관리 시스템을 제안한다. 또한, 개발된 시스템을 실제 시뮬레이션 도구와 연계하여 소프트웨어형상관리 시스템으로써의 적합성을 확인한다.

• 정보처리학회논문지:소프트웨어 및 데이터공학
• /
• 제2권7호
• /
• pp.461-470
• /
• 2013

소프트웨어 시스템 각 개발단계에서 만들어지는 다양한 산출물들의 연관 관계를 추적하는 능력은 소프트웨어의 품질 관리에 필수적인 요소이다. 소프트웨어 릴리스는 신규 또는 변경된 산출물들의 집합(실행 프로그램 포함)을 고객에게 인도하는 것이다. 소프트웨어 릴리스를 구성하는 산출물들의 연관 관계를 정확하게 추적할 수 있어야 고객의 변경 요구나 기능 개선을 위한 효율적인 작업을 수행할 수 있으며, 릴리스 관리는 형상 관리와 변경 관리를 통합할 때 효율적으로 이루어질 수 있다. 본 논문은 개인 작업 공간과 형상 관리 시스템을 통합한 환경을 통해 산출물들의 변경 관리를 지원하고 릴리스를 구성하는 산출물들의 연관 관계를 효율적으로 추적할 수 있는 방법을 제시한다. 제시된 환경에서 산출물의 연관 관계를 추적하기 위해 시각화된 버전 그래프와 자동화된 태깅(tagging) 기능을 사용한다.

• 한국정보시스템학회:학술대회논문집
• /
• 한국정보시스템학회 2000년도 추계학술대회
• /
• pp.26-31
• /
• 2000

It is said that the focus of managing venture business is currently moving from technology competition to management competition. By the way, the software venture business(SVB) has some weak points in its structural composition and itematization and no professional personnel in other several sections except technology development section. In addition, such basic functions as technology and R & D, finance and accounting, marketing required to the management of business are concentrated on only one man, its representative director. Therefore, this study aims to provide the basic data useful to the establishment of governmental policy in information and communication, to the rearing of the SVB by a local government related to the software, and to the administration of SVB by investigating the actual conditions. This study attempts to examine the literature on venture business and software industry, and its management with a questionnaire about the actual conditions of managing the SVB. The questionnaire is given to 527 local enterprises belonging to the Software Industry Association and to 171 enterprises in the Software Center. This study compromises the characteristics of the SVB, the actual conditions of its technology and R & D, finance and accounting, and marketing. The characteristics of the SVB are classified into categories such as the stage of its growth(the stage of its seed and start-up, the stage of tis development and growth, the stage of its stability and maturity) and the main business(the system integration, the software development for contract, the package software development service, the software-related service). Additionally, the study attempts to analyze positively the actual condition of its management after classified by the areas of business profile, its general management, its technology development, its finance and accounting, and its marketing The result of this study is found that the SVB has a lot of troubles in part of marketing and finance & accounting activity as well as general management. The SVB realizes the importance of the technology development rather than that of management activity including marketing activity. So we expect this study can assist the SVB to establish the business guidelines for own management plans.

• Asia pacific journal of information systems
• /
• 제26권2호
• /
• pp.322-337
• /
• 2016

Research on information systems and software engineering has often neglected behavioral effects, which may play a role in decision making on software development. The current study addresses this issue by empirically investigating the behavioral roots of over-requirement in the context of a software development project via an experiment. The negative phenomenon of over-requirement refers to specifying a software system beyond the actual needs of the customer or the market, which overload the system with unneeded features. The research question addressed here is whether over-requirement is due in part to the emotional involvement of developers with the software features they developed because of behavioral effects. Previous studies have demonstrated that under the endowment, I-designed-it-myself, and IKEA effects, people become emotionally involved and overvalue physical items that they respectively possess, self-design, or self-create. The findings of our experiment show that participants over-valued features they were assigned to be responsible for, to specify, or to construct, thereby confirming that the three behavioral effects play a role in software development decisions and affect over-requirement. Thus, the study contributes to software development research and practice from the behavioral economics perspective, highlighting the roots of over-requirement.

• Journal of Information Technology Applications and Management
• /
• 제22권3호
• /
• pp.143-167
• /
• 2015

This paper addresses the issue how the total life cycle cost may be minimized and how the cost should be allocated to the acquirer and developer. This paper differentiates post life cycle change (PLCC) endeavors from PLCC activities, rigorously classifies PLCC endeavors according to the result of PLCC endeavors, and rigorously defines the life cycle cost of a software product. This paper reviews classical definitions of software 'maintenance' types and proposes a new typology of PLCC activities too. The proposed classification schemes are exhaustive and mutually exclusive, and provide a new paradigm to review existing literatures regarding software cost estimation, software 'maintenance,' software evolution, and software architecture from a new perspective. This paper argues that the long-term interest of the acquirer is not protected properly because warranty period is typically too short and because the main concern of warranty service is given to removing the defects detected easily. Based on the observation that defects are caused solely by errors the developer has committed for software while defects are often induced by using for hardware (so, this paper cautiously proposes not to use the term 'maintenance' at all for software), this paper argues that the cost to remove defects should not be borne by the acquirer for software.

• 품질경영학회지
• /
• 제27권3호
• /
• pp.94-112
• /
• 1999

It is booming to use computer and information owing to the information society. As software applications have grown, so too has the importance of software quality. Therefore, software quality measurement and evaluation are necessary to satisfy the users who are using computers. The ISO/IEC 9126 defines six quality characteristics and twenty-one subcharacteristics including forty inter quality characteristics. We developed software measurement and evaluation technique using the check list in accordance with the ISO/IEC 9126 in design phase. We applied idea and concept of Total Quality Management in order to evaluate and measure the quality of software. Namely, it is the concept such as "you should do it right the first time." or "you have to build quality in the process." We executed the quantitative evaluation of software, also had shown the distinctive result in order that users and developers can find the errors easily. We evaluated the quality of academic softwares in order to verify developing technique at S college. As a result of the evaluation, this college has found it necessary to maintain the software as soon as possible because academic systems are not adequate for users at this present time.

• Industrial Engineering and Management Systems
• /
• 제7권3호
• /
• pp.266-287
• /
• 2008

To manage collaborative negotiation in software system design, we have built a socio-technical argument-based negotiation management approach by integrating a Socio-technical Co-construction Process (STCP) with an Argument-based Negotiation Process (ABNP). This paper reviews relevant research work and presents each step of this approach. The STCP provides rich contextual information of technical decisions and social interactions in a system design process. The ABNP provides STCP with a negotiation management and conflict resolution strategy by guiding software engineers to generate, exchange and evaluate their argument claims in negotiation activities. In addition, this paper describes a prototype system which implements this new approach using the advanced Web-based software technologies with the goal of demonstrating how to systematically enhance the negotiation management capabilities in a dynamic socio-technical framework.

• 플랜트 저널
• /
• 제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.

• 한국품질경영학회:학술대회논문집
• /
• 한국품질경영학회 1998년도 The 12th Asia Quality Management Symposium* Total Quality Management for Restoring Competitiveness
• /
• pp.43-50
• /
• 1998

The cause of software crisis is that software quality and productivity can not meet the requirement of software market. In order to resolve the software crisis, there are many approaches to be proposed. Software reuse is one of the high potential approaches to improve software quality and productivity. Some high-tech countries (like USA, Japan) have proposed and studied the topics of software reuse in 1970 and got several results. In software development procedure, the products of detailed design and implement phases are simple, definite and suitable for reuse. In this paper, the necessary documents of reusable software component will be proposed, and how to select and evaluate the software components with high reuse potential and high quality will be discussed and recommended.