• The KIPS Transactions:PartD
• /
• v.15D no.5
• /
• pp.647-658
• /
• 2008

Customers' requirements written in a natural language are rewritten to modeling language in development phases. In many cases, those who participate in development cannot understand requirements written in modeling language. This paper proposes the translation technique from the requirement model which is written by REED(REquirement EDitor) tool into a natural language in order to help for the customer understanding requirement model. This technique consists of three phases: $1^{st}$ phase is generating the IORT(Input-Output Relation Tree), $2^{nd}$ phase is generating the RTT(Requirement Translation Tree), $3^{rd}$ phase is translating into a natural language.

• Proceedings of the KSR Conference
• /
• 2006.11b
• /
• 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.

• Proceedings of the Korea Society for Simulation Conference
• /
• 2005.05a
• /
• 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.

• The KIPS Transactions:PartD
• /
• v.15D no.4
• /
• pp.505-512
• /
• 2008

In order to do requirement-based testing of embedded system, we must have correct requirement specifications. But, natural language requirements of a client have ambiguity, inaccuracy, and inconsistency. To solve these problems, natural language requirements are modeled with modeling language such as UML and Simulink. During a modeling phase, the requirements are rearranged and retranslated in use-case. These activities are disadvantages of modeling. In this paper, we propose the technique, which is how to model a embedded system requirement into a model without rearranging and retranslating. This technique 1) represent a embedded system requirement with graphical language, and 2) model a requirement into a model. Because this technique only describes "what-to-do" of the requirement, this technique is useful to not only the low-level requirements but also the high-level requirements. We show some example systems modeled by REED, which has adopted this technique.

• International Journal of Computer Science & Network Security
• /
• v.23 no.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.

• Journal of Institute of Control, Robotics and Systems
• /
• v.11 no.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.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.13 no.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
• /
• v.10 no.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%.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.9 no.1 s.24
• /
• 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).

• Journal of KIISE:Software and Applications
• /
• v.31 no.7
• /
• pp.869-882
• /
• 2004

This paper proposes an effective method to create logically consistent and structured requirement model by applying consistency control approach of the formal method to the use-case modeling. This method integrates the multi-perspective scattered requirement segments that may overlap and conflict each other into a structured requirement model. The model structure can be analyzed based on context goal and concerned area overlap analysis. The model consistency can be achieved by using specification overlap-based consistency checking method as an integration vehicle. An experimental application to case study shows that the Proposed method can successfully identify requirement overlaps and inconsistency. It can also transfer multi-viewpoint requirement segments into a consistently integrated use-case model to clarify software behaviors and functionality This method helps users to enhance capability to identify specification inconsistency in the use-case modeling at the early stage of software engineering development. The proposed approach can also facilitate communication between users and developers to ensure customer satisfaction.