• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1164-1177
• /
• 2005

As the software development process becomes complicated, software requirements become complicated, too. Many efforts are needed in requirements management. It is impossible to define all requirements of software at first, and the development environment changes as project is gone. As the cost of requirements change management is much more than development cost, the changes should be controled immediately through systematic change management. In this paper, I suggest a method to manage requirements change systematically based on the change management process in software product lines. The requirements change at the application engineering process is analyzed and managed using the domain engineering process because the application requirements are customized from the domain requirements in software product lines. Such the consistent change management helps to make decisions about changes by change impact analysis and alternative solution design. Through this method, the potential change costs can be saved because same change requests are not repeated by controlling the change requests completely.

• The KIPS Transactions:PartB
• /
• v.12B no.1 s.97
• /
• pp.1-8
• /
• 2005

The importance of software is getting high in development of the digital device (digital camcoder, digital camera, mp3 player, ....). And because the sire of software becomes larger and complicated, the necessity of software configuration management (to solves a software crisis) is increased. The general software configuration management system shows lack of the property and features of software development environment for image processing algorithm due to its wide range to be covered. Image processing algorithm development environment has properties like repetitive analysis and simulation using visual programming environment where, beside support of elementary development functions. component(or library) can be combined and tested interactively. Moreover, the method to look fast and effectively for component having similar function is required. In this paper, we present the system which supports the software configuration management method for a simulation tool and the property in the visual programming environment. And we relate our system to real simulation tool so as to check its ability as the software configuration management system for image processing algorithm development environment.

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.7
• /
• pp.461-470
• /
• 2013

The capacity for tracing relationships among various artifacts which are created at each phase of software system development is essential for software quality management. Software release refers to delivering a set of newly created or changed artifacts to customers. The relationships among artifacts which comprise software release must be traced so that the work for customer's requirement of change and functional enhancement is effectively established. And release management can be effectively realized through the integration of configuration management and change management. This paper proposes the technique for supporting change management of artifacts and for tracing relationships of artifacts which comprise software release through the integrated environment of personal workspace and configuration management system. In the proposed environment, the visualized version graph and automated tagging function are used for tracing relationships of artifacts.

• Proceedings of the Korea Association of Information Systems Conference
• /
• 2000.11a
• /
• 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
• /
• v.26 no.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
• /
• v.22 no.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.

• Journal of Korean Society for Quality Management
• /
• v.27 no.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
• /
• v.7 no.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.

• Plant Journal
• /
• v.6 no.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.

• Proceedings of the Korean Society for Quality Management Conference
• /
• 1998.11a
• /
• 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.