• Proceedings of the CALSEC Conference
• /
• 2001.08a
• /
• pp.671-679
• /
• 2001

사례연구를 통하여 UML Component Design Process의 일관성 및 정확성을 검증한다. Business Concept Model과 Use Case Model을 이용하여 Component Specification Process의 산출물인 Interface, Component Specification 및 Component Architecture 작성 UML Notation을 확장해서 Component 명세에 적용하는 것이 올바른 것인지 확인한다. <>,<>,<>,<>,<>, <>:로 Component Specification이 충분한지를 확인 OCL을 이용하여 Component Specification 중 Component Specification, Interface Specification, Operation Specification, Constraint, Pre/Post Condition의 정의에 유용한지 확인(중략)

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2003.05a
• /
• pp.749-752
• /
• 2003

The HLA is defined by three components: (1) Rules, (2) the HLA Interface Specification, and (3) the Object Model Template(OMT). The RTI(Run-Time Infrastructure) software implements the interface specification. It provides services in a manner that is comparable to the way a distributed operating system provides services to applications. A way to test whether is suitable for a standard, and all service was implemented is tested through two phases of processes to verify the RTI which proposed in DMSO. In this paper, we discuss Level One Test Procedures and a method. Confirms whether RTI was implemented in Interface Specification according to Level One Test Procedures appropriately through a test. Develops Test Suite for every each step to test whether a correct command and the expected results are occur.

• Proceedings of the CALSEC Conference
• /
• 2001.02a
• /
• pp.427-444
• /
• 2001

ㆍ ebXML Message Services Requirements Specification - Working Draft 26-May-2000, v0.96 · ebXML Message Services Specification - Working Draft 13-Sep-2000, v0.21 ㆍ ebXML Collaboration Protocol Profile and Agreement Specification - Working Draft 24-Jan-2001, v0.29 · ebXML Technical Architecture Security Specification - Working Draft 5-Feb-2001, vl.02(Under development) ㆍ ebXML Message Service Interface Specification - Under development.(omitted)

• Journal of the Korea Society for Simulation
• /
• v.12 no.4
• /
• pp.41-50
• /
• 2003

HLA (High Level Architecture) is the object, time, and interface standard that proposed for distribution simulation in the US Department of Defense. The HLA is defined by three components: Rules, the HLA Interface Specification, and the Object Model Template (OMT). The RTI (Run-Time Infrastructure) software implements the interface specification. It provides services to simulation applications. To test whether a RTI software is suitable for the standard and all service was implemented is performed through two phases of processes proposed by DMSO. In this paper, we implement Level One Test Procedures of DMSO and apply to NetCust's RTI software. The experimental results are discussed.

• IE interfaces
• /
• v.12 no.2
• /
• pp.319-328
• /
• 1999

Today, offshore design field is concerned with system integration such as CIM(Computer Integrated Manufacturing), PDMS(Product Data Management System) and EDMS(Engineering Data Management System) in order to cope with the change of engineering specification as owner's requirements during construction stage of the project. This paper deals with the case study that describes about the efficient interface between material control system and 3D CAD system to support the design process in offshore industry using design rules involved the designer's knowledge. In this paper, we constructed an information system, called knowledge-based CAD interface systems, which is composed material code management system and 3D specification generator which automatically creates 3D catalogue anti specification by linking the material code, called short code, and the specification components of the 3D CAD system. As a result of the construction, it is possible to maintain consistency of the design process, and through reduction of the design processing time and improvement of the design process, competitiveness is improved.

• Journal of The Korean Association of Information Education
• /
• v.8 no.4
• /
• pp.555-562
• /
• 2004

There are informal, semi-formal and formal methods in software specification. Among them, formal method which is based on mathematical theory had been used to remove ambiguity, incompleteness and contradiction efficiently. In this paper, we propose implementation steps from Z specification to EJB source code, Also, as a case study we show steps consisted of specifying stack data structure and implementing it in EJB. In conclusion, Z specification proved to be capable of implementing EJB interface, exception class, method, through refinement and definition of schema, interface, post-condition, pre-condition.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.3
• /
• pp.808-817
• /
• 2000

Component specification languages in consideration of reuse are essential factor in classification, verification and retrieval of components. A number of legacy specification languages have already been used, however, they are complex and include many necessary elements in the specification for implementation. In this paper, we present XML-based component specification and software architecture specification language to solve these problems of legacy specification languages. The presented specification languages consist of component specification, which is composed of signature specification, interface specification and message specification, and software architecture specification providing graphical notations and textural notations. Component specification supports component retrieval with behavioral match and black-box reuse of component. In addition to this, it improves the efficiency of retrieval and document management with XML-based component specification. Software architecture specification supports the structural reuse of architecture, which is white-box reuse, through mesage-based architecture specification.

• Journal of KIISE
• /
• v.44 no.1
• /
• pp.27-35
• /
• 2017

Many studies have addressed 'Adaptive User Interface (AUI)', wherein the user interface changes in accordance with the situation and the environment of each user at runtime. Nevertheless, previous papers for AUI barely reflected the viewpoints from requirements engineering field, since most of them focused on proposing the architecture and design. In this study, we outline AUI with the perspective of requirements engineering and propose the requirements elicitation and specification method based on concepts which have been researched in the area of self-adaptive system. Step by step, we first redefine and reinterpret the well-known concepts of self-adaptive software, after which the AUI requirements are elicited and specified. Finally, we illustrate a case study, which demonstrates the effectiveness of our method.

• 전기의세계
• /
• v.26 no.6
• /
• pp.41-47
• /
• 1977

The paper deals with the fundamental specification for the physical implementation of interface circuit, which will play an important role in information and signal trammission between computer and controlled system, and also we have proved that the digital contoller will be able to improve the data handling of interface circuit.

• Journal of Korea Spatial Information System Society
• /
• v.9 no.2
• /
• pp.1-11
• /
• 2007

Recently, with the development of collecting methods of spatial data, the spatial data is produced, circulated, and used in various fields of industry and research. To manage the mass spatial data efficiently, the researches on extension of the existing commercial DBMS, such as ESRI's ArcSDE or Oracle's Oracle Spatial, is making progress actively. However, the usage of the extension of the commercial DBMS Incurs an additional expense and causes an interoperability problem due to differences in spatial data types and spatial operators. Therefore, in this paper, we developed an OpenGIS Spatial Interface for Oracle, which supports a standard interface by fellowing the "Simple Features Specification for SQL" proposed by OGC(Open Geospatial Consortium). Since the OpenGIS Spatial Interface provides all spatial data types and spatial operators proposed in "Simple Features Specification for SQL", users can manage mass spatial data of Oracle efficiently by using the standard interface without additional expense. In addition, we proved that the OpenGIS Spatial Interface is superior to the Oracle Spatial in the response time through the performance evaluation.