Command Program (CP) Autocoding - Verilog


TECHNICAL OBJECTIVES
  • Extend autocoding successes to CP domain
  • Identify and enhance COTS graphical design, simulation and autocoding tool
  • Couple PGM development environment with CP development environment
  • Prototype Application Interface Builder (AIB) to raise CP development abstraction
  • Demonstrate CP development environment

STATUS
  • Funded Verilog, Inc. to enhance ObjectGEODE
  • Implementing "Smart Stubs" for MCCI CPI
  • Implementing prototype Application Interface Builder (AIB)
  • Demonstrated concepts at 11/96 RASSP Conference

Verilog:encontre@verilogusa.com    (972) 241 - 6595
MCCI:crobbins@mcci.arl.va.com    (703) 522 - 7177

FUNDAMENTAL CP REQUIREMENTS
  • Translate high level (user) input (e.g., stop track mode, start weather mode) into lower level signal processor control commands (e.g., create queue, write graph variable)
  • Forward signal processor results to command and control system
FUNDAMENTAL CP DESIGN APPROACH
  • Finite State Machine with transitions issuing the low level signal processor control command sequences


Previous Quad

Next Quad
WBS Element No.: 1.2.5.1
Point of Contact: Clay Fickle (609) 338 - 4028
or e-mail cfickle@atl.lmco.com

Quad Index

Acronyms