Military Communications and Information Technology: A Trusted ...

Military Communications and Information Technology: A Trusted ... Military Communications and Information Technology: A Trusted ...

22.01.2015 Views

210 Military Communications and Information Technology... Another family of computer languages, which will be in focus of our attention, is the family of domain-specific languages. Domain-specific languages (DSLs) are computer languages designed for a specific class of problems and for particular application domains [2], [3]. They can be dedicated to a particular problem domain, a particular problem representation technique or a particular solution technique. The basic idea behind DSLs is to offer means which would allow expressing solutions in the idioms and at the abstraction level of the problem domain. The consequence is that domain experts (or qualified users) can express, validate or modify solutions described in a particular DSL. They might be designed with the intention to be [3], [4]: • Programming languages dedicated for a particular problem domain, or • Specification languages dedicated for a particular problem domain. DSLs can have both textual and graphical (visual diagrams) forms. The latter one is popular due to an increasing number of supporting tools for its creation (e.g. Generic Eclipse Modeling System, or Microsoft Visual Studio DSL); the former one usually brings higher productivity. DSLs can be classified as either internal or external. Internal DSLs are only extensions of existing general-purpose computer languages. They are sets of functions, data structures, and conventions applied to existing languages, such as C++ or Java. On the contrary, external DSLs are independent languages that have been entirely designed for their specific purpose. Generally, a DSL “program” can be viewed as a text file, which is then interpreted (or compiled) by the corresponding engine or subsystem. The great advantage of properly-designed DSLs is that they are both: • Human-readable and understandable (in comparison with, for example, XML-based languages, which are also sometimes considered to be humanreadable), and • Machine-processible, since they have formally defined syntax and semantics. DSLs are primarily used in software engineering where they can help overcome the gap between the worlds of domain experts and implementers of software systems. Their design and implementation are challenging tasks since they require expert knowledge of both the problem domain and the area of computer languages, language processors, compilers, and interpreters. CLs (DSLs) have promising potential to be utilized within modern C2 systems. This potential comes from the fact that military application domains have established their own terminology with quite formal syntax and semantics [5] as well as a standardized way of information exchange [6]. Currently probably the most significant initiative within NATO connected with the utilization of artificial CLs is a series of projects and activities connected with the development of the Coalition Battle Management Language (C-BML) [7], [8], [9], [10]. The objective was to “define an unambiguous language to describe a commander’s intent, to be understood by both live forces and automated systems, for simulated and real world operations. The resulting language is intended to be applicable not only to simulation systems,

Chapter 3: Information Technology for Interoperability and Decision... 211 but also to operational command and control systems, and robotic systems” [7]. The language developed on the basis of Command and Control Lexical Grammar (C2LG) with a GUI editor [8], [9] is an XML-based one and a series of experiments and demonstrations has been undergone with the aim to prove that C-BML is a promising tool for the exchange of orders and reports between individual C2 systems and constructive simulators [10]. Since the author of this contribution has not been involved in the aforementioned projects, in the rest of the paper we will try for an “independent” view of the topic. We consider DSLs to be a supplementary technology that could be used together with the mainstream ontology and semantic web technologies. In the case of C2 systems we see the following areas of utilization of DSLs: • Specification and modeling tools in the process of development of C2 systems, and • Subsystems of C2 systems themselves. In this paper we will consider the latter possibility of utilization. A DSL subsystem can be incorporated into the architecture of a C2 system (Fig. 1). The DSL subsystem is used by the User Interface and/or System Integration Interface subsystems and its role is to process inputs in the form of documents prepared in the DSL. These documents can have both textual and graphic forms containing, for example, observed and human-processed information about the battlespace awareness and knowledge that can influence the Common Operational Picture (COP), or they could also contain direct commands that could be processed by the Executive Control Subsystem, which could disseminate them to the appropriate entities. Figure 1. Elements of an architecture of a C2 system that are interesting from a DSLs point of view

Chapter 3: <strong>Information</strong> <strong>Technology</strong> for Interoperability <strong>and</strong> Decision...<br />

211<br />

but also to operational comm<strong>and</strong> <strong>and</strong> control systems, <strong>and</strong> robotic systems” [7].<br />

The language developed on the basis of Comm<strong>and</strong> <strong>and</strong> Control Lexical Grammar<br />

(C2LG) with a GUI editor [8], [9] is an XML-based one <strong>and</strong> a series of experiments<br />

<strong>and</strong> demonstrations has been undergone with the aim to prove that C-BML<br />

is a promising tool for the exchange of orders <strong>and</strong> reports between individual C2<br />

systems <strong>and</strong> constructive simulators [10]. Since the author of this contribution<br />

has not been involved in the aforementioned projects, in the rest of the paper we<br />

will try for an “independent” view of the topic.<br />

We consider DSLs to be a supplementary technology that could be used together<br />

with the mainstream ontology <strong>and</strong> semantic web technologies. In the case<br />

of C2 systems we see the following areas of utilization of DSLs:<br />

• Specification <strong>and</strong> modeling tools in the process of development of C2<br />

systems, <strong>and</strong><br />

• Subsystems of C2 systems themselves.<br />

In this paper we will consider the latter possibility of utilization. A DSL subsystem<br />

can be incorporated into the architecture of a C2 system (Fig. 1). The DSL<br />

subsystem is used by the User Interface <strong>and</strong>/or System Integration Interface subsystems<br />

<strong>and</strong> its role is to process inputs in the form of documents prepared in the DSL.<br />

These documents can have both textual <strong>and</strong> graphic forms containing, for example,<br />

observed <strong>and</strong> human-processed information about the battlespace awareness <strong>and</strong><br />

knowledge that can influence the Common Operational Picture (COP), or they<br />

could also contain direct comm<strong>and</strong>s that could be processed by the Executive<br />

Control Subsystem, which could disseminate them to the appropriate entities.<br />

Figure 1. Elements of an architecture of a C2 system that are interesting from a DSLs point of view<br />

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!