Tactical Systems Common Operating Environment (TS-COE)

1
Tactical Systems Common Operating Environment
(TS-COE)

• Team A1
• Williamson, MacFarlane, Crabtree

2
Problem

• Re-implementing Common Functions on multiple
  Projects with no requirements changes
• Application Code locked to O/S and Hardware
• Difficult to test Software reliably before Target
  Hardware is ready

3
Requirements/Assumptions

• Maximum Use of COTS Processors and Operating
  Systems
• Handle High Bandwidth Sensors and DSP
• Application Domain
• Static Threads
• Static Scheduling
• Simulation before Hardware

4
TS-COE

• Tactical Systems Common Operating Environment
  (TS-COE)
• Language, O/S Independent
• Product and a Design Methodology
• Simple to Implement
• Improves Embedded, Real-Time Software
  Productivity and Reliability

5
TS-COE Facilities
6
Typical TS-COE Software Layers
Applications
COE Extensions
Drivers
Legacy API
Legacy Wrapper
COE
VxWorks/BSP/Drivers
Board Specs
Hardware
COE
MCCR
From Board Vendor
7
TS-COE Sub-Layers
8
Endpoints(implemented one or more per thread)
Sending thread(s)
Receiving thread (owns the pipe/endpoint)
Thread pops one mailbox at a time out of endpoint
and processes it
Mail
Registered mail goes in here when sent by
sending thread(s) (FIFO)
9
Design Methodology

• Decomposition into Tasks
• Inter-task Communication
• Sequence Diagrams
• Task State Machine Design
• State Charts
• Coding to Thread Templates
• Simulation
• Universal Test Driver (UTD)

10
Application Interfaces(documented in sequence
diagrams)
threads
MissileGuidance
FmControl
Arm
Mailboxes (across VME and shared memory)
GuidanceResults
11
Sample State Chart
12
Sample UTD Input Files
13
Other Approaches

• RT-COE
• DAPRA Project
• Large Scale Computing
• RT-CORBA
• DII COE Recommended for weapons system domain
• Client/Server Distributed Object