• KIPS Transactions on Software and Data Engineering
• /
• v.4 no.1
• /
• pp.31-36
• /
• 2015

There are many uncertainty items when we're working on a software. Especially, if we don't have experience in similar field, ambiguity items have a strong influence on the system entirely. Management of ambiguity items such like uncertainty things is important the factor for reliability of software. Therefore, this research is processing the evaluation criteria for remove of uncertainty items by identify of ambiguity items. Also, this research provides criteria of uncertainty identify and processing of uncertainty items, quantitative evaluation criteria to the remove of ambiguity on software development.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.12 no.1
• /
• pp.139-139
• /
• 1987

This study addresses basic requirements for mathematical programming software, discusses considerations in designing these software, implementation issues facing in these types of applications development, and shows some examples of codes being developed in the course. This type of projects requires long and ever-changing evolutionary phases. The experience is therefore, valuaable in suggesting some useful hints which may be salvaged for similar projects as well as providing reusable codes. In particular, scanning and parsing the free-format inputs, symbol table management, mixed-language programming, and data structures dealing with large sparse matrices are indispensable to many management science software development. Extensions to be made are also discussed.

• Knowledge Management Research
• /
• v.16 no.2
• /
• pp.227-248
• /
• 2015

SPI (Software Process Improvement) activities have been considered one of the crucial approaches to achieve high quality, productivity and timely delivery of software products and services. The basic premise of SPI model is that higher maturity levels lead to better performance. In this research, the relationships between SPI results and performance were empirically investigated with Korean software companies. CMM key process areas were categorized into two dimensions, "Process Implementation" and "Quantitative Management". The relationship between process implementation and performance was significant, but the relationship between quantitative management and performance was insignificant. The control variable, size of OU(Organizational Unit), did not have significant impact on the relationships between SPI activities and OU performance.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.22 no.1
• /
• pp.173-184
• /
• 1997

As the scale of the switching software gets large, it takes much time and is hard to compile and the manage it. We implement the compilation management system for the mobile switching software on network file system and describe its structure and functions in this paper. The compilation management system distributes its task of compilation to the each network system equally to reduce the comilation time and also simplifies the management of the communications among the systems, compilation manager, and the software devedlopers.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.31 no.1
• /
• pp.37-53
• /
• 2006

SPI (Software Process Improvement) activities have been considered one of the crucial approaches to achieve high quality, productivity and timely delivery of software products and services. The basic premise of SPI model is that higher maturity levels lead to better performance. In this research, the relationships between SPI results and performance were empirically investigated with Korean software companies. CMM key process areas were categorized into two dimensions, 'Process Implementation' and 'Quantitative Management'. The relationship between process implementation and performance was significant, but the relationship between quantitative management and performance was insignificant. The control variable, size of OU(Organizational Unit), did not have significant impact on the relation ships between SPI activities and OU performance.

• Asia pacific journal of information systems
• /
• v.16 no.3
• /
• pp.143-158
• /
• 2006

Identifying risk factors in software risk management is imperative for project managers. The purpose of this paper is to provide software project risk factors validated by statistical analysis, and thus to help project managers alleviating the possibility of software project failure. Factor analysis with data collected from 264 Korean project managers and consultants identified 12 categories and 46 risk factors. T-test results showed that project managers and participants had statistically different perception on 3 risk factors among those 46 risk factors. We concluded by discussing implications of our findings and future research directions.

• KIPS Transactions on Software and Data Engineering
• /
• v.9 no.7
• /
• pp.205-212
• /
• 2020

Defects are an important factor in the quality of software developments. In order to manage defects, we propose additional information of search and classification. Additional information suggests a systematic classification scheme and method of operation. In this study, we propose additional information at the requirements analysis stage for defect management.

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2022.01a
• /
• pp.263-264
• /
• 2022

본 논문은 회사 직원들의 재택근무와 출퇴근 관리를 위한 Web 페이지이다. 프로젝트의 핵심 기능은 캘린더를 이용한 직원들의 출퇴근 관리로 근태, 재택, 휴가, 급여 관리 기능이 포함되어있다. 각 회사에서 이 프로그램을 이용할 시 직원들은 출근, 퇴근 버튼 기능으로 시간을 기록하고 휴가신청과 재택근무 일정을 확인할 수 있다. 관리자들은 직원들의 출퇴근 일정 목록과 재택일정, 휴가일정을 확인 가능하고 수정, 관리할 수 있다. 채팅 기능을 활용하여 직원과 관리자의 원활히 소통이 가능하다. 회사에서 필요한 근태 관리 시스템 기능들을 제공한다.

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2023.07a
• /
• pp.561-562
• /
• 2023

본 연구는 상태관리를 위한 새로운 모델, Quantum State Management (QSM)을 제안한다. QSM은 어플리케이션의 상태를 Quantum이라는 최소 단위로 나누어 비동기 및 병렬처리를 최적화하며, 상태의 추적가능성을 높이는 모델이다. 본 연구에서는 QSM의 개념을 제시하고 이를 Flux 패턴의 Redux와 비교하여 QSM이 갖는 장점과 비교한다.

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