• Big Data
    Interagency Working Group
    (BD IWG)

    The Big Data Interagency Working Group (BD IWG) works to facilitate and further the goals of the White House Big Data R&D Initiative.

    BigData
  • Cyber Physical Systems Interagency Working Group (CPS IWG)

    The CPS IWG is to coordinate programs, budgets, and policy recommendations for Cyber Physical Systems (CPS) research and development (R&D).

    CPS
  • Cyber Security and Information Assurance Interagency Working Group (CSIA IWG)

    Cyber Security and Information Assurance (CSIA) Interagency Working Group coordinates the activities of the CSIA Program Component Area.

    CSIA
  • Health IT R&D
    Interagency Working Group

    The Health Information Technology Research and Development Interagency Working Group coordinates programs, budgets and policy recommendations for Health IT R&D.

    healthitrd
  • Human Computer Interaction & Information Management Interagency Working Group (HCI&IM IWG)

    HCI&IM focuses on information interaction, integration, and management research to develop and measure the performance of new technologies.

    hciim
  • High Confidence Software & Systems Interagency Working Group (HCSS IWG)

    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).

    hcss
  • High End Computing Interagency Working Group (HEC IWG)

    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).

    hec
  • Large Scale Networking Interagency Working Group
    (LSN IWG)

    LSN members coordinate Federal agency networking R&D in leading-edge networking technologies, services, and enhanced performance.

    lsn
  • Software Productivity, Sustainability, and Quality Interagency Working Group (SPSQ IWG)

    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.

    sdp
  • Video and Image Analytics
    Interagency Working Group (VIA IWG)

    Formed to ensure and maximize successful coordination and collaboration across the Federal government in the important and growing area of video and image analytics

    VIA CG
  • Wireless Spectrum Research and Development Interagency Working Group (WSRD IWG)

    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.

    WSRD

File:R gamble beyond documentation.pdf

From NITRDGROUPS
Jump to: navigation, search
R_gamble_beyond_documentation.pdf(file size: 50 KB, MIME type: application/pdf)

Beyond Documentation

R. Gamble* L. Davis D. Flagg G. Jonsdottir

Department of Mathematical and Computer Sciences

University of Tulsa

...

Abstract

Software component integration is increasingly permeating product development, impacting everything from government, ecommerce and enterprise application systems. While companies and government agencies attempt to streamline their business and provide better customer service, software and middleware vendors are all vying for dominance to bridge the gap between legacy software and COTS, and the new technology that is available to integrate them. There are a number of major problems with this scenario, particularly those with respect to determining the fit of a component in a multi-component application, instantiating the medium by which components should be connected, assuring that the integration meets security requirements, and defining the enterprise infrastructure that enfolds them.

We seek to demystify the integration process. The objective of our research is to efficiently assess qualified software properties, as well as other factors that constrain the multi-component application. To commence the assessment process, we use a software component conspectus that embodies static, architecturally significant properties. These properties can be easily described in the XML, making them portable and extensible, as well as available as part of online documentation. The evaluation produces the major architecture conflicts among the components and any requirements that govern the overall application. The conflicts can then be used to define the basic integration functionality needed for the middleware architecture. Hence, the result of this evaluation is an integration architecture that encompasses the application and the technology that it comprises.

As we move toward further characterization of the technology at work in a multi-component application, we envision empowering developers to quickly assess their software components and integration needs. However, a critical issue is getting software and middleware vendors to embrace the conspectus idea: to go beyond traditional documentation toward qualifying a uniform set of properties that make evaluation easier. To develop the assessment technology, we must define the relevant properties of components, communication mediums, middleware, infrastructures and security concerns in a normalized and uniform way. The values of these properties should be easily discernable from documentation, external interfaces, functional paradigms, or application domains. With the advent of this technology businesses can achieve a large payoff by lessening time and developer resources.

...

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeDimensionsUserComment
current11:05, 27 December 2012 (50 KB)Webmaster (talk | contribs) Category:SDP

There are no pages that link to this file.