Software reuse is a common strategy in developing complex systems and has proven successful in reducing labor and maintenance costs. However, simply reusing modules will not produce a system that is adaptable to a variety of mission requirements. Because of this, projects often involve development of similar software systems from scratch in order to satisfy requirements. The end result is a system that can only operate in a specific environment and be used only in a specific way, with consequentially higher costs for maintenance and user training. Component architecture consists of a framework that defines the standard interactions between components and standard interfaces for useful components to attach to the framework and interact with other components. Modern object-oriented programming languages are very good in their support for static interfaces, but need additional work in the area of dynamic interfaces. Reflection, which is available in some 00 languages, should be considered in developing model component systems to enable dynamic discovery of service components at runtime. This enables software systems to be assembled at deployment time and provide users the ability to customize the software system with respect to their operating environment. Our File Exchange Interface (FEI) is af ile transaction service that offers portable, high performance, database-driven file management and transfer service. Unlike the common File Transfer Protocol (FTP), FEI provides file integrity verification on the fly, user authentication and authorization support, and database transaction management. FEI played a major role in file archiving and delivery service in flight missions such as Galileo
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.