Design Rules: The Power of Modularity Volume 1
Design Rules: The Power of Modularity Volume 1
| Hi-index | 0.00 |
This paper describes the High Bandwidth High Throughput (HBHT) Government Reference Architecture (GRA) effort and utilization of Dependency Structure Matrix (DSM) tools to validate the architecture. This paper is intended to show how the development of GRA compliant modules advances both new and time-tested technologies through establishing a standard for Above 2 GHz SATCOM Terminal modules. The paper will also describe plans to develop and apply tools, products and solutions to validate the GRA. The paper describes the process associated with engaging industry in developing the GRA Functional Decomposition, validating the GRA through a prototype, creating the GRA as a standardfor the Army HC3 Program, and managing to that architecture and standard in a development environment. The paper also describes how GRA validation through use of DSM tools, such as LATTIX, will aid in the development and testing of a GRA Hardware and Software Interface Test Development Environment designed to allow a GRA module developer to develop, interface, and test interface applications to the GRA compatible open hardware/software interfaces. Full documentation shall be developedfor all open hardware and software interfaces, sufficient to develop applications with minimum interface or interaction with the module developer. Interface definition stability over time will be a key factor in the mission success of the HC3 open system interfaces, so they must be designed with stability and longevity in mind. This paper will review alternatives for validation of GRA compliant modules. Particular emphasis will be placed on DSM techniques. The interdependencies between modules will be modeled using a DSM so as to provide a big picture view of GRA. DSM can also be used to model and expose key design decisions for the entire team. Rules can be established in the DSM model for GRA compliance to guide a GRA module developer during development and testing for validation. The use of DSM to model various hardware and software modules in the HBHT will create a common artifact that can be shared across various teams with different skills and domains of expertise. DSM can also be used to analyze the impact of change. Over time, DSM will provide a blue print of the architecture and how it evolves to meet changing needs.