• The Journal of Society for e-Business Studies
• /
• v.12 no.3
• /
• pp.33-47
• /
• 2007

The requirements have been changed during development progresses, since it is impossible to define all of software requirements. These requirements change leads to mistakes because the developers cannot completely understand the software's structure and behavior, or they cannot discover all parts affected by a change. Requirement changes have to be managed and assessed to ensure that they are feasible, make economic sense and contribute to the business needs of the customer organization. We propose a feature-oriented requirements change management method to manage requirements change with value analysis and feature-oriented traceability links including intermediate catalysis using features. Our approach offers two contributions to the study of requirements change: (1) We define requirements change tree to make user requirements change request generalize by feature level. (2) We provide overall process such as change request normalization, change impact analysis, solution dealing with change request, change request implementation, change request evaluation. In addition, we especially present the results of a case study which is carried out in asset management portal system in details.

• Knowledge Management Research
• /
• v.19 no.1
• /
• pp.1-18
• /
• 2018

As the online space becomes more active, interest in protecting personal information is increasing. From this point of view, it is important to prevent personal information from being leaked in advance. As a precaution, it is suggested that users change their password periodically to protect their personal information effectively. Currently, various online services provide a request message that prompts users to periodically change their password. These messages are expressed as positive-centric or negative-centric. This message can be seen as a powerful way to trigger users' behavior. In this context, this study suggests that message framing type can be applied to the password change request message, and to investigate the difference between the positive-centric message and the negative-centric message. In addition, this study concluded that the effect of message type may be different depending on the degree of psychological ownership of the individual on the online service. As a result, users with high psychological ownership in online service were more effective when positive-centric message was presented than negative-centric message. On the other hand, users with low psychological ownership in online service were more effective when negative-centric message was presented than positive-centric message.

• Journal of Korea Game Society
• /
• v.5 no.1
• /
• pp.33-40
• /
• 2005

Game Designs & Developers that system designs improve, the product and the change of tasks to all developers are essential in achieving On-Line Game project. Existent Or-line Game project management designs supper the definition and the change of project activities, and configuration management designs support version check, workspace management, build management, etc. In this paper. the proposed Design defines Game component based development process model, and achieves recording of process progression, processing the request of change, reporting the progression of each task, product registering and change, version recording, artifact or form search, etc. using UML. Furthermore, study on the stake holders get the systematic management and standardization by sharing information that are necessary in Game design & development and configuration management in distributed environment using the system integrated management design.

• Journal of Korea Game Society
• /
• v.4 no.3
• /
• pp.21-28
• /
• 2004

Game Designs & Developers that system designs improve, the product and the change of tasks to all developers are essential in achieving On-Line Game project. Existent On-line Game project management designs supper the definition and the change of project activities, and configuration management designs support version check, workspace management, build management, etc. In this paper, the proposed Design defines Game component based development process model, and achieves recording of process progression, processing the request of change, reporting the progression of each task, product registering and change, version recording, artifact or form search, etc. using UML. Furthermore, study on the stake holders get the systematic management and standardization by sharing information that are necessary in Game design & development and configuration management in distributed environment using the system integrated management design.

• Proceedings of the CALSEC Conference
• /
• 1997.11a
• /
• pp.443-461
• /
• 1997

ㆍProSTEP, PDES, Inc., and JSTEP announce agreement on PDM Schema ㆍ November 4, 1997 ㆍInteroperable with STEP AP203, AP2l0, AP214, and AP232 ㆍNeutral specification allows for the exchange of the following types - item master data (part identification, approval of part version) - item structure - item classification - item property (mass, costs) - document management (identification, revision… ) - work management (engineering change request, EC order, project) ㆍVendors of PDM systems are asked to join ProSTEP's PDM Round Table and PDES, Inc.'s PDMnet.(omitted)

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 1997.10a
• /
• pp.33-36
• /
• 1997

