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

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

• The Journal of Korean Association of Computer Education
• /
• v.7 no.1
• /
• pp.27-35
• /
• 2004

Software documents consist of a number of objects and relationships between them, and structure of documents can be changed frequently. In the existing software version management models, changes in one object may be propagated to other objects unnecessarily. In this paper, we propose an efficient version management model for software objects based on history of operations applied to software objects. Operations applied to objects are recorded in the operation history, and those are used to retrieve versions of a document. Because versions of objects are stored and retrieved using the operation delta, it is not required to compare versions of a document to extract delta during check-in process. In addition, it can manage changes of structure of objects efficiently because it supports not only object creation, deletion, and update operation but also object move operation.

• Industrial Engineering and Management Systems
• /
• v.11 no.1
• /
• pp.70-81
• /
• 2012

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

• Journal of Veterinary Clinics
• /
• v.24 no.2
• /
• pp.142-149
• /
• 2007

The purpose of this study was to develop a computerized software program to help for reproductive management in dairy cows. The developed software program in the study is compatible with a window 95/98 or XP system. Data in the system were recorded, stored, and processed from two sources: 1) Data downloaded monthly from the database of the Korean Dairy Herd Improvement Association (milk yields, milk somatic cell counts, milk fat, protein, lactose and urea nitrogen content). 2) Data recorded by the farmer or veterinarians by the time (body condition score, heats, inseminations, veterinary diagnosis and treatments). These data indices after processing by computerized dairy management system were presented by numerical or graphical display. The presented data were obtained from three dairy farms with more than 50 milking cows. The presented reports of this program using milk fat, protein, urea nitrogen, and somatic cell counts enabled the dairy producer and veterinarians to monitor the protein-energy balance and feeding management practice, and for distribution of diseases (mastitis, metabolic and reproductive disorder) in individual cows. The presented analytical reports of this program also included herd average of reproductive indices such as day to first insemination, days open, and inseminations per conception. This software program will assist in analysis, interpretation and demonstrate the results of reproductive trials conducted in dairy herds.

• Journal of Internet Computing and Services
• /
• v.22 no.3
• /
• pp.59-66
• /
• 2021

This study proposes a requirements monitoring method that systematically performs traceability management and change management for requirements in order to improve the quality of software systems in the software development process. To this end, we present the artifact change history management models to systematically perform change management for individual artifacts and the traceability matrixes to define the relationship between artifacts. It also proposes a visual dashboard that makes it easy to grasp the situation in which changes are propagated to related artifacts when specific artifacts change.

• International journal of advanced smart convergence
• /
• v.8 no.4
• /
• pp.207-213
• /
• 2019

Assistance for the quality assurance management and developers to provide high quality software products. Using a bug record keeping system is exceptionally important in software progress, and it is followed vastly by majority of software producing companies in modern era. Regular application of a bug record keeping system is very helpful in developing software systems. We developed this system which helps the software testing team to keep a complete record of their testing activities during the software testing, also increases your confidence in the software quality, class and worth. Our proposed system offers trouble-free and effortless approaches to acquire desired information about bug, also produces different kinds of reports like summary reports, detailed reports etc. It gives facility to create, delete and update any project. Our developed application system is designed by using visual c# at front end and sql server 2008 management studio express at back end.

• Korean Management Science Review
• /
• v.9 no.1
• /
• pp.31-40
• /
• 1992

The size of software collection at any organization is increasing rapidly with the use of computer becomes popular for various applications. This trend points out the importance of proper 'catalog'or 'directory' for software collections, however, only 'title list' is found in practice. The problem of no proper directory with software collection would be more serious than the problem with book collection since browsing is not possible with softwares. Many of the expensive softwares will be a waste of money to purchase and to hold if no catalog about them is provided. In this paper the difficulties in applying AACR2 to software cataloging and the most important characteristic of computer software are discussed as well as presenting the necessity of localized information due to the requirement of a machine to be used, the difficulty using subject-based-call-number scheme, an expected way of searching software to design a location indicator, software qualifications to be cataloged, and so on. In addition, an analysis of randomly selected softwares after a cataloging practice is followed.

• Journal of Computing Science and Engineering
• /
• v.4 no.4
• /
• pp.253-275
• /
• 2010

In this article we review the metaphor of service-oriented architecture for enterprise computing. In typical definitions service-oriented architecture appears as a single message and a consistent roadmap for building flexible software system landscapes. But it is not. Different communities have elaborated different SOA (service-oriented architecture) concepts to address different problem areas, i.e., enterprise application integration, business-to-business, business process management, and software productizing. If software architects and software managers are aware of these strands of SOA when talking about SOA in their projects they can avoid misunderstandings and detours better. This article contributes a clarification of the different strands of SOA concepts and technologies and their mutual dependencies and identifies particular SOA concepts as instances of more general software engineering principles.