• Industrial Engineering and Management Systems
• /
• v.11 no.1
• /
• pp.39-47
• /
• 2012

Requirements definition, which determines a project baseline, has a strong impact on the success of a project. However, since in-depth requirements are gradually revealed through the requirements definition process, the requirements definition is not a straight forward process and often falls into disorder. Thus project management standpoints are critical for the success of the requirements definition. In this paper, we present a framework and mechanisms of communication-centered project management, which controls the requirements definition process based on the situation of communication-oriented activities among stakeholders. In addition, we present a communication-centered project plan with a planning method. The project plan, which represents a time schedule of requirements definition activities, is made by a simulation-optimization algorithm using a stakeholder matrix showing the relations of requirements domains and relevant stakeholders. The effectiveness and the significance of communication-centered project management at the requirements definition phase are demonstrated by numerical examples.

• The Safety technology
• /
• no.48
• /
• pp.58-61
• /
• 2001

• The Safety technology
• /
• no.47
• /
• pp.60-63
• /
• 2001

• 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 Korean Society of Industrial and Systems Engineering
• /
• v.37 no.1
• /
• pp.68-78
• /
• 2014

Recently, companies are trying to gain a competitive advantage in the market to meet the voice of customer. For this purpose, QFD has been used as product development technology in many areas to include the customer' requirements. Also, Kano model has been used to understand the customer' requirements for an effective way. Therefore integration of Kano model and QFD can more efficiently reflect the customer' requirements when designing a new service. This paper proposes PI index by taking into account the current satisfaction position of our company and competitors while IR (Improvement Ratio) value was set uniformity. This study suggests a more accurate index to predict potential improvements and calculates the final importance or priority. Through case studies targeted at elevator maintenance companies, we can have a general idea how much to improve in the near future and estimate the final importance of customer requirements.

• The Journal of Korea Robotics Society
• /
• v.2 no.2
• /
• pp.196-204
• /
• 2007

In this paper, we are looking for requirements of software, hardware and application for use in network-based robots and also directions in building standardization and research activities by reviewing technical status of the robot industries developing robots. The questions are including awareness of RUPI(Robot Unifies Platform Initiative) activities, target market and applications, hardware specifications, software development technologies, and HRI(Human Robot Interaction). The RUPI committee creates standard and drives implementation software for network-based robots through industrial requirements as like of the results. Many robots have been developed and launched services based on RUPI 1.0 standards. Based on this achievement we are expanding RUPI standard to include thin and thick client robots. The results also show that which one is important and urgent technology in the sense of industrial robotic business.

• Journal of Technology Innovation
• /
• v.13 no.2
• /
• pp.1-22
• /
• 2005

This paper adopts an embeddedness perspective and discusses rationales for government intervention in relation to economic development. Looking at East Asian experiences with industrial and technology policy the paper examines the general requirements, specific areas of focus and appropriate techniques for industrial and technology policy. Eight generic policy requirements are identified, viz. government capacity; monitoring and adjustment; policy sequencing; incremental upgrading; progressive market reliance; performance-orientation; selectivity; and flexibility.

• Journal of Drive and Control
• /
• v.21 no.2
• /
• pp.44-52
• /
• 2024

In this study, we predicted PTO power requirements based on torque predicted by the discrete element method and the multi-body dynamics coupling method. Six different scenarios were simulated to predict PTO power requirements in different soil conditions. The first scenario was a tillage operation on cohesionless soil, and the field was modeled using the Hertz-Mindlin contact model. In the second through sixth scenarios, tillage operations were performed on viscous soils, and the field was represented by the Hertz-Mindlin + JKR model for cohesion. To check the influence of surface energy, a parameter to reproduce cohesion, on the power requirement, a simple regression analysis was performed. The significance and appropriateness of the regression model were checked and found to be acceptable. The study findings are expected to be used in design optimization studies of agricultural machinery by predicting power requirements using the discrete element method and the multi-body dynamics coupling method and analyzing the effect of soil cohesion on the power requirement.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.41 no.4
• /
• pp.160-170
• /
• 2018

This paper is an exploratory study on the success factors of Defence Quality Management System (DQMS) which is the certification system granted by the military for improving the quality of munitions. DQMS is established by adding military requirements to the ISO standard, thus, we especially focus on the additional requirements to figure out success key factors of DQMS certification. The 51 additional requirements of Korean Defense Specification (KDS) are empirically investigated from 67 companies that acquired DQMS certification. Firstly, we conduct an independent t-tests on 51 additional requirements of KDS 0050-900-3 to determine if there is a difference between an easily certified company and a hard-to-certify company, and obtain 8 requirements such as 'Internal propagation of performance', 'Preparation of documented work instructions', 'Work instructions in the workplace', 'Documentation of equipment management', 'Inventory management', 'Packaging and identification', 'Guarantee of access to internal audit result for customers', 'Notification to the customer for improper product.' Secondly, we carry out an factor analysis to the 51 additional requirements for classification, and figure out that 4 requirements among the 8 requirements above mentioned are grouped together in the same factor. The 4 requirements are 'Preparation of documented work instructions', 'Work instructions in the workplace', 'Packaging and identification', and 'Guarantee of access to internal audit result for customers.' The result of this paper will provide useful information to the company preparing for DQMS.

• Proceedings of the KIEE Conference
• /
• 2007.10c
• /
• pp.10-13
• /
• 2007

System requirements (SRs), which describe the technical attributes to be satisfied by a desired system, serve as a fundamental guideline for system development. Standard methods and processes to define SRs are suggested in systems engineering literature. But in practice, we encounter many difficulties in defining and managing SRs since there are few experiences on development of complex systems in accordance with systems engineering processes of development. In this paper, to expanding SRs management experiences in a working-level, we reviewed problems occured in SRs defining process in 'Urban MAGLEV Train Project', and analyzed our activities to adjust and solve the problems.