• 제목/요약/키워드: Requirement Definition

검색결과 114건 처리시간 0.022초

요건공학을 통한 TRIZ 문제정의 (TRIZ Problem Definition through Requirements Engineering)

  • 정진하;박영원
    • 한국생산제조학회지
    • /
    • 제19권4호
    • /
    • pp.440-448
    • /
    • 2010
  • Recently, there are many corporations, schools and institutes that apply TRIZ to solve technical problems. However, in reality, only a few cases of brainstorming applications exist in utilizing forty principles of TRIZ due to the difficulty at TRIZ problem definition. In order to facilitate TRIZ applications, this study proposes the utilization of requirement definition and description tool of systems engineering in TRIZ problem definition. No requirement definition exists in general problem types that TRIZ approach is used in implementing system solution. At most of problem situations, TRIZ users reversely infer that certain problem belongs to which requirement definition it is and recommends TRIZ tools to be used for the exact problem definition. This study also proposes TRIZ problem definition method by applying the results of requirement definition process. The application of TRIZ is demonstrated to the general situation with no problem definition where the proposed method enables the proper use of TRIZ.

수출용 KT-1 요구사항 아키텍처 모델 구축 (System Requirement Architecture Modeling of KT-1 Export Version)

  • 강민성;이진균;김진석;손환익;강영호;이중윤;최민신;이영선
    • 한국군사과학기술학회지
    • /
    • 제9권1호
    • /
    • pp.135-143
    • /
    • 2006
  • This paper describes a requirement architecture modeling for the front end of KT-1 export version requirement definition processes to construct SDS(system development specification). The requirement definition process is a highly conceptual process that is difficult to carry out. This paper focuses on how to perform the KT-1 export version requirements definition process including the integration of process, methods and tools for the front-end activity of requirements definition process. This requirement model is structured in four segments, including requirement layering, requirement categorization, life cycle stakeholder and requirement definition process using Computer-Aided Systems Engineering tool(CORE).

운용 개념에서 시스템 요구사항을 정의하는 프로세스의 개발 및 특정 유도무기(ATACMS) 적용 사례 (System Requirement Definition Process from Operational Concept and The Application Case-Study of ATACMS)

  • 이중윤;박영원
    • 한국군사과학기술학회지
    • /
    • 제6권3호
    • /
    • pp.22-35
    • /
    • 2003
  • 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.

요구사항 분석 및 아키텍처 정의 분야의 인공지능 적용 현황 및 방향 (Application of AI Technology in Requirements Analysis and Architecture Definition - status and prospects)

  • 김진일;염충섭;신중욱
    • 시스템엔지니어링학술지
    • /
    • 제18권2호
    • /
    • pp.50-57
    • /
    • 2022
  • Along with the development of the 4th Industrial Revolution technology, artificial intelligence technology is also being used in the field of systems engineering. This study analyzed the development status of artificial intelligence technology in the areas of systems engineering core processes such as stakeholder needs and requirements definition, system requirement analysis, and system architecture definition, and presented future technology development directions. In the definition of stakeholder needs and requirements, technology development is underway to compensate for the shortcomings of the existing requirement extraction methods. In the field of system requirement analysis, technology for automatically checking errors in individual requirements and technology for analyzing categories of requirements are being developed. In the field of system architecture definition, a technology for automatically generating architectures for each system sector based on requirements is being developed. In this study, these contents were summarized and future development directions were presented.

THE FEATURE CONSIDERATION AND PLAN FOR DEFINITION SYSTEMATIZATION OF CLIENT'S REQUIREMENT

  • Su-Kyung Cho;Chang-Hyun Shin;Jea-Sauk Lee;Jae-Youl Chun
    • 국제학술발표논문집
    • /
    • The 2th International Conference on Construction Engineering and Project Management
    • /
    • pp.635-641
    • /
    • 2007
  • The construction starts its business by receiving the order from client and owner. The client presents requirements and related information so that the desired result can come out while the designer and the builder express and implement the building according to set objectives and goals of project based on information on project environment and presented requirements. Because the construction project makes decisions on such objectives at its early stage and previous stage becomes the situation for decision making of next stage as the computation to implement decisions get performed. Accordingly, this study has mentioned necessity of requirement analysis and systematization of construction project, analyzed the work of construction's early stage and resented a plan for objective of construction project requirement definition model in which requirements engineering has been applied and using it while making decisions on designing.

  • PDF

SOA를 위한 온톨로지 기반의 서비스 도출 방법론 (A Methodology for Ontology-based Service Drawing for SOA)

  • 장효선;박세권;류승완;신동천
    • 한국IT서비스학회지
    • /
    • 제10권2호
    • /
    • pp.309-327
    • /
    • 2011
  • Even though several methodologies for SOA(Service Oriented Architecture) have been proposed, in practical aspects most of them have some problems since they fail to propose specific policies in definition and identification of a service. This paper proposes a service modeling methodology. SOMO(Service Oriented Modeling using Ontology), which draws proper services in the process of defining and identifying services. SOMO defines a service ontology based on service definition and characteristics in SOA. The service drawing process consists of 3 steps : requirement analysis, service identification, and service definition. SOMO is expected to increase the degree of reuse and facilitates the definition and search of services by using service ontology. In addition, it clearly allows the definition and identification of services, satisfying the user requirements.

수리온 체계개발에서의 시스템엔지니어링 적용사례 (Application of Systems Engineering in SURION R&D Project)

  • 김진훈;이동욱
    • 시스템엔지니어링학술지
    • /
    • 제10권1호
    • /
    • pp.81-86
    • /
    • 2014
  • Systems Engineering application focused on requirement definition and management for SURION System Development Project is described in this paper. To perform the development process effectively based on systems engineering processes; Requirements Definition, Design Review, Configuration Management, Quality Assurance, Data Management, are applied in this project. In this processes, the Stakeholder's Requirements are transferred to Specifications verified with design reviews, prototyping inspections, and integration tests. All engineering data, especially verification plan & results are recorded, and traced to each requirements of system specification in Surion database. Therefore, it could be assured that all requirements of specification are evaluated and verified successfully in Surion Project.

엔지니어링 데이터베이스를 위한 제품데이터의 모델링 (Product Data Model ing for Engineer ing Database)

  • 김철한;김진홍
    • 한국전자거래학회지
    • /
    • 제1권2호
    • /
    • pp.93-116
    • /
    • 1996
  • Nowadays, there are many efforts to integrate CAD/CAM and other systems. The key of integration is engineering database implementation through the product data definition. In this paper, we suggest the product data definition and their properties for electronic consumer product throughout the requirement analysis for engineering database. Electronic consumer products include electric/electronic parts. as well as mechanical part which mainly compose of machinery. The paper is composed of three parts: the first is analysis about engineering data base. the second is understanding of product data structure and properties. and the last is modeling of product data including static and dynamic characteristics.

  • PDF

QFD(Quality Function Deployment)와 시스템 요구분석 기법을 이용한 지능형 병원 시스템 개념 정립 (Intelligent Hospital Concept Definition by Implementing Quality Function Deployment And System Requirement Analysis)

  • 이준호;김대홍;진경훈;함재복;이재우
    • 시스템엔지니어링학술지
    • /
    • 제2권1호
    • /
    • pp.24-30
    • /
    • 2006
  • In this study, the design concepts for Intelligent Hospital are derived using the Quality Function Deployment(QFD) and System Requirement Analysis Method. First, requirements for important elements of Intelligent hospital are defined. Second, similar systems are compared and user requirement are refined. Through this process, operational requirement for Intelligent Hospital are defined by combining user requirements and similar systems. To analyze operational requirement, the QFD of the system engineering approach are implemented. Alternative design specifications are constructed by implementing the QFD results by building the Morphological Matrix. Various concepts that satisfy the system requirement are derived. Finally the best design concept are obtained using the Pugh concept selection matrix.

  • PDF

선유도어뢰 체계운용성능분석 기법 (System Operational Performance Analysis for Wire-Guided Torpedo)

  • 김태규
    • 한국시뮬레이션학회논문지
    • /
    • 제23권2호
    • /
    • pp.7-15
    • /
    • 2014
  • 선유도어뢰 체계운용성능분석은 요구분석 및 개발을 위한 기술적 분석 자료를 제공하는 것을 목표로 하며, 결과적으로 선유도어뢰 체계공학에서 요구정의 활동을 지원한다. 본 논문에서는 문제정의, 정식화, 모델링, 시뮬레이션, 분석 결과 등 체계운용 성능분석을 위한 기술적 접근 방법과 분석 사례를 소개한다.