The Big Data Interagency Working Group (BD IWG) works to facilitate and further the goals of the White House Big Data R&D Initiative.
The CPS IWG is to coordinate programs, budgets, and policy recommendations for Cyber Physical Systems (CPS) research and development (R&D).
Cyber Security and Information Assurance (CSIA) Interagency Working Group coordinates the activities of the CSIA Program Component Area.
The Health Information Technology Research and Development Interagency Working Group coordinates programs, budgets and policy recommendations for Health IT R&D.
HCI&IM focuses on information interaction, integration, and management research to develop and measure the performance of new technologies.
HCSS R&D supports development of scientific foundations and enabling software and hardware technologies for the engineering, verification and validation, assurance, and certification of complex, networked, distributed computing systems and cyber-physical systems (CPS).
The HEC IWG coordinates the activities of the High End Computing (HEC) Infrastructure and Applications (I&A) and HEC Research and Development (R&D) Program Component Areas (PCAs).
LSN members coordinate Federal agency networking R&D in leading-edge networking technologies, services, and enhanced performance.
The purpose of the SPSQ IWG is to coordinate the R&D efforts across agencies that transform the frontiers of software science and engineering and to identify R&D areas in need of development that span the science and the technology of software creation and sustainment.
Formed to ensure and maximize successful coordination and collaboration across the Federal government in the important and growing area of video and image analytics
The Wireless Spectrum R&D (WSRD) Interagency Working Group (IWG) has been formed to coordinate spectrum-related research and development activities across the Federal government.
SOFTWARE PRODUCT LINE TECHNOLOGIES FOR MILITARY SYSTEMS For The SOFTWARE DESIGN AND PRODUCTIVITY COORDINATING GROUP WORKSHOP ON NEW VISIONS FOR SOFTWARE DESIGN AND PRODUCTIVITY: RESEARCH AND APPLICATIONS
Mr. David Sharp
The Boeing Company
Mr. Don C. Winter
The Boeing Company
In 1995, an initiative was launched at Boeing (then McDonnell Douglas) to assess the potential for reuse of operational flight program (OFP) software across multiple fighter aircraft platforms, and to define and demonstrate a supporting system architecture based upon open commercial hardware, software, standards and practices . The following year, this became a key element of the Bold Stroke Open System Architecture avionics affordability initiative which applied these techniques to the broader tactical aircraft mission processing domain. The Bold Stroke architecture, application components, middleware framework, and development processes have been leveraged on an increasing number of military platforms of national importance including manned and unmanned vehicles for the USAF and USN.
Our experiences on this effort have demonstrated the dramatic increases in software development productivity possible through use of cross-platform reuse and highly portable and standardized run-time subsystems. They have also highlighted weaknesses in several areas which significantly impact overall system cost, quality, and timeliness, many of which are unique to large-scale distributed real-time embedded (DRE) systems. Embedded system product lines depend on suitable domain specific architectures, run-time frameworks, application component libraries, and component development and integration tools and processes, and stress these capabilities beyond what would be sufficient for single system development approaches. In weapon systems, key remaining technology hurdles include (1) integration of thousands of software components with real-time deadlines; (2) integration of hard and soft real-time components; (3) enlargement in scope of quality of service resource management services from single processors to widely networked systems; (4) establishment of safety critical and mixed criticality runtime frameworks; (5) interoperability with closed legacy systems; (6) retention of high security levels while opening up strike assets to greater and greater levels of tactical network connectivity; and (7) infusing new technologies into fielded systems. In addition to these “design-centric” challenges, additional important challenges are contained at the front and back ends (i.e. requirements definition and verification) of the embedded system development process.
Click on a date/time to view the file as it appeared at that time.
|current||10:49, 27 December 2012||(127 KB)||Webmaster||Category:SDP|