Over the last few years, electronic warfare systems have grown in number of functionalities, to handle increasingly complex system architectures. Traditional system architectures have reached to the limit of their capabilities, while traditional requirements of electronic warfare systems persist. In order to a system be rapid in production and to have low cost, the system should have the following characteristics: Adaptability to various changes, Enhancement of system quality, Reduction of operation and maintenance cost. Combat Management systems are based on a federation of dedicated and heterogeneous systems, and because of that their operational integration deals with the following difficulties: Lack of operational interoperability, Weak integration of Information Systems services for Situation Awareness (from the strategic level to the tactical level and, Lack of global system management, prohibiting dynamic (re)configuration of systems. Today’s military solution for information exchange, the information flow is typically defined by a set pattern from sender to recipient. It is pre-planned and preconfigured, and changes normally require manual assistance. The solutions used are often stove piped, tailored for certain applications within one military service and with no interoperability with other types of systems. Another problem is the limited exchange of information between security domains [9]. Service Oriented Architecture (SOA) was identified as a possible solution to the above-mentioned problems. Moving towards a Service Oriented Architecture (SOA) is a way to achieve the seamless information and service sharing required in a future electronic warfare. The aim of this paper is investigating the affects of SOA on the architecture of Electronic Warfare Simulation software in terms of reusability and performance. In this paper, common functionalities of electronic warfare systems developed in DLRL are implemented as services.