A Federated Design for a Neurobiological Simulation Engine: The CBI Federated Software ArchitectureReport as inadecuate




A Federated Design for a Neurobiological Simulation Engine: The CBI Federated Software Architecture - Download this document for free, or read online. Document in PDF available to download.

Simulator interoperability and extensibility has become a growing requirement in computational biology. To address this, we have developed a federated software architecture. It is federated by its union of independent disparate systems under a single cohesive view, provides interoperability through its capability to communicate, execute programs, or transfer data among different independent applications, and supports extensibility by enabling simulator expansion or enhancement without the need for major changes to system infrastructure. Historically, simulator interoperability has relied on development of declarative markup languages such as the neuron modeling language NeuroML, while simulator extension typically occurred through modification of existing functionality. The software architecture we describe here allows for both these approaches. However, it is designed to support alternative paradigms of interoperability and extensibility through the provision of logical relationships and defined application programming interfaces. They allow any appropriately configured component or software application to be incorporated into a simulator. The architecture defines independent functional modules that run stand-alone. They are arranged in logical layers that naturally correspond to the occurrence of high-level data biological concepts versus low-level data numerical values and distinguish data from control functions. The modular nature of the architecture and its independence from a given technology facilitates communication about similar concepts and functions for both users and developers. It provides several advantages for multiple independent contributions to software development. Importantly, these include: 1 Reduction in complexity of individual simulator components when compared to the complexity of a complete simulator, 2 Documentation of individual components in terms of their inputs and outputs, 3 Easy removal or replacement of unnecessary or obsoleted components, 4 Stand-alone testing of components, and 5 Clear delineation of the development scope of new components.



Author: Hugo Cornelis , Allan D. Coop, James M. Bower

Source: http://plos.srce.hr/



DOWNLOAD PDF




Related documents