Journal of the Korea Institute of Military Science and Technology (한국군사과학기술학회지)

The Korea Institute of Military Science and Technology (한국군사과학기술학회)
권호 표지

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

운용 개념에서 시스템 요구사항을 정의하는 프로세스의 개발 및 특정 유도무기(ATACMS) 적용 사례

  • Published : 2003.09.01
Download PDF
⟨ Previous Next ⟩

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

References

  1. 국방부훈령 제700호, 국방기획관리 기본규정, 국방부, 2003.5, pp.8-38, p.107
  2. 국방부훈령 제733호, 국방획득관리 규정, 국방부, 2002.2, p.9, pp.18-26
  3. 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
  4. Department of Defense(DoD), DoDD-5000.1, The Defense Acquisition System, DoD, 2003.5, p.5
  5. Department of Defense(DoD), DoDI-5000.2, Operation of the Defense Acquisition System, DoD, 2003.5, pp.2 -6
  6. 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
  7. Department of Defense(DoD), MIL-STD-498, Operational Concept Description, DI-IPSC-81430, DoD, 1994.12, pp.3-7
  8. IEEE, Guide for Information Technology System Definition-Concept of Operations Document, IEEE Std 1362-1998, 1998.3
  9. AIAA, Guide for the Preparation of Operational Concept Documents, ANSI/AIAA G-043-1992, 1993.1
  10. 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
  11. Andrew P Gabb, 'Operational Concepts Some Variations', Systems Engineering, Test & Evaluation Conference, Sydney, Australia, 2002.10
  12. 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
  13. Buede, D. M., The Engineering Design of Systems. John Wiley & Sons, INC., New York, 2000, pp.125-135
  14. MiI-Std-961D, Standard Practice for Defense Specifications, Department of Defense(DoD), 1995.3, pp.122-125
  15. Electronic Industries Alliance(EIA), Process for Engineering a System(EIA-632), EIA Press, Arlington, 1999, pp.34-36, p.97
  16. FM 6-20, Fire Support In The Airland Battle, www.adtdl.army.mil., 1988.5
  17. FM 6-20-10, Tactics, Techniques, Aand Procedures For Corps Artillery, Division Artillery, And Field Artillery Brigade Operations, www.adtdl.army.mil.. 1993.1
  18. FM 6-60, Tactics, Techniques, And Procedures For Multiple Launch Rocket System(MLRS) Operations, www.adtdl.army.mil., 1996.4
  19. FM 90-36, The Joint Targeting Process And Procedures For Targeting Time-Critical Targets, www.adtdl.army.mil., 1997.7