White Papers

Read from our White Paper library

Zeligsoft's White Papers contain a wealth of information about Zeligsoft's Component-Oriented Engineering (COE) methodology, component-based software development, and best-practice development processes.

We'd like the opportunity to field any questions you may have about our White Papers so please don't hesitate to contact us at info@zeligsoft.com.

  • Code harvesting with component modeling increases software reuse and improves developer efficiency for embedded systems applications. Zeligsoft’s Component Oriented Engineering (COE) methodology, CX development tool suite and expertise can be used to harvest legacy application code and transform it into a component-based, model-driven digital asset. This can reduce code size by 20-40% and development efforts by 40-60%.

  • Improving embedded software development productivity is rapidly becoming the overwhelming mantra of product companies across a wide range of industries. Recognizing the need for new software development approaches to successfully address these growing challenges, industry is increasingly looking to modeling and software component technologies to help them succeed. This paper proposes a new approach to help organizations realize the promise.

  • Component-based software development, deployment and configuration for Software Defined Radio using the Software Communications Architecture (SCA) has seen an increased interest in the past few years. This paper provides an introduction to the SCA and highlights the goals it is trying to achieve and the technology it uses.

  • All project teams developing software based on the Software Communications Architecture (SCA) standard need to create descriptor files that accurately describe their system. Many teams have manually authored these descriptor files early in their development process. This paper discusses the cost of unvalidated descriptor files and provides a tool-based solution.

  • SCA systems are based on portable, component-based applications executing on flexible hardware platforms. The actual assignment or deployment of software components to hardware devices is done at system initialization time. How can the architect or system integrator ensure that this assignment will work properly and be fully tested? This paper answers that question. 

  • Until now, SDR standards have focused on General Purpose Processors. Integration with specialized hardware processors including Digital Signal Processors (DSPs) and Field Programmable Gate Arrays (FPGAs) has been done mostly manually and in a non-systematic manner. This is about to change with different standards for DSP and FPGA integration being proposed. This paper provides a high-level introduction of the various standards and highlights the differences between them.

  • Software Communications Architecture (SCA) systems are designed to be flexible in terms of run-time deployment. A single waveform can be deployed dynamically across a heterogeneous execution environment. Understanding deployments is a crucial aspect of testing and delivering a waveform.This paper will look at monitoring and analyzing deployments in a running system.

  • Component based software design depends heavily on communication between components. In the past engineers have tried to minimize communication delays by combining components into monolithic systems or by using custom coded transportation mechanisms. This has resulted into in-flexible, fragile systems that are hard to design and test. This paper demonstrates through performance measurements that a high-performance ORB like OIS’s ORBexpress makes flexible, reusable component based software designs a reality.

  • The definition and coding of a component that makes up part of an SCA system requires detailed knowledge of the SCA standard, and continuous attention to the external interface of the component. SCA specific coding tools and automation used in the development process can make component development much more manageable and can thus accelerate SCA development, and improve software quality. This paper provides an overview of the source code requirements for an SCA component, and the design considerations that should be taken by the developer.