본 연구에서는 공동 작업에 참여하는 작업자들의 업무흐름(workflow)을 관리하기 위한 워크플로우 엔진의 프로토타입을 개발하였다. 분산 객체관리의 표준으로 정착되어 가고 있는 CORBA(Common Object Request Broker Architecture)를 이용하여 네트워크 프로그래밍을 하였으며, JAVA를 사용하여 프로그램의 호환성과 이식성을 높였다. 또한, HAD(heterogeneous and autonomous and distributed) 환경에서 작동 가능하도록 엔진을 설계하였다. 따라서, 공동작업에 참여하는 작업자들이 플랫폼에 상관없이 네트워크를 통해 엔진에 접속할수 있으며, 워크플로우 엔진은 공동 작업을 진행 및 감독할 수 있다. 본 연구에서 개발한 시스템을 설계 작업에서의 변경요청(ECO:Engineering Change Order)이라는 업무흐름에 적용하여 보았다.

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

• The Journal of Information Systems
• /
• v.19 no.2
• /
• pp.37-71
• /
• 2010

This article identifies factors affecting successful ERP systems by focusing on the stages after stabilizing ERP systems and overcoming temporary performance dip by introduction of ERP systems, and suggests change management tactics to control those identified factors. We can not expect that every users are familiar with the usage of an ERP system even after they are informed about the expected advantage of the newly implemented ERP system and trained intensively for changed business process and system usage while implementing a new ERP system. Moreover, even after more than six months usage of the system, the users may still have some trouble due to the reason why they have insufficient information about the expected advantage of the system (recognition gap) and insufficient knowledge about the changed usage of the system (knowledge gap). Hence, this article diagnoses by conducting a case study that those recognition and knowledge gap would have a severe bad influence upon the users' trust and satisfaction on ERP systems. This article suggests an appropriate change management tactics to overcome those recognition and knowledge gap by considering the relationship with the efforts for change management before, during, and after the introduction of ERP systems and performing an in-depth analysis on the users' dissatisfaction and request for update during the stages after the stabilization of the ERP systems. This article also shows a corroborative evidence that these efforts of change management consequently contributes to the solution of users' distrust and dissatisfaction. In sum, this article identifies the factors influencing badly on the magnitude and seriousness of knowledge and recognition gap, and suggests a conceptual research model which says that the satisfaction of ERP users could be uplifted by the solution of their knowledge and recognition gap if we keep making efforts on appropriate change management considering those identified factors during the stages after the stabilization of an ERP system.

• Journal of Internet Computing and Services
• /
• v.5 no.4
• /
• pp.11-22
• /
• 2004

Works that improve the process and notify the improved process, the product and the change of tasks to all users are essential in achieving project. Existent project management tools support the definition and the change of project activities, and configuration management tools support version check, workspace management. build management. etc. It costs too much to buy each tool. as well as, it is burdensome to learn usage for various tools. Therefore the web-based integrated tool is proposed to manage the process and artifacts at a time in this paper. The proposed tool defines component based development process model. and achieves recording of process progression, processing the request of change, reporting the progression of each task, product registering and change, version recording, artifact or form search, etc. using ebXML. Furthermore, the stakeholders get the systematic management and standardization by sharing information that are necessary in process achievement and configuration management in distributed environment using the integrated management tool.

• Journal of the Korea Safety Management & Science
• /
• v.16 no.1
• /
• pp.69-77
• /
• 2014

The environment and requirements of modern war fields have been affected and thus changed by a variety of issues. To this end, the development of safety-critical weapon systems frequently need to meet those changes even in the operational phase. The necessity of the changes may be due to the preparation for mass-production or the request originated from the user military forces. To meet such a need can be even tougher in the development of safety-critical weapon systems since the integration of the requirements for both systems design and systems safety would make it troublesome. To handel the matter in this paper, utilization of architecture DB is proposed. Specifically, the situation in demand has first been analyzed and then a problem-solving process to accommodate the design changes has been constructed. In doing so, the concept of the aforementioned integration is particularly focused on the functional architecture, which could be a core concept of our approach to solving the problem. The result of a case study demonstrating the method studied using a computer-aided systems engineering tool is also presented.