By Topic

Possibilities for Improving Dependability of C4I2SR Systems Based on Service-Oriented Architecture

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Jormakka, Jorma ; Dept. of Mil. Technol., Nat. Defence Univ., Helsinki, Finland ; Lucenius, J.

Service oriented architecture (SOA) is currently the way to design and integrate information services in enterprises. SOA is usually based on Web services,originating from the e-business world, but SOA is not only technology, it is more of a philosophy. SOA has been selected as the architectural solution for the new command, control, communication, computers, information, intelligence, surveillance and reconnaissance (C4I2SR) system of the Finnish defense forces. The task of the military is not Internet business and therefore SOA is not used for the purpose that it is created. Dependability demands, such as reliability, availability, security, of a C4I2SR system are high but a service oriented design approach cannot use many of traditional ways of achieving high dependability. In this paper we describe some dependability problems of SOA, and our ideas on how to solve these problems. Particularly, thorough design and management aspects are important. It seems like we have to model, design and test carefully both the underlying logic and protocols, and the high level services, i.e. combine a down-up and top-down approach. One aspect, which we have to be aware of are service interactions, at least if services get complicated. The non-functional requirements and performance parameters should be defined for a military SOA-based system. This may, however, be difficult in CC4I2SR as the final use cases are not necessarily predictable in advance. During use, the system should be monitored in order to identify the problems and enable correcting actions.

Published in:

Future Computing, Service Computation, Cognitive, Adaptive, Content, Patterns, 2009. COMPUTATIONWORLD '09. Computation World:

Date of Conference:

15-20 Nov. 2009