repository
An Approach to Defining the Required Capability of a Weapon System using Universal Naval Task List
| DC Field | Value | Language |
|---|---|---|
| dc.contributor.advisor | 박범 | - |
| dc.contributor.author | 원유재 | - |
| dc.date.accessioned | 2022-11-29T02:32:12Z | - |
| dc.date.available | 2022-11-29T02:32:12Z | - |
| dc.date.issued | 2020-08 | - |
| dc.identifier.other | 30083 | - |
| dc.identifier.uri | https://dspace.ajou.ac.kr/handle/2018.oak/19715 | - |
| dc.description | 학위논문(박사)--아주대학교 일반대학원 :시스템공학과,2020. 8 | - |
| dc.description.tableofcontents | Ⅰ. Introduction 1 1.1 Thesis Background and Purpose 1 1.2 Thesis Scope and Method 5 1.3 Thesis Composition 9 Ⅱ. Review of Literature and Problem Definition 10 2.1 Major Concept and Pre-Study on Combat Development 10 2.1.1 Capabilities-based Planning 10 2.1.2 Concepts and Roles of Combat Development System 15 2.1.3 Advance Research on Combat Development 30 2.2 Problem Definition 40 Ⅲ. Methodology for Defining the Required Capability of a System 45 3.1 System Concept Definition 51 3.1.1 Operational Concept 51 3.1.2 Operational Concept Development Process 56 3.2 Required Capability Identification 65 3.2.1 Joint Capability Area 65 3.2.2 Identification of Required Capability from Concept 68 3.3 Attributes Selection 71 3.3.1 Attribute 71 3.3.2 Derivation and Definition of Attributes for Each Required Capability 73 3.4 Selection of UNTL Tasks and Deriving Metrics 76 3.4.1 Metric 76 3.4.2 Selection of Metrics by the Attribute based on UNTL 83 Ⅳ. Application and Evaluation of Methodology 89 4.1 Cases of Applying the Previous Threat-based 90 4.1.1 Necessity 90 4.1.2 Formation 92 4.1.3 Operational Concept 92 4.1.4 Required Operational Performance 92 4.2 Cases of Applying the Proposed Model 96 4.2.1 System Concept Definition 96 4.2.2 Required Capability Identification 115 4.2.3 Attributes 119 4.2.4 UNTL Tasks and Metric 121 4.3 Derivation of the Operational Requirements and Verification 134 4.3.1 Operational Requirements based on OCD 134 4.3.2 Operational Requirements based on ORD 137 4.3.3 Evaluation based on Requirements Demonstration Criteria 140 4.4 Verification based on the Evaluation Indicators 147 4.4.1 Process Evaluation Model 147 4.4.2 Verification through Expert Survey 151 4.5 Verification by CMMI 157 4.5.1 Systems Engineering Capability Model 157 4.5.2 Methodology Evaluation by CMMI 164 Ⅴ. Conclusion 175 REFERENCES 179 Abstract (Korean) 187 | - |
| dc.language.iso | eng | - |
| dc.publisher | The Graduate School, Ajou University | - |
| dc.rights | 아주대학교 논문은 저작권에 의해 보호받습니다. | - |
| dc.title | An Approach to Defining the Required Capability of a Weapon System using Universal Naval Task List | - |
| dc.title.alternative | Youjae Won | - |
| dc.type | Thesis | - |
| dc.contributor.affiliation | 아주대학교 일반대학원 | - |
| dc.contributor.alternativeName | Youjae Won | - |
| dc.contributor.department | 일반대학원 시스템공학과 | - |
| dc.date.awarded | 2020. 8 | - |
| dc.description.degree | Doctoral | - |
| dc.identifier.localId | 1151626 | - |
| dc.identifier.uci | I804:41038-000000030083 | - |
| dc.identifier.url | http://dcoll.ajou.ac.kr:9080/dcollection/common/orgView/000000030083 | - |
| dc.subject.keyword | Required Capability | - |
| dc.subject.keyword | Universal Naval Task List | - |
| dc.subject.keyword | Weapon System | - |
| dc.description.alternativeAbstract | The “Needs” function is the first button used to acquire a weapon system in the defense field, this indicate the force required at the mid- and long-term levels in the construction of future military forces. Thus far, Korea has created needs through “Threat-Based Planning,” which plans requirements according to clear threats. From the mid-2000s, the Korean military has focused on strengthening capabilities-based planning by benchmarking the United States Joint Capability Integration and Development System (JCIDS) and re-establishing it as a “Joint Combat Development System.” As the Korean military promoted the establishment of a Joint Combat Development System, each military had to raise a rough capabilities-based requirement. After 2019, each military was required to conduct preconception studies prior to raising the weapons system. The related laws and regulations have been revised so that each military can prepare the operational requirements document (ORD) previously prepared by the Defense Agency Program Administration (DAPA). This requires each military to strengthen its capability of planning requirements, emphasizing the ability of each military to supplement the necessity and characteristics of the weapon system and the completion of the initial requirement at the stage of raising needs. In this manner, while switching to capability-oriented requirements planning and emphasizing the user's initial activities in requirements planning, each military must clearly present the capabilities required for the weapon system to be used during planning. However, each military still raises the need to focus on the performance of a single weapon system through threat-based planning. This is because there is no method for deriving the required capability at each group level, so there is no actual capability demand. Therefore, in this thesis, the method for deriving the requirements of the weapons system centered on the capabilities of each military was studied at the stage of the capability requirement of the joint combat development system. The proposed methodology was defined as a series of processes that leads to concepts, required capabilities, attributes, and metrics, and was established as follows. First, this study focused on 'how to fight' the concept of each military's operation, which should be reflected in the concept of joint action. Upon analyzing the future environment and the mission analysis from the upper level strategic guidelines, the concept of how to perform an operation or function was materialized as a scenario. In addition, the set of activities or functions specified in the operation concept was expressed as the capability the system should have, and the derived capabilities were divided into seven classification systems in the joint capability area of the Korean military. Then, for each capability, the attribute, which is an adjective expression indicating what capability is, was selected, and the measurement criteria were set to quantitatively measure the attribute. To set metrics for each attribute, UNTL (Universal Naval Task List), which is a common task list that presents what needs to be performed by the Navy as an act of conduct during exhibitions and peacetime, was used. The verification of the methodology for defining the required capability proposed in this study was performed considering the requirements derivation, requirements planning, and systems engineering activities. First, based on the operation concept description (OCD) and operation request (ORD), the previous threat-based and capabilities-based planning requirement derivation methods proposed in this study were applied to the coastal combat ship system, respectively. The operating requirements were derived and compared. Next, in terms of planning the requirements, the methods of deriving requirements based on threats and capabilities were evaluated by an accomplished questionnaire using AHP. Third, the previous and the proposed methods were compared and evaluated by applying the Capability Maturity Model Integration (CMMI) considering the organization performing the requirements planning for the weapon system. As a result, the effectiveness of the proposed capabilities-based method for deriving the required capability was confirmed. The significance of this study supports the requirements planning capability of each military by analyzing the method of deriving the capability-centered requirement considering the activities to be performed by the military. Using the results of this study, it is possible to plan requirements focused on the needs of the users. In addition, by using the standardized language from the user's perspective, the capability to be clarified is extended to the system development stage in the future, and is expected to assist the developer in specifying system requirements. | - |
- Appears in Collections:
- Graduate School of Ajou University > Department of System Engineering > 4. Theses(Ph.D)
- Files in This Item:
- There are no files associated with this item.
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.
-
- License
- STATISTICS
- Total Visit :3,726,365
- Total Download :1,818
- Today View :4,023
