• Journal of the Korea Institute of Military Science and Technology
• /
• v.18 no.6
• /
• pp.771-778
• /
• 2015

In this paper, we have proposed a design method for standardization of weapon information exchange between a weapon control computer of guided missile system and a high echelon command and control system. Because the weapon control computer based on diverse combat platforms is operated with several kinds of a high echelon system, it is necessary to provide a standardized design method for weapon information exchange between mutual system. In fact, it is possible to standardize a interface design specification of weapon information message because weapon information message is closely related to standard tactical data link message. It is essential that the interface design specification of weapon information is submitted to that of tactical data link information. It seems that this interface design specification is very useful in development process of the future weapon system.

• IEIE Transactions on Smart Processing and Computing
• /
• v.5 no.1
• /
• pp.55-62
• /
• 2016

In this paper, we propose a hybrid multi.system-on-chip (H-MSoC) architecture that provides a high-flexibility system in a rapid development time. The H-MSoC approach provides a flexible system-on-chip (SoC) architecture that is easy to configure for physical- and application-layer development. The physical- and application-layer aspects are dynamically designed and modified; hence, it is important to consider a design methodology that supports rapid SoC development. Physical layer development refers to intellectual property cores or other modular hardware (HW) development, while application layer development refers to user interface or application software (SW) development. H-MSoC is built from multi-SoC architectures in which each SoC is localized and specified based on its development focus, either physical or application (hybrid). Physical HW development SoC is referred to as physical-SoC (Phy-SoC) and application SW development SoC is referred to as application-SoC (App-SoC). Phy-SoC and App-SoC are connected to each other via Ethernet. Ethernet was chosen because of its flexibility, high speed, and easy configuration. For prototyping, we used a LEON3 SoC as the Phy-SoC and a ZYNQ-7000 SoC as the App-SoC. The proposed design was proven in real-time tests and achieved good performance.

• 시스템엔지니어링워크숍
• /
• s.4
• /
• pp.86-89
• /
• 2004

A web-based program life-cycle management(PLM) system is introduced to implement the system engineering processes and to provide the development teaceability online. This information system aims for the realization of essential system engineering management techniques currently applied to the space launch system development program including management of configuration and data based on the work breakdown structure(WBS), WBS, bill of materials and properties. The system enhances communication and gives access to the development data with relevant information such as data-to-data relation and approval status/history through the web, and preserve all of the development data throughout the program life-cycle. Further improvement of the system is planned to implement the program managrment pricesses and to provide integrated information useful for the programmatic decision making.

• Journal of the Korean Society of Systems Engineering
• /
• v.2 no.1
• /
• pp.48-53
• /
• 2006

A web-based program life-cycle management(PLM) system is introduced to implement the system engineering processes and to provide the development traceability online. This information system aims for the realization of essential system engineering management techniques currently applied to the space launch system development program including management of configuration and data based on the work breakdown structure(WBS), WBS, bill of materials and mass properties. The system enhances communication and gives access to the development data with relevant information such as data-to-data relation and approval status/history through the web, and preserve all of the development data throughout the program life-cycle. Further improvement of the system is planned to implement the program management processes and co provide integrated information useful for the programmatic decision making.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.25 no.6
• /
• pp.628-636
• /
• 2022

This paper describes the design of the avionics architecture for military unmanned aerial vehicles considering the airworthiness requirements for the first time. This design considers the redundancy in the system data bus and the power system and the data link system to meet the system safety requirements of the airworthiness requirements of military UAVs. This avionics architecture design has been verified through the system integration test and the flight test after manufacturing the UAV.

• Proceedings of the Korean Society of Precision Engineering Conference
• /
• 2006.10a
• /
• pp.569-570
• /
• 2006

• Proceedings of the Korean Nuclear Society Conference
• /
• 2005.10a
• /
• pp.1073-1074
• /
• 2005

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.23 no.57
• /
• pp.93-102
• /
• 2000

The objective of this paper is to introduce to development of resource planning system of footwear manufacturing. The system development is to be done separately by module and each of which makes interface possible. And the final goal of the system development is to combine those modules to be ERP system covering all works from order to make, shipment, accounting. First, in this case study, introduce analysis of existing business flow and design of standard business process for development of systems. Second, describe in and out of the standard business process for shoes production and information management. Third, basic structure and design of the total system flow, configuration of completed 6 sub-systems of developing total 13 sub-system are presented. Fourth, function of software modules and principal algorithm and basic data structuring techniques o the 6 sub-systems are explained. Finally, hereafter implementation and development plans are presented.

• IE interfaces
• /
• v.16 no.spc
• /
• pp.127-131
• /
• 2003

Component-based development approach is used in modern software system development projects that are very complex and large-scale. Technical components are more effective rather than business components in software development. However, on the Microsoft .net environment, the technical component-based development issues are not adopted. Moreover, software architecture on the .net environment is not studied yet because the development platform is recently used in the development of enterprise-level system. This paper proposes a technical component-based software architecture on .net environment. Seven technical components - configuration, data access, exception, file I/O, log, message, and paging - are contained in the architecture. The proposed architecture enables developers to reduce development time and to concentrate business logic rather than architectural issues. To verify the proposed architecture and the components, a partner management system is developed based on the architecture.

• Proceedings of the Korean Nuclear Society Conference
• /
• 2005.05a
• /
• pp.1293-1294
• /
• 2005