• The KIPS Transactions:PartD
• /
• v.12D no.7 s.103
• /
• pp.1001-1006
• /
• 2005

The Ministry of National Defense has developed MND-AF and Defense-CBD methodology to make the integration and management of standardization effective through enhancing the interoperability and reusability of information systems. Yet no explicit guidelines or procedures have not been developed for the applying range and mutual relationship of the artifacts between MND-AF and Defense-CBD methodology. Thus, the development time is unnecessarily extended and budget also is increasing because both methodologies produce the artifacts respectively. This paper presents a reusability enhancement scheme for producing MND-AF artifacts according to Defense-CBD process by analyzing artifacts of two methodology les at each element level, so that it will reduce the overhead of producing the artifacts and enhance the completeness of the artifacts. In result, in the case of applying Defense-CBD methodology for developing a information system34 artifacts out of 37 MND-AF artifacts can be reusable.

• Journal of the military operations research society of Korea
• /
• v.32 no.2
• /
• pp.131-142
• /
• 2006

Nowadays, most enterprises have introduced both EA methodology to optimize an entire enterprise and CBD methodology to improve a software reusability. The Korea Government not only have developed many EA guiding products such as EA framework, Reference Model, Guideline, etc. but also have instituted a law to optimize a government-wide enterprise. The Minister of National Defense(MND) have developed the MND-AF as a standard methodology for EA and the ADDMe as a standard methodology for CBD. But it is possible to develop products of WD-AF and ADDMe redundantly because the process of MND-AF and ADDMe is not quitely aligned. The purpose of this paper is to present a scheme that ADDMe can reuse the artifacts of MND-AF by analyzing the relationships between two processes. In order to identify the relationships between two processes, we first identify the relation of a 'definition' part of two processes and then identify the relation of an 'attribute' part based on the relation of a 'detailed definition' part. As a result we found that 113 attributes of MND-AF are related to 49 attributes of ADDMe. Therefore the proposed study will decrease the development cost and time and will be a good example for aligning the process of EA and CBD methodology.

• Journal of Information Technology and Architecture
• /
• v.10 no.3
• /
• pp.315-321
• /
• 2013

The ROK military has established the MND-AF (Ministry of National Defense- Architecture Framework) and is applying it when developing architecture for Enterprise (MND), Segment (component) and Solution (weapons and force support system). The AMM (Architecture Meta model) of the MND-AF supports the establishment of interoperability by systematizing the architecture information structure defined by the Architecture artifact, describing the relationship between data and also by liking reference models and Information technology standard, common components, and MND-Meta data. which are interoperability standards. However, the MND-AMM has insufficient linkage with the standards, which places constraints on applying interoperability standards when developing Solution architecture. This study suggests a logical data model (OV-7c) from the MND-Meta-data-based Architecture meta model that will enhance the application of MND meta data managed by the MND interoperability standard when developing Solution architecture.

• Journal of Information Technology Services
• /
• v.3 no.2
• /
• pp.129-140
• /
• 2004

Traditional information systems in the Ministry of National Defense(MND) are insufficient about interoperability between all kinds of them. Also there is no the applicable architecture framework to develop information systems. The Architecture Framework(AF) is to provide guidance for describing architectures for both warfighting operations and business operations and processes in the MND. Therefore, in this paper we propose the MND AF to develop and manage information systems in the MND.

• The KIPS Transactions:PartD
• /
• v.11D no.2
• /
• pp.407-414
• /
• 2004

The US DoD architecture framework defines architecture Products according to three viewpoints : operational view, system view, and technical view. But, its coarse-grained development process causes leakage of the details In transforming among different views. It also uses different methods for architecture products development, so that the levels of those products are not consistent. So. we propose MND AF(Ministry of National Defense Architecture Framework) for military environment to solve those problems. We propose additional architecture products to achieve consistency, including “architecture disciplines definition description,”“organization-to-activity relationships matrix,” “system definition description,” and “technical reference model,” etc. We also propose the architecture development process in more detail through seven steps. In addition, we propose the applicability of those products to the life cycle processes of the acquisition management. MND AF can provide consistency and traceability of architecture products, provide the basis for sl·stem integration and interoperability. Also, architecture developers can construct architecture in a more effective and efficient way through MND AF.

• Journal of the Korean Society of Systems Engineering
• /
• v.16 no.2
• /
• pp.118-130
• /
• 2020

Modern weapon systems are composed of complex systems(System of Systems) and require a complex and advanced operational concept that performs missions through interoperability with various weapon systems. In order to derive the operational concept of the weapon system that the military wants to acquire (i.e., single mission, component operation, Joint and Alliance operations), it is necessary to identify the system related to the weapon system, environmental factors and restrictions of the weapon system to be developed. Through the derivation of the operational concept, the weapon system acquisition agency can reasonably and accurately extract various and complex requirements. In this paper, we propose a complementary method of using MND-AF to OCD and ORD required in weapon system acquisition process. MND-AF can increase the understanding and consensus of business stakeholders (users, acquirers, developers, etc.) by showing the results of weapon system analysis from various perspectives. We compare the items in the standard form of OCD and ORD with the MND-AF outputs.

• The KIPS Transactions:PartD
• /
• v.12D no.6 s.102
• /
• pp.857-862
• /
• 2005

MND(Ministry of National Defense) has developed MND AF(Ministry of National Defense Architecture Framework) and CADM(Core Architecture Data Model to guarantee interoperability among defense information systems. But, it is very difficult to manage architecture product documented through MND AF and CADM. So, there Is necessity for development of modeling tool and repository system which can develop architecture products and manage architecture product informations in common repository In this paper, we developed architecture product management system which supports development and management of meta model and architecture product of MND AF and CADM. Through architecture product management system architect of each agency can construct architecture product in a more effective and efficient way with modeling method and a user can search and refer useful architecture product informations using query function. Also, architecture product management system provides the basis for system integration and interoperability with integration, analysis and comparison of architecture product.

• The KIPS Transactions:PartD
• /
• v.12D no.5 s.101
• /
• pp.729-736
• /
• 2005

MND(Ministry of National Defense) has developed MND AF(Ministry of National Defense Architecture Framework) and CADM(Core Architecture Data Model) to guarantee interoperability among defense information systems. TRM(Technical Reference Model) and SP(Standard Profile) product defined in MND AF is core part of Information Technology Architecture and core element of interoperability guarantee. In this paper, we proposed a method which manages technical service and standard of TRM and SP, and developed TRM and SP management system based on the method. TRM and SP management system provides the basis for interoperability among information systems and a more efficient development and management of TRM and SP product.

• Journal of the Korean Society of Systems Engineering
• /
• v.11 no.1
• /
• pp.25-31
• /
• 2015

Under the relevant regulations, it is required to develop a system architecture for the research and development of the information and communication infra system ; however, the national defense architecture development guides and MND-AF, which provide the instructions on the development and utilization of a system architecture, are still limited to the ITA level and merely providing the guidelines for developing the information system centric architecture. Thus, it is evident that we need a suitable architecture development methodology that corresponds to the growing needs for the communication infra system architecture, as well as the general weapon system architecture. Improving a meta-model is the core of improving a architecture framework. It determines a contents of a architecture and it influences a efficiency and a effectiveness of a architecture. The meta-model of the architecture framework must reflect concerns of various stakeholders and provide a traceability among them. Also, it should be easy to develop and use the architecture by securing the feasibility of the logical relationships and eliminating the duplication of the data inside the architecture. It is implemented through the development of the data-centric architecture and achieved through the "Fit-for-purpose" concept.

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.683-690
• /
• 2004

MND(Ministry of National Defense) has developed .nm AF(Ministry of National Defense Architecture Framework) to guarantee interoperability among defense information systems. Users can easily and consistently develop architecture products through MND AF. There is necessity for development if CADM(Core Architecture Data Model), which facilitate exchange, integration, and comparison for architecture data, to store architecture data from architecture products and reuse them. We developed CADM from defining entities and relationships that satisfy data requirement of each architecture product from MND AF. After we developed architecture products about MIMS(Military Intelligence Management System), and inserted these architecture data to CADM repository. we verified CADM entities and relationships through query. Through CABM which provides common data model for the whole my architectures, interoperability and integration among defense information systems ran be improved, and integrated defense information resources efficiently can be managed.