• Proceedings of the Korean Society for Quality Management Conference
• /
• 1998.11a
• /
• pp.429-434
• /
• 1998

QS-9000 was established by Chrysler, Ford, General Motors and some Truck Manufactures to solve problems of efforts to prepare original standards for each company. When we compare the requirements in QS-9000 with those in ISO 9000, we may observe that those of QS-9000 are more specific, since the user of the standard is limited to the automobile industry. In particular, the requirements on statistical techniques are described in more detail. In this paper, we present the requirements on statistical techniques in QS-9000. Specifically, we review the contents of QS-9000 and explore the philosophy and the minimum requirement on statistical techniques behind the description.

• IE interfaces
• /
• v.17 no.3
• /
• pp.261-268
• /
• 2004

The primary goal of the requirement analysis phase during information system development is to identify and document what is really needed, in a form that clearly communicates to the user and to development team members. Presented in this paper is a QFD(Quality Function Deployment)-based requirement analysis method and procedure for developing a large-scale enterprise information system. For the purpose of elicitation of software functional requirements, this paper adopts the method of HOQ(House Of Quality) and proposes a simplified HOQ which is more suitable for the software requirement analysis. As a result of this paper, it suggests desired functionalities for an integrated design &manufacturing information system.

• Journal of the Korean Society of Systems Engineering
• /
• v.10 no.1
• /
• pp.81-86
• /
• 2014

Systems Engineering application focused on requirement definition and management for SURION System Development Project is described in this paper. To perform the development process effectively based on systems engineering processes; Requirements Definition, Design Review, Configuration Management, Quality Assurance, Data Management, are applied in this project. In this processes, the Stakeholder's Requirements are transferred to Specifications verified with design reviews, prototyping inspections, and integration tests. All engineering data, especially verification plan & results are recorded, and traced to each requirements of system specification in Surion database. Therefore, it could be assured that all requirements of specification are evaluated and verified successfully in Surion Project.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.28 no.2
• /
• pp.60-68
• /
• 2005

ISO 9000 quality standards families were established in 1987 and have been started to implement Korean industry since early 1990s. ISO 9000 standards families of 1987 were revised in 1994 and 2000, respectively, by request of world wide certification bodies and industry quality experts. This article reviews the necessity of ISO 9001 :2000 revision, quality management principles behind it, and benefits that ISO 9001: 2000 could bring. We summarize responses of foreign industry that ISO 9001: 2000 has been implemented. Survey questionnaire for 23 requirements of ISO 9001: 2000 from manufacturing companies of Busan and Kyungnam provinces are collected. Research hypotheses that there is any difference in quality management system practical application due to company size and implementation motivation are tested using SPSS. Finally, recommendations are provided for operating successful quality management system.

• The KIPS Transactions:PartD
• /
• v.11D no.7 s.96
• /
• pp.1459-1466
• /
• 2004

As the area of software application is increased. the software is becoming larger and more complex. In addition, development of the high quality software within the limits of the budget is strongly demanded. Many methodologies, such as software process improvement, object-ori-ented development, requirement-engineering, and software metrics have been introduced in the software development process in order to attain such objectives. Among those techniques. Requirements-Engineering gives basic guideline to develop high quality software. In other word. in order to develop high quality software, requirements should be elicited, and described. And with proper reviews and management. the quality of requirements can be improved. In this paper, quantitative measurement method that is based on IEEE Std-830-1998 for the require-ment-specifications is proposed.

• Journal of Korean Society for Quality Management
• /
• v.46 no.4
• /
• pp.821-842
• /
• 2018

Purpose: To derive key requirements and key technologies for weapon system acquisition business by using Qualify Function Deployment (QFD), and to reduce business cost by setting the target performance and key expense of weapon system. Methods: We propose a QFD methodology that can induce rational decision-making by translating analyst's subjective opinions into quantitative values when analyzing requirements at the initial stage of weapon system development project. Based on QFD methodology, QFD application model combining house of quality, value engineering, and analogy cost estimating technique is presented. Results: It was possible to analyze the specific requirements necessary for the development of the weapon system, to solve the communication problem of the participants, to set clear development direction and target. Conclusion: By applying the QFD application model at the early stage of the weapon system acquisition project, it is possible to reduce the business cost by establishing clear development direction and goal through the procedural analysis process.

• 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 the Korea Society of Computer and Information
• /
• v.26 no.3
• /
• pp.99-109
• /
• 2021

In recent machine learning studies, in order to consider the quality and completeness of data, derivation of non-functional requirements for data has been proposed from the viewpoint of requirements engineering. In particular, requirements engineers have defined data requirements in machine learning. In this study, data requirements were derived at the data acquisition (DAQ) stage, where data is collected and stored before data preprocessing. Through this, it is possible to express the requirements of all data required in the existing DAQ system, the presence of tasks (functions) satisfying them, and the relationship between the requirements and functions. In addition, it is possible to elicit requirements and to define the relationship, so that a software design document can be produced, and a systematic approach and direction can be established in terms of software design and maintenance. This research using existing DAQ system cases, scenarios and use cases for requirements engineering approach are created, and data requirements for each case are extracted based on them, and the relationship between requirements, functions, and goals is illustrated through goal modeling. Through the research results, it was possible to extract the non-functional requirements of the system, especially the data requirements, from the DAQ system using requirements engineering.

• Proceedings of the Safety Management and Science Conference
• /
• 2007.11a
• /
• pp.299-303
• /
• 2007

This paper deals with conformity assessments requirements for accreditation and certification bodies. This study also introduces conformity guidances of product certification and code of good practice. This paper presents general requirements for accreditation, recognition and registration bodies of environmental quality system and product certification.

• Journal of Distribution Science
• /
• v.17 no.2
• /
• pp.101-107
• /
• 2019

Purpose - The purpose of this study is to analyze the user requirements and developer requirements in virtual reality(VR), and suggest ways to increase the satisfaction of users who experience virtual reality. Specifically, focused on experience store of VR as a distribution retailer, user requirements were analyzed according to the results of previous research that the characteristics of Affordance, Presence, and Head Mounted Display (HMD) affect user satisfaction. Research, design, data, and methodology - Based on previous studies, in this study, we analyzed the importance of immerse, interaction, perception, and presence for the satisfaction of the user through the questionnaire, and the user experiences virtual reality (VR) The importance of HMD, Presence, Affordance, and experience satisfaction were analyzed. Based on this, we analyzed the user requirements and the developer requirements based on the questionnaires and interviews of the experts, starting from the user's desire or preference using QFD technique. Results - As a result of the analysis, the development factors that occupied a big part in the virtual reality field appeared to be visual. In detail, this showed that there was a lack of sense of presence for users. This should be improved. This paper shows that the requirements for visual, auditory, and tactile development are necessary. For the satisfaction of the users of virtual reality (VR) users, it is necessary to develop them according to their priority in consideration of importance and difficulty in the future. Conclusions - In this study, it was suggested that development according to priority should be considered, considering the difficulty level. Based on the results of this study, the following suggestions are made. First, we tried to search the list of user requirements as much as possible, but it is likely to change due to the development of VR technology. Therefore, it is necessary for developers to continually supplement user requirements with recent research literature. Second, development priorities according to difficulty level should be considered. This aspect should be considered in the actual VR development process, so if the numerical value of the difficulty is calculated, it should be presented in the research.