• 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.

• 제어로봇시스템학회:학술대회논문집
• /
• 2000.10a
• /
• pp.419-419
• /
• 2000

This paper describes a requirement analysis for automotive engine design using a computer aided systems engineering tool RDD-100. Because the engine is a complex system with many subsystems, there are many needs of stakeholder throughout the life-cycle of the engine. The originating requirements have been derived from the needs and decomposed into leaf-node requirements with the tool. Many requirement errors have been detected during the decomposition process and resolved by modifying the requirements. Inconsistency problems have been also resolved with the tool, Analysis of engine requirements using RDD-100 brings clarity to engine design early in the development process.

• 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.

• Proceedings of the KSR Conference
• /
• 2001.10a
• /
• pp.35.1-40
• /
• 2001

This study is on the behavior analysis which can define and verify a system requirement through a behavior diagram for High speed rail system. The model considered in this study is limited to the preconditioning control of the control system specification for HSRS. To build an executable model, requirements should be decomposed first into leaf node requirements. The behavior model is composed of input, output, and functions which are linked with leaf node requirements. It is important that a single requirement must specify a single Auction. Using the developed executable model and the traceability between requirements and functions, this study found out a lot of static and dynamic inconsistency, missed and derived requirements. This is to develop and executable behavior model to do functional analysis and be able to verify the integrity of a specification.

• Information Systems Review
• /
• v.10 no.1
• /
• pp.91-113
• /
• 2008

Recently, as most functional business activities in an enterprise are supported by computerized information systems, data duplication and inconsistency among functional information systems become serious problems. It brings people to have many interests on data quality management. This paper presents a case study in which a company had improved their data quality by enhancing their data quality management processes. Though the case study, we describe main issues and risk factors in the process of data quality improvement projects as well as solutions to resolve the issues, which can be referred by other companies who pursue data quality improvement. Also, the improvement effects are evaluated by multidimensional perspectives which include quantitative and qualitative measures on data quality, productivity, customer satisfaction, organization, and culture.

• Journal of the Korea Society for Simulation
• /
• v.18 no.3
• /
• pp.113-122
• /
• 2009

Software is getting more complex due to a variety of requirements that include desired functions and properties. Therefore, verifying and testing the software are complicated problems. Moreover, if the software is already implemented, inserting and deleting tracing/logging code into the source code may cause several problems, such as the code tangling and the code scattering problems. This paper proposes the Aspect DEVS Verification Framework which supports the verification and testing process. The Aspect DEVS Verification Framework utilizes Aspect Oriented Programming features to handle the code tangling and the code scattering problems. By applying aspect oriented features, a user can find and fix the inconsistency between requirement and implementation of a software without suffering the problems. The first step of the verification process is the building aspect code to make a software act as a generator. The second step is developing a requirement specification using DEVS diagrams and implementing it using the DEVSIM++. The final step is comparing the event traces from the software with the possible execution sequences from DEVS model.

• Journal of Environmental Impact Assessment
• /
• v.19 no.2
• /
• pp.205-213
• /
• 2010

The purpose of this research is to analysis the application of the ISG(Index of Streetscape Greenness) in EIA through case study of Seoul. ISG is a new index which directly expresses human's perceptions of plants in a street and is defined as the area ratio of which leaves of plants occupy an eye-level view of a person standing on the center line of a street. In this research the 42 cases of 3 step reports such as plans, drafts, and final reports which had been passed through the EIA procedure of Seoul were analyzed. The results are as follows: In the drafts frequent mistakes or errors such as unsuitable picture composition, unsuitable sample points, inconsistency of the simulation result with the planting plan, and insufficient numbers of analysis were found, but almost of them were corrected in the final reports. In the most of final reports, the 30% of minimum requirement was satisfied. At all cases the changes of the ISG values were clearly positive. Finally the average current ISG was 19.6%, meanwhile the average proposed ISG was 35.4%. It was verified that the ISG is very practical index to promote green streetscape, but in order to guarantee an achievement a thorough investigation of reports are needed.

• East Asian Journal of Business Economics (EAJBE)
• /
• v.9 no.3
• /
• pp.15-28
• /
• 2021

Purpose -In the credit transaction, the issuing bank must examine the documents to pay the credit amount. In order to smoothly execute the credit transaction, document review is a key element, so the 5th revised credit unification rule specifically defines the document review procedure. Research design, data, and methodology - The document review procedure specified in the UCP Rules can be largely divided into the document review period and the rejection procedure for inconsistent documents. First of all, confusion was caused by the ambiguous regulation.. Result - With regard to the document review period, in the actual credit transaction, the issuing bank often negotiates with the issuing client about the waiver of the document inconsistency. Next, in the process of notifying the rejection of inconsistent documents, the issuing bank shall send the rejection notice. Conclusion - This study suggests that the requirement to list all inconsistencies makes it impossible for the issuing bank to further notify the refusal, thereby limiting the right to defend against inconsistencies not listed in the first refusal notice and consequently having the effect of matching them. In addition, the issuing bank's rejection notice is closely related to the beneficiary's exercise of the right to replenish documents.

• Spatial Information Research
• /
• v.6 no.2
• /
• pp.201-216
• /
• 1998

The :Ministry of Transportation and Construction has a plan to finish up the construction of digital topographic map which is based. on airphoto intepretation method by the end of 1998 as a part of NQS (National Geogaphic Information System) Project. The digital topographic map, especially 1:1,000 scale, is used as a basemap of many local government's GIS projects. The digital topographic map, however, does not include property information such as cadastral and urbanplan data that are essential for the GIS database of many local governments. This study aims to develop a set of technical guidelines for the construction of digital cadastral map, which can be used together with the 1:1,000 scale digital topographic map, through 1) analysis of the inconsistency between topographic map and cadastral map, 2) comparison of technical methods for the integration of GIS data that have different accuracy, and 3) requirement analysis of the departments related to urban planning of Seoul Metropolitan Govemment. For this research, edited digital cadastral map has been experimentally produced in pilot study area, a part of Hwanghak-dong, Shindang-dong, and Soongin-dong in Seoul.

• Korean Journal of Construction Engineering and Management
• /
• v.21 no.4
• /
• pp.82-89
• /
• 2020

Article 64 of the Enforcement Decree of the National Contract Act The requirement of the pre-amendment statute related to the adjustment of the contract price was 5% or more of the price fluctuation rate from the date of the contract. However, the meeting requirement was changed from 5% or more to 3% or more from the date of signing of the Presidential Decree No. 19035 to 2005. 9. 8. The method of adjusting the contract amount was also changed to determine the contractor's desired adjustment method at the time of contract. Alleviating these requirements and revising the empowerment of contract partners is intended to prevent difficulties in achieving smooth objectives by applying to public construction contractors without unfairly benefiting or unfavorable to contract partners. Even if the standards are relaxed and the rights are secured as described above, if the existing provisions for the adjustment of price fluctuation are applied, unlike the original purpose of the government system, the Korea Bank's price economic statistics classification method and the contract construction classification criteria applied in public construction work Due to the inconsistency, it can be seen that the amount of adjustment for price fluctuation by construction type is excessive and underestimated. Therefore, the purpose of this study is to analyze problems through cases and to make appropriate construction cost adjustment through improvement measures.