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

30 Military Communications and Information Technology... information. In the first step a request is processed. Next, request for evacuation of civilians from a threatened area is send to service provided by external organization. Finally, the request for fire on target is send. Process results are saved. Initiating events are generated according to closed stream described using the GAWorkloadEvent stereotype. Process steps which consume time are modeled using the PaStep stereotype. Some of the services can use other services to fulfill their functionality. The TargetMsgService sends information about the target to two other services: ISTARService and ArtilleryService. The TargetMsgService behavior and its interaction with other services is shown on Fig. 7. Requests which consume time and resources are modeled using the PaStep stereotype. Figure 6. Example NSOV-4 Operational Activity Model Figure 7. Example NSOV-5 Service Behaviour

Chapter 1: Concepts and Solutions for Communications and Information Systems 31 Figure 8. Example NSOV-2 Service Definitions Services are described through well-defined interfaces. An interface definition is an independent from the underlying platform on which a service implementation operates. Fig. 8 shows an example service definition. Class diagram with SoaML profile is used. The TargetMsgService provides two operations. To implement its functionality the services ISTARService and ArtilleryService are required. Fig. 7 describes the TargetMsgService behavior and depicts how the required services are used. A service is a concept which represents well defined fragment of an operational functionality so it is at a level above the technology details. Each functionality described by a service is implemented by software components or legacy systems which are responsible for quality of those services. Fig. 9 describes the software components as well as the provided and required service interfaces. The ISTARComponent is an adapter to the legacy system (ISTARSystem) and implements the service defined by the ISTARService interface. A component implements a set of operations. The behavior of methods describes scenario and can be specified using interaction diagrams. Fig. 10 presents the specification of the example method. Furthermore, methods have demands for resources which is modeled using MARTE profile. Requests which consume resources are modeled using the PaStep stereotype, while communicates send by network are stereotyped using the PaCommStep. Figure 9. Example NSV-12 Service Provision

Chapter 1: Concepts <strong>and</strong> Solutions for <strong>Communications</strong> <strong>and</strong> <strong>Information</strong> Systems<br />

31<br />

Figure 8. Example NSOV-2 Service Definitions<br />

Services are described through well-defined interfaces. An interface definition<br />

is an independent from the underlying platform on which a service implementation<br />

operates. Fig. 8 shows an example service definition. Class diagram<br />

with SoaML profile is used. The TargetMsgService provides two operations.<br />

To implement its functionality the services ISTARService <strong>and</strong> ArtilleryService<br />

are required. Fig. 7 describes the TargetMsgService behavior <strong>and</strong> depicts how<br />

the required services are used.<br />

A service is a concept which represents well defined fragment of an operational<br />

functionality so it is at a level above the technology details. Each<br />

functionality described by a service is implemented by software components or<br />

legacy systems which are responsible for quality of those services. Fig. 9 describes<br />

the software components as well as the provided <strong>and</strong> required service interfaces.<br />

The ISTARComponent is an adapter to the legacy system (ISTARSystem) <strong>and</strong><br />

implements the service defined by the ISTARService interface.<br />

A component implements a set of operations. The behavior of methods describes<br />

scenario <strong>and</strong> can be specified using interaction diagrams. Fig. 10 presents<br />

the specification of the example method. Furthermore, methods have dem<strong>and</strong>s<br />

for resources which is modeled using MARTE profile. Requests which consume<br />

resources are modeled using the PaStep stereotype, while communicates send<br />

by network are stereotyped using the PaCommStep.<br />

Figure 9. Example NSV-12 Service Provision

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

Saved successfully!

Ooh no, something went wrong!