• 정보처리학회논문지D
• /
• 제15D권5호
• /
• pp.647-658
• /
• 2008

자연어로 작성된 고객의 요구사항은 개발과정에서 모델링 언어로 재작성 된다. 그러나 개발에 참여하는 다양한 계층의 사람들은 모델링 언어로 작성된 요구사항을 이해하지 못하는 경우가 많이 발생한다. 본 논문에서는 REED(REquirement EDitor)로 작성된 요구사항 모델을 자연어로 번역하여 개발에 참여하는 모든 계층의 사람들이 요구사항 모델을 이해할 수 있도록 도와주는 방안을 제시한다. 제시한 방법은 3단계로 구성되어 있다. 1단계 IORT(Input-Output Relation Tree) 생성, 2단계 RTT(Requirement Translation Tree) 생성, 3단계 자연어로 번역의 단계를 거친다.

• 한국철도학회:학술대회논문집
• /
• 한국철도학회 2006년도 추계학술대회 논문집
• /
• pp.170-173
• /
• 2006

Requirement management is an essential process that has a significant influence on the project success. Due to the evolutionary development nature of requirement, the effective management for requirement must include change process and configuration control. This paper describes how to implement effective requirement management process to the Korea Tilting Train eXpress development with the application of a model based systems engineering tool.

• 한국시뮬레이션학회:학술대회논문집
• /
• 한국시뮬레이션학회 2005년도 춘계학술대회 논문집
• /
• pp.100-105
• /
• 2005

Development of complex discrete event simulators requires cooperation between domain experts and modeling experts who involve the development. With the cooperation the domain experts derive user requirement and modeling experts transform the requirement to a simulation model. This paper proposes a method for consistency verification of simulation model in DEVS formalism against the user requirement in UML diagrams. It also presents an automated tool, called VeriDEVS, which implements the proposed method. Inputs of VeriDEVS are three UML diagrams, namely use case, class and sequence diagrams, and DEVS Graph, all in Visio; outputs of a verification result is represented in PowerPoint files.

• 정보처리학회논문지D
• /
• 제15D권4호
• /
• pp.505-512
• /
• 2008

임베디드 시스템에 대한 RBT(Requirement-Based Testing)를 수행하기 위하여 정확한 요구사항 명세서가 존재해야 한다. 그러나 고객이 자연어로 작성하는 요구사항은 모호성, 부정확성, 불일치성을 가지고 있다. 이를 해결하기 위해서 UML, Simulink등의 모델링 언어를 이용하여 요구사항을 다시 모델링 하지만, 이 과정에서 요구사항을 use-case단위로 조합하고 재해석하는 단점이 생겨나게 되었다. 본 논문에서는 임베디드 시스템에 대한 고객의 요구사항을 use-case단위의 조합이나 재해석이 필요 없이 곧바로 모델로 표현할 수 있는 그래픽 언어를 이용한 1:1 요구사항 모델링 기법을 소개한다. 제안한 방법은 1) 임베디드 시스템의 요구사항을 자연어가 아닌 의미가 분명한 그래픽 언어를 이용하여 표현하고, 2) 하나의 요구사항을 하나의 그래픽 모델로 표현한다. 또한 제안한 방법은 시스템의 입출력을 기반으로 "what-to-do"만을 기술하기 때문에 상위레벨의 요구사항이나 하위레벨의 요구사항 모두에 적용할 수 있는 기법이다. 이 기법이 적용된 REED라는 도구를 통하여 실제 프로젝트에 적용한 예를 살펴본다.

• International Journal of Computer Science & Network Security
• /
• 제23권8호
• /
• pp.199-203
• /
• 2023

Influential trend that widely reflected the software engineering industry is service oriented architecture. Vendors are migrating towards cloud environment to benefit their organization. Companies usually offer products and services with a goal to solve problems at customer end. Because customers are more interested in solution of their problem rather than focusing on products or services. In software industry the approach in which customers' problems are solved by providing services is known as software as a service. However, software development life cycle encounters enormous changes when migrating software from product model to service model. Enough research has been done on the overall development process but a limited work has been done on the factors that influence requirements elicitation process. This paper focuses on those changes that influence requirement elicitation process and proposes a systematic methodology for transformation of software from product to service model in a successful manner. The paper then elaborates the benefits that inherently come along with elicitation process in cloud environment. The paper also describes the problems during transformation. The paper concludes that requirement engineering process turn out to be more profitable after transformation of traditional software from product to service model.

• 제어로봇시스템학회논문지
• /
• 제11권2호
• /
• pp.152-159
• /
• 2005

This paper describes the application of a model-based system design method critical to complex intelligent systems, PSARE, to a welding robot development to define its top level architecture. The PSARE model consists of requirement model which describes the core processes(function) of the system, enhanced requirement model which adds technology specific processes to requirement model and allocates them to architecture model, and architecture model which describes the structure and interfaces and flows of the modules of the system. This paper focuses on the detailed procedure and method rather than the detailed domain model of the welding robot. In this study, only the top level architecture of a welding robot was defined using the PSARE method. However, the method can be repeatedly applied to the lower level architecture of the robot until the process which the robot should perform can be clearly defined. The enhanced data flow diagram in this model separates technology independent processes and technology specific processes. This approach will provide a useful base not only for improvement of a class of welding robots but also for development of increasingly complex intelligent real-time systems.

• 한국군사과학기술학회지
• /
• 제13권1호
• /
• pp.67-76
• /
• 2010

RAM(Reliability, Availability, Maintainability) characteristics of weapon system is a part of Required Operational Capability, must be reasonable and achievable. In this study, we studied the criteria, important factors to establish RAM requirement and reviewed the current process. Then we propose the new process and method to establish the reasonable and achievable RAM requirement by BCS(Baseline Comparison System) model.

• Asian-Australasian Journal of Animal Sciences
• /
• 제10권3호
• /
• pp.277-283
• /
• 1997

Purified diets containing five levels of methionine with 0.4% cystine were fed to growing chicks (8 days old male Arbor Acre strain) to evaluate methionine requirements for growth and maintenance. A model was developed to separate methionine requirement for maintenance from requirement for growth. From this model the daily methionine requirement for growth was 4.22 mg/g gain, and the daily methionine requirement for maintenance was 0.034 times metabolic body size ($W^{0.75}$). Based on nitrogen gain response, the methionine requirement for growth was 0.162 mg/mg N gain, and the daily maintenance requirement was 0.037 times metabolic body size. The plateau of plasma methionine concentration reached at 117.16 mg intake pre day. The total methionine requirement determined based on weight gain response was 138.29 mg/day or 0.33% of the diet and the one determined based on nitrogen gain response was 141.7 mg/day of 0.34% of the diet, respectively. As a percentage of protein, methionine was calculated to be 2.6%; the reported methionine content of carcass CP was 1.76%.

• 한국군사과학기술학회지
• /
• 제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).

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제31권7호
• /
• pp.869-882
• /
• 2004

본 논문에서는 정형방법론의 일관성 검사방법을 유스케이스 모델링에 적용함으로써 논리적으로 일관되고 구조화된 요구사항 모델을 생성할 수 있는 방안을 제안하였다. 제안된 방안을 통해 서로 중복되거나 충돌할 수 있는 다중 사용자관점의 부분적인 요구사항들을 구조화된 요구사항 모델로 통합할 수 있다. 요구사항 모델의 구조는 문맥목표와 관심영역의 중복구조를 통하여 분석되며, 요구사항의 모델의 일관성은 요구사항 통합의 수단으로 요구사항 명세의 중복관계에 기반한 일관성 검사방법을 사용함으로써 획득된다. 제시된 방법을 사례분석에 적용한 결과 제안된 방안이 요구사항의 중복관계 및 불일치를 도출할 수 있을 뿐만 아니라 다중 사용자관점의 부분적인 요구사항들을 일관성을 갖는 통합된 요구사항 모델로 전환함으로써 소프트웨어의 행위와 기능을 명확하게 규명할 수 있음을 보여 주었다. 제안된 방안을 통하여 개발 초기단계의 유스케이스 모델링에 있어서 요구사항 불일치 도출능력을 강화할 수 있으며, 고객만족을 위해 사용자와 개발자간의 의사소통을 촉진할 수 있다.