130 likes | 248 Vues
Tactical Systems Common Operating Environment (TS-COE). Team A1 Williamson, MacFarlane, Crabtree. Problem. Re-implementing Common Functions on multiple Projects with no requirements changes Application Code locked to O/S and Hardware
E N D
Tactical Systems Common Operating Environment (TS-COE) Team A1 Williamson, MacFarlane, Crabtree
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
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
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
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
API Logic Layer O/S and Communication Bindings TS-COE Sub-Layers
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)
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)
Application Interfaces(documented in sequence diagrams) threads MissileGuidance FmControl Arm Mailboxes (across VME and shared memory) GuidanceResults
Other Approaches • RT-COE • DAPRA Project • Large Scale Computing • RT-CORBA • DII COE Recommended for weapons system domain • Client/Server Distributed Object