• 제목/요약/키워드: OCD(Operational Concept Document)

검색결과 3건 처리시간 0.014초

"3D 모델기반 디지털 협업 시스템" 운용개념 개발 방안 수립 사례 (Planning of Development of the Operational Concept Document of the "3D Model Based Digital Collaboration System" : Case Study)

  • 김진일;차재민;이태경;김준영
    • 시스템엔지니어링학술지
    • /
    • 제13권2호
    • /
    • pp.42-48
    • /
    • 2017
  • OCD (Operational Concept Document) is very important in system development. To develop OCD we should answer questions about, what template to use, what is the overall process to develop OCD, what kinds of diagrams we should use and how can we validate the OCD. To answer about the template we compared tow industrial guide on operational concept development and tailored it. For development process, we proposed a comprehensive process which satisfies the requirements of the project context. For use of proper diagram, we analyzed many kinds of diagrams used in representing behavior of system and choose some diagrams which best fit for our purpose. Finally we established validation criteria for operational scenario and requirement texts in operational concept documents.

운용개념 개발 가이드와 프로세스 분석 및 작성 사례 연구 (Analysis of Operational Concept Development Guide, Process and A Case Study)

  • 박중용
    • 시스템엔지니어링학술지
    • /
    • 제9권1호
    • /
    • pp.13-23
    • /
    • 2013
  • Operational Concept Descriptions or Document(OCD) shall be developed to understand stakeholder's desire for to-be-delivered system. But there is little study on methodology of OCD generation and many developers do not understand importance of OCD in Korea. According to Nicole Roberts' industry(18 U.S. companies and organizations) survey, only 30% of system development projects had OCD, too. Researchers and developers have opposing views regarding the generation of an OCD. Many researchers believe that the development and use of operational concepts at the start of large projects is essential. Alternatively, developers may view the OCD as a burden to the development process rather than an enabler due to the extensive documentation requirement. In this paper a couple of OCD guidelines were investigated to clarify how to build a CONOPS effectively and what to include. Finally, OCD for rotorcraft based Personal Air Vehicle System(PAVS) was developed as a case study. In the future, a template for generating OCD appropriate to Korean environment could be proposed.

MND-AF를 활용한 운용개념기술서(OCD) 및 운용요구서(ORD)에 대한 보완 연구 (The Complementary Study for Operational Concept Document(OCD) and Operational Requirements Document(ORD) using MND-AF)

  • 차승훈;장재덕;이혜진;최상욱;유제상
    • 시스템엔지니어링학술지
    • /
    • 제16권2호
    • /
    • pp.118-130
    • /
    • 2020
  • Modern weapon systems are composed of complex systems(System of Systems) and require a complex and advanced operational concept that performs missions through interoperability with various weapon systems. In order to derive the operational concept of the weapon system that the military wants to acquire (i.e., single mission, component operation, Joint and Alliance operations), it is necessary to identify the system related to the weapon system, environmental factors and restrictions of the weapon system to be developed. Through the derivation of the operational concept, the weapon system acquisition agency can reasonably and accurately extract various and complex requirements. In this paper, we propose a complementary method of using MND-AF to OCD and ORD required in weapon system acquisition process. MND-AF can increase the understanding and consensus of business stakeholders (users, acquirers, developers, etc.) by showing the results of weapon system analysis from various perspectives. We compare the items in the standard form of OCD and ORD with the MND-AF outputs.