Browse > Article

System Requirement Definition Process from Operational Concept and The Application Case-Study of ATACMS  

이중윤 (국방과학연구소)
박영원 (아주대학교 시스템공학과)
Publication Information
Journal of the Korea Institute of Military Science and Technology / v.6, no.3, 2003 , pp. 22-35 More about this Journal
Abstract
This paper describes system technical requirement development process from operational concept using computer-aided Systems Engineering tool(CASysE Tool-CORE). The army tactical missile system-ATACMS's technical requirements are developed by the process as a case-study The scope of the work is context analysis and requirement definition process. The proposed process is as follows. At first, an integrated architecture could be developed from the operational concept. From the integrated architecture a capability needs, which includes KPPs, are generated. And the capability needs expanded according to the Mil-Std-961D format. Lastly, a system technical requirement could be generated automatically from the CASysE Tool-CORE.
Keywords
System Requirement; Requirement Definition Process; Operational Concept; Missile System; Systems Engineering Tool; CORE; ATACMS : Army Tactical Missile System;
Citations & Related Records
연도 인용수 순위
  • Reference
1 Department of Defense(DoD), MIL-STD-498, Operational Concept Description, DI-IPSC-81430, DoD, 1994.12, pp.3-7
2 AIAA, Guide for the Preparation of Operational Concept Documents, ANSI/AIAA G-043-1992, 1993.1
3 FM 6-20-10, Tactics, Techniques, Aand Procedures For Corps Artillery, Division Artillery, And Field Artillery Brigade Operations, www.adtdl.army.mil.. 1993.1
4 Department of Defense(DoD), DoDD-5000.1, The Defense Acquisition System, DoD, 2003.5, p.5
5 FM 6-20, Fire Support In The Airland Battle, www.adtdl.army.mil., 1988.5
6 Department of Defense(DoD), DoDI-5000.2, Operation of the Defense Acquisition System, DoD, 2003.5, pp.2 -6
7 FM 6-60, Tactics, Techniques, And Procedures For Multiple Launch Rocket System(MLRS) Operations, www.adtdl.army.mil., 1996.4
8 IEEE, Guide for Information Technology System Definition-Concept of Operations Document, IEEE Std 1362-1998, 1998.3
9 국방부훈령 제733호, 국방획득관리 규정, 국방부, 2002.2, p.9, pp.18-26
10 Center for Program Management(CPM) of Defense Acquisition University(DAU), New Deputy Secretary of Defense Guidance, http://www-tradoc.army.mil/dcscd/library.htm, 2002.11
11 Andrew P Gabb, 'Operational Concepts Some Variations', Systems Engineering, Test & Evaluation Conference, Sydney, Australia, 2002.10
12 FM 90-36, The Joint Targeting Process And Procedures For Targeting Time-Critical Targets, www.adtdl.army.mil., 1997.7
13 국방부훈령 제700호, 국방기획관리 기본규정, 국방부, 2003.5, pp.8-38, p.107
14 Chairman of the Joint Chiefs of Staff Instruction(CJCSI), CJCSI 3170.01C, Joint Capabilities Integration and Development System, DoD, 2003.6, pp.1-3, p.20
15 R. E. Fairley and R. H. Thayer, 'The Concept of Operations: The Bridge from Operational Requirements to Technical Specifications,' Software Engineering, M. Dorfman and R. H. Thayer(eds.), IEEE Compo Soc. Press, Los Alamitos, CA, 1997
16 U.S. Army Training and Doctrine Command, TRADOC Pamphlet 71-9, Requirements Determination, Department of the Army Headquarters, U.S. Army Training and Doctrine Command, Fort Monroe, USA, 5 November 1999, pp.214-218, pp.219-246
17 Buede, D. M., The Engineering Design of Systems. John Wiley & Sons, INC., New York, 2000, pp.125-135
18 MiI-Std-961D, Standard Practice for Defense Specifications, Department of Defense(DoD), 1995.3, pp.122-125
19 Electronic Industries Alliance(EIA), Process for Engineering a System(EIA-632), EIA Press, Arlington, 1999, pp.34-36, p.97