• Journal of Information Technology Applications and Management
• /
• 제20권3_spc호
• /
• pp.315-331
• /
• 2013

As the business has been highly informatized, many companies has bought the software for their works. There are two types of software license. One is a site license and the other is a user license. This paper is focused on the user license. User license has the number of the right to use software. So, software managers always need to know the number of licenses in use and should limit the number of software license in use. If someone in the company use a software without license, he will be treated as a piracy. In that case, the company should pay for the settlement cost for the exceeding license use. In this paper, we suggest the model how we can limit the installation of the software within the number of licenses by license management system.

• 한국IT서비스학회지
• /
• 제11권4호
• /
• pp.171-180
• /
• 2012

Since software and hardware integration has became a strategic tool for companies to innovate their products, an information system that can comprehensively manage software and hardware integrated product development is critical for the current product development. This paper proposed a product data model that can support modules of related software and hardware parts in Product Data Management(PDM) integrated with Software Configuration Management(SCM). The model allows engineers to define software and hardware product structure independently, and support the integration module that can summon related software and hardware parts to build a comprehensive module for collaboration. Through the integration module, engineers can identify and examine the effectiveness of their design alternatives to other related parts form different disciplines. The product data model was implemented as a prototype PDM system and tested with an example robotics product.

• 산업공학
• /
• 제21권2호
• /
• pp.198-208
• /
• 2008

Effective management of a project is a crucial issue to software companies. There are various international standards, such as CMM, ISO9000, and SPICE, applied to project management. But, small scale companies have some difficulties in accepting those standards because of its complexity and enormous manpower requirements. This study proposes a project management approach streamlining the CMM by which a small scale software company can perform the tasks with ease. A prototype system has also been developed to show the capability of the proposed model.

• 경영과학
• /
• 제15권2호
• /
• pp.59-70
• /
• 1998

According to the Gartner Group, the market for ERP software in Korea is growing rapidly. However, the number of successful ERP implementations is quite few. Standard(unmodified) ERP's are built based on best practices. Improvements expected from successful implementation are based on best practices built into the software. Many improvements are lost through modification to "standard" software. Even minor changes in software can significantly reduce benefits. Both implementation time and risk factors are increased with modifications. We introduce a methodology, called package Enable Re-engineering (PER) and the main components of change management program by Ernst & Young. "To-Be" model could be developed through the software capabilities. And change management processes such as continuous education and self-developments are required. The philosophy of the change management processes is to let the software package drive the re-engineering practices and avoid moving the software toward the "As-IS" process. Extensive top management involvement, major focus on speed, extensive communication program, and "clear" picture of the future are essential components of change management. We are sure that the complied experiences and model have implications for practice and for academicians for their endeavors in their fields.

• Journal of Communications and Networks
• /
• 제3권4호
• /
• pp.307-316
• /
• 2001

Two hard sub-problems have emerged relating to the use of mobile agents for service management tasks. First, what is their impact on security, and second, how can they receive a flexible capacity to adapt to an open range of different environments on demand, without introducing trio stringent prior assumptions. In this paper, we present work towards solving the second problem, which is of particular interest to management software, because it typically needs to excert fine-grained and therefore particular resource control. We suggest a mechanism that reassembles mobile agents from smaller sub-components during arrival at each hop. The process incorporates patterns of unmutable and mutable sub-components, and is informed by the conditions of each local environment. We discuss different kinds of software adaptation and draw a distinction between static and continuous forms. Our software prototype for dynamic adaptation provides a concept far exchanging environment-dependent implementations of mobile agents during runtime. Dynamic adaptation enhances efficiency of mobile code in terms of bandwidth usage and scalability.

• 시스템엔지니어링학술지
• /
• 제13권1호
• /
• pp.1-6
• /
• 2017

A stores management software which is embedded in the stores management system requires high-level reliability and real-time processing. It also required to implement and verify protocols which requires timing constraints to control various weapons. In this paper, we propose design methodology to design a stores management software and its support middleware based on the TMO (Time-triggered Message-triggered Object) model.

• 한국정보처리학회논문지
• /
• 제3권4호
• /
• pp.846-854
• /
• 1996

본 연구에서는 소프트웨어 위기의 주요 원인인 유지보수 문제를 해결하기 위한 방안을 제시하기 위한 것으로, 국내의 유지보수 문제점과 현황을 설문으로 기초 조 사·분석하고 면담과 문헌을 참고하여 문제점을 해결하고자 하였다. 연구의 결과로 유지보수 생명주기를 정의하고 유지 보수를 효율적으로 수행하기 위한 기본 전략을 수립하고, 수립된 기본 전략을 구현하기 위한 유지보수 지원 시스템을 개략 설계하여 유지보수 시스템의 자동화 설계를 위한 기반을 구축하였다.

• 한국통신학회논문지
• /
• 제22권9호
• /
• pp.1880-1889
• /
• 1997

CMS-MX(CDMA Mobile System-Mobile eXchange) 이동통신교환기 소프트웨어는 그 규모가 크고 새로운 기능 추가에 따른 지속적인 변경이 요구되기 때문에 체계적인 버전 관리를 필요로 한다. 그러나 CMS-MX 소프트웨어는 다양한 형태의 파일들로 구성되어 있고 고유의 소프트웨어 개발 체계를 따르기 때문에 범용의 버전 관리 시스템을 그대로 적용하기가 어렵다. 본 논문에서는 CMS-MX 소프트웨어의 개발 환경 및 개발 체계에 적합하도록 구현된 CMS-MX 소프트웨어 버전 관리 시스템을 소개하고 그 구성과 기능에 대해 기술하였다. CMS-MX 소프트웨어 버전 관리 시스템은 소프트웨어 형상과 소프트웨어 개발자 정보를 하여 파일의 등록관리, 버전제어, 그리고 정보 관리의 기능을 수행하며 파일 전체 저장, 파일 검증, 소프트웨어 종합 작업과의 연계등의 특징을 가지고 있다.

• Journal of information and communication convergence engineering
• /
• 제4권1호
• /
• pp.23-27
• /
• 2006

The discipline of software performance is very broad; it influences all aspects of the software development lifecycle, including architecture, design, deployment, integration, management, evolution and servicing. Thus, the complexity of software is an important aspect of development and maintenance activities. Much research has been dedicated to defining different software measures that capture what software complexity is. In most cases, the description of complexity is given to humans in forms of numbers. These quantitative measures reflect human-seen complexity with different levels of success. Software complexity growth has been recognized to be beyond human control. In this paper, we have focused our discussion on the increasing software complexity and the issue with the problems being faced in managing this complexity. This increasing complexity in turn affects the software productivity, which is declining with increase in its complexity.

• Journal of Information Technology Applications and Management
• /
• 제20권3호
• /
• pp.1-18
• /
• 2013

Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders' concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder's concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.