• 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 KSR Conference
• /
• 2008.06a
• /
• pp.1083-1088
• /
• 2008

The first task for the development of a train system is to define the system and to determine its requirements. Reliability target is one of the requirements defined in the system requirements. In railway applications it is advised to follow the procedures given in IEC 62278 to fulfill reliability requirements. The reliability requirements are derived from the customer's needs. The way in which the system requirements reflect the customer's needs is strongly dependent on the characteristics of the product. In general the customer of commercial trains presents the system requirements from their needs. However, the relation between the customer and supplier is equivocal for a project to development a prototype train, and the reliability program should be different from that of an usual commercial project. This paper deals with the reliability management and assessment plan carried out for the on-going "Next generation high-speed train development project".

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

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.44 no.2
• /
• pp.124-131
• /
• 2021

In the recent business environment, risks related to product safety problems are increasing. These are arising from various factors such as increasing product and production complexity, supply chain diversification, enhanced PL (product liability) law and strengthening regulations of the government. Accordingly, ISO (international organization for standardization) published standards of PSMS (product safety management system) for suppliers such as ISO 10377 and ISO 10393. Meanwhile, the ISO 9001 QMS (quality management system) was revised in 2015, and it has established itself as an effective tool that can consistently meet the various requirements of stakeholders and promote customer satisfaction. This study aims to suggest an integration framework of QMS and PSMS based on the recent ISO international standards. To this end, firstly, the relationship between QMS and PSMS is studied based on the quality and product safety definitions, PDCA (plan-do-check-act) cycle and risk-based thinking. Secondly, the requirements of ISO 10377 and ISO 9001 are compared and classified as the common and ISO 10377 specific requirements. Finally, integration steps of two systems are suggested and guidelines that can systemize the integrated requirements are presented in the aspect of processes and documentation. This study is expected to be used as a guideline that helps companies those have already acquired QMS certification to build an international-level product safety management system early.

• Journal of Korean Society for Quality Management
• /
• v.39 no.4
• /
• pp.516-526
• /
• 2011

The AS9100 standard builds upon the ISO 9001:2000 quality management system requirements(in their entirety) and defines additional quality management system requirements for the aerospace industry. The 9100 standard on quality management system requirements is intended to be used at all levels of the supplier chain. The International Aerospace Quality Group has released a revision to 9100 for the aviation, space and defense industries. This change aims at improvement on quality, schedule and cost performance by adopting new requirements based on stakeholders' needs. This paper is to review how the AS9100 QMS Requirement has been established and improved, and to communicate the significant changes from AS9100, Rev. B to Rev. C focusing on reasons for revisions. The proposed schedule and considerations on the transition of the changes to Rev. C are also dealt with in this paper.

• Journal of Information Technology Services
• /
• v.20 no.1
• /
• pp.41-54
• /
• 2021

The SW-centered battlefield management information system R&D project takes a long period of 5-10 years or more by applying a complex and rigid batch acquisition strategy. In order to solve this problem, it is necessary to institutionalize a rapid and flexible battlefield management information system R&D project management procedure applying agile development methodology, and a government project management organization and contract management method to support it In this study, we analyzed the case of applying the Agile development method centered on Scrum to the US SW-centered weapon system R&D project and the characteristics and problems of the battlefield management information system R&D project in Korea, and suggested improvement measures as follows. First, the battlefield management information system R&D model applies the hybrid development method, and the system requirements analysis and system structure design use the existing waterfall development procedure, and the agile method is applied from the SW requirements analysis to the system integration stage. Second, flexible adjustment of performance, schedule, and cost by organizing an Agile IPT in which military (requirements) - DAPA (project management) - developer - functional specialized organizations (test and evaluation, quality, government research institutes, etc.) participate. Third, improving the Basic Order Agreement so that it can be applied to agile R&D.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.13 no.5
• /
• pp.801-807
• /
• 2010

Requirements management is one of the most essential activities of systems engineering in developing successful weapon systems. Particularly it is very important to consistently manage the traceability among the user requirements, the system requirements, the development specifications and the testing plans throughout the entire life cycle of the weapon system. However, the most part of requirements-related activities has centered around the functional and performance requirements but the integrated logistics support(ILS) requirement has not properly been managed. In this regard, a special attention is needed to develop and manage the ILS requirements. To do so, the ANSI/EIA-632 standard can be referred as a starting point since the ILS requirements of the weapon system under development are specified by the enabling products whereas the functional and performance requirements are covered by the end product requirements. Specifically, we first review and model several cases of previous weapon systems development, which reveals the problem of interest. Then, under the framework of ANSI/EIA-632, we study a hierarchical model for effectively managing ILS requirements by analyzing the features of ILS requirements. Finally, the value of the proposed model is discussed through the case study of electronic warfare equipment.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.503-514
• /
• 2003

In conventional development methodologies, requirements are considered to be not changing after analysis phase, and requirements specifications are used for the next step system design purpose. But in the real world, requirements can be changed and modified throughout the development life cycle according to end-user's more understanding about the target system, new IT technologies, changes of customer environment and market situation, and so on. So there needs a requirements change management process that can extend requirements management over the entire development life cycle and can support managing changes to the requirements after design phase. In this paper, a requirements change management process that can be integrated into conventional development methodologies is proposed to support the extension of requirements life cycle and managing changes to the requirements after design phase. This process was evaluated through an verification test with a widely used development methodology‘MaRMI’.

• Journal of the Korea Safety Management & Science
• /
• v.9 no.6
• /
• pp.89-96
• /
• 2007

It is well known that the test and evaluation plan (TEP) is very crucial in the successful development of safety-critical systems. As such, this paper discusses an approach to the development of the TEP for a system that should meet safety requirements in the systems development process. It is studied how to incorporate the result of preliminary hazard analysis (PHA) in generating the safety requirements. It is also discussed how to deal with them when the system requirements (i.e., functions, performance, constraints, components, etc) and the safety requirements are integrated into one model. While doing so, we have constructed the required traceability among them, which is necessary and very useful when the safety requirements need to be corrected or be changed. The use of the traceability makes it possible to easily check out whether and how the safety requirements are properly incorporated in the system design process. Furthermore, without the verified traceability, the system cannot be changed or upgraded later. In order to implement the model on a computer-aided tool, we have constructed a database (DB) schema. As a result, the implemented model/DB allows to automatically generate TEP which can be used to measure the performance and safety level of the developed system.

• Journal of the Korea Safety Management & Science
• /
• v.13 no.4
• /
• pp.161-169
• /
• 2011

International Organization for Standardization has recently published ISO 9001:2008 which is the basic requirements for a quality management system that an organization must fulfil to demonstrate its ability to consistently provide products that enhance customer satisfaction and meet applicable statutory and regulatory requirements. Not many empirical researches based on ISO 9001:2008 have been done up until now. In this article we outline transitional features for ISO 9000 quality management system (QMS) since its first publication in 1987. In order to effectively maintain ISO 9001:2008 QMS certification and continuously enhance quality management activities, we perform statistical analysis for the minor nonconformity data generated from follow-up audits for subcontractors of shipbuilding industry based on ISO 9001:2008 requirements. A Kruskal-Wallis test is used to show relationships between the minor nonconformity data and three classification criteria: the type of business, the size of business, and the number of follow-up audits.