• 한국IT서비스학회:학술대회논문집
• /
• 2005.11a
• /
• pp.345-355
• /
• 2005

As the portion of information systems(IS) budget to the total government budget becomes greater, the cost estimation of IS development and maintenance projects is recognized as one of the most important problems to be resolved for quantitative and efficient management of IS budget. The primary concern in the cost estimation of IS projects is to estimate software development cost. In this paper, we propose a new method to estimate software cost using support vector regression(SVR), which has attracted considerable attention because of its good performance and theoretical clearness. The paper is the first study which apply SVR to software cost estimation.

• Journal of Platform Technology
• /
• v.11 no.5
• /
• pp.3-15
• /
• 2023

Requirements traceability link information is the basis for determining whether requirement change requested throughout the software development life cycle should be reflected in the system. Setting up complete requirements traceability links requires considerable effort. However, the commensurate benefits can be obtained in later development or further maintenance phases. For this reason, setting up and managing requirements traceability links in the software development phase are tasks that cause considerable resistance to developers. This study proposes a method for generating requirement traceability links in business applications. The key feature of the proposed method is that the traceability link from the requirements element, which is the basis of the corresponding element to the analysis element, is automatically established at the same time the elements of the analysis model are identified. This can be a way to reduce developer effort while increasing the efficiency of the traceability model. A case study on a Course Registration System demonstrates the feasibility of applying the proposed requirements traceability management method to actual software development.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 1993.04a
• /
• pp.62-71
• /
• 1993

Recently, the computer software technology is not keeping pace with the increasing demand of application software development and rapid changes in business environment. To overcome this "software crisis", many researchers have studied the methodologies to improve the productivity in software development and the flexibility of software usage. Among these methodologies, the most promising and intensively studied methodology is the Object-Oriented Approach The purpose of this study is, therefore, to examine the applicability of the Object-Oriented Approach for improving productivity and flexibility in Management Information Systems development. For an application, we selected a financial planning model, especially focusing on the budgeted income statement. In this thesis, we identified relevent objects in the budgeted income statement, and represented them in the object models. By implementing these object models using C++ language, we evaluated their adaptability in the budget-making process, and showed, by comparing them with the existing Planning '||'&'||' Modeling Languages such as IFPS(Interactive Financial Planning Saystem), their practicability in Management Information Systems. The results of this study are as follows: First, the same object models can be used in making the budgeted income statement both in the department level and in the corporate level. Second, the object models provide the flexibility and extensibility of an application program in case of the changes in business environment. Third, the Object-Oriented Approach is a practical methodology to improve the productivity and cut down the maintenance cost of application software development.t.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.6 no.3
• /
• pp.121-129
• /
• 2010

For the development of software industry, offers an expanded software authentication scheme caused by the unauthorized copying of software is to reduce the damage to software developers, retail sales and to promote the development of the software industry was studied. Serial Number of the current software registration is conducted in such a simple verification procedure if the Serial Number only illegal and can be installed on multiple computers, such as program code to allow third parties to enter the Serial Number, or the extract can be used without is a reality. The proposed extension to the software authentication system when you install the software, my phone authentication and MAC Address Authentication Service introduced to distinguish normal user, the user of the MAC Address of the server and software development company that was sent to the registered MAC Address of the computer to be run only by the use of genuine software and to make unauthorized copies of software generated by the software developer can reduce the damage of the proposed plan.

• 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.

• Journal of Korean Society of Archives and Records Management
• /
• v.5 no.1
• /
• pp.65-77
• /
• 2005

This paper aims to introduce the background history and development of records management in brief prior to and after the 1990s based on the records life cycle. This paper also explains the development of electronic document imaging systems and shifts to ERM systemsin the 1990s. The paper explains functional requirements in archival management and software application standards suggested by the industry of electronic records management. The paper concludes with providing problems and issues associated with software design in electronic records management for further development.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 1996.04a
• /
• pp.225-229
• /
• 1996

In order to accomplish large-size information systems successfully, one of the most improtant factor is the system integration(SI) of individual software projects which consist of the systems. A developer of each project should consider aspects of SI through the development cycle, and a manager of the entire system should manage, control, and evaluate each from a SI point of view. In this research, management models for the system managers, development models for the developers of unit projects, and standardized output documents for the management and evaluation purpose are presented based on the SI concepts.

• Journal of Convergence Society for SMB
• /
• v.6 no.1
• /
• pp.7-15
• /
• 2016

As most devices in a wide range of automotive, aerospace, and missile have built-in software that controls the system behaviors, the safety of the software is growing in its importance. That is, the software safety has emerged as one of big issues because the threat of accidents caused by software malfunction is rising. Accident by software can be occurred from user mal-operation, but the fundamental reason of the accident comes from insufficient verification of the safety in software development process. Therefore, this paper presents how the software safety analysis and management activities should be done in the development process. In particular, we propose how to apply the safety analysis and management activities in the prototype or incremental development process.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.22 no.1
• /
• pp.87-93
• /
• 2021

As the portion of modern weapons systems equipped with electronic components increases, the presence of embedded software has also increased, subsequently drawing interest in quality management and development methods. Unlike mechanical systems, software is logically intangible, hard to troubleshoot, and hard to reuse, making it hard to utilize limited resources when exposed to failures. The United States had successful results in establishing the Capability Maturity Model (CMM) by studying and applying separate processes for development and quality management of defense software. South Korea has also established, and utilizes, a standard of development and quality management for defense software based on international standards. However, some say those standards still remain at a basic level, and should be modified along with the progress in software. If the standard stays at a basic level, compared to software progression, the cost to reuse and restore resources will increase exponentially. This paper discusses improvement in the test processes for defense software through the Test Maturity Model-integration (TMMi)-derived from the CMM-and presents a blueprint for defense software quality management.

• Journal of Korean Society for Quality Management
• /
• v.13 no.2
• /
• pp.61-65
• /
• 1985

The quality of a final SOFTWARE PACKAGE depends on many complicated factors in the software development process. This paper describes ststistical methods for establishing relationships between final quality and development process factors. The final software quality is represented by the number of errors through the system test phase. The data presented here were gathered during the course of a real IS-month development project. Regression theory is used for data analysis. Some of the interesting results include the observation that specification changes during the development process have an adverse effect on final software quality.