open systems development initiative (osdi) systems development initiative (osdi) unclassified 5a....
Post on 21-Mar-2018
231 Views
Preview:
TRANSCRIPT
John T. PaulJohn T. PaulNaval Air Warfare Center - Weapons DivisionNaval Air Warfare Center - Weapons Division
China Lake, CAChina Lake, CA
Open Systems Development Initiative (OSDI)Open Systems Project Engineering Conference (OSPEC)
FY 98 Status Review29 April - 1 May 1998
REPORT DOCUMENTATION PAGE Form Approved OMB No.0704-0188
Public reporting burder for this collection of information is estibated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completingand reviewing this collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burder to Department of Defense, WashingtonHeadquarters Services, Directorate for Information Operations and Reports (0704-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. Respondents should be aware that notwithstanding any other provision oflaw, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. PLEASE DO NOT RETURN YOUR FORM TO THE ABOVE ADDRESS.
1. REPORT DATE (DD-MM-YYYY)29-04-1998
2. REPORT TYPEBriefing
3. DATES COVERED (FROM - TO)29-04-1998 to 01-05-1998
4. TITLE AND SUBTITLEOpen Systems Development Initiative (OSDI)Unclassified
5a. CONTRACT NUMBER5b. GRANT NUMBER5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S)Paul, John T. ;
5d. PROJECT NUMBER5e. TASK NUMBER5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME AND ADDRESSNaval Air Warfare CenterWeapons DivisionChina Lake, CAxxxxx
8. PERFORMING ORGANIZATION REPORTNUMBER
9. SPONSORING/MONITORING AGENCY NAME AND ADDRESSOpen Systems Joint Task Force (OSJTF)1931 Jefferson Davis HighwayCrystal Mall 3, Suite 104Arlington, VA22202
10. SPONSOR/MONITOR'S ACRONYM(S)11. SPONSOR/MONITOR'S REPORTNUMBER(S)
12. DISTRIBUTION/AVAILABILITY STATEMENTAPUBLIC RELEASE,13. SUPPLEMENTARY NOTES14. ABSTRACTSee Report.15. SUBJECT TERMS16. SECURITY CLASSIFICATION OF: 17. LIMITATION
OF ABSTRACTPublic Release
18.NUMBEROF PAGES24
19. NAME OF RESPONSIBLE PERSONhttp://www.acq.osd.mil/osjtf/library/library_alpha.html,(blank)lfenster@dtic.mil
a. REPORTUnclassified
b. ABSTRACTUnclassified
c. THIS PAGEUnclassified
19b. TELEPHONE NUMBERInternational Area CodeArea Code Telephone Number703767-9007DSN427-9007
Standard Form 298 (Rev. 8-98)Prescribed by ANSI Std Z39.18
Open Systems Development Initiative
Ethernet
RS-232
MIL-STD-1553
RGB
Tornado 1.0.1 Host
Avionics Sub-system Simulation(AV8-B SimC)
Cockpit Displays
May 1, 1998 2Copyright (c) 1998 Naval Air Warfare Center
Goals
COTS technology Object Oriented S/W
Hands-on expertise ina low risk environment
In-house OS expertise
Technology Transfer
AV8B OSCAR
F/A-18 AMC&D
OTHERS
Plug & Play capabilitiesPerformance Characteristics
May 1, 1998 3Copyright (c) 1998 Naval Air Warfare Center
OSDI Relationships
PMA-209
PMA-257 : OSCAR
PMA-265 : AMC&D
Fibre Channel AE
Prime/Subs
COTS Vendors
May 1, 1998 4Copyright (c) 1998 Naval Air Warfare Center
Architecture
• Operational Architecture - Description of the operational elements,assigned tasks, and information flows.
• Systems Architecture - Defines the physical connection, location andidentification of key components, circuits, networks etc., and specifiessystem and component performance parameters.
• Technical Architecture - Identifies the services, interfaces, standards,and their relationships.
May 1, 1998 5Copyright (c) 1998 Naval Air Warfare Center
OSDI System Architecture
Ethernet
RS-232
MIL-STD-1553
RGB
Tornado 1.0.1 Host
Avionics Sub-system Simulation(AV8-B SimC)
Cockpit Displays
May 1, 1998 6Copyright (c) 1998 Naval Air Warfare Center
OSDI Technical Architecture
Backplane COTS PPC Card COTS 1553 Card
Hardware
VxWorks BSP for Tornado 1.0.1
Hardware Dependent Software
Hardware Independent SoftwareOperational Flight Program
OpenGL Graphics Driver
VxWorks Wind Kernel for PPC
MIL-STD-1553 Driver
Graphics Card
May 1, 1998 7Copyright (c) 1998 Naval Air Warfare Center
OSDI S/W Architecture
VxWorks Wind Kernel for PPC MIL-STD-1553/Graphics Drivers
Avionics InfrastructureExecutive
NAV
Adv
. Bal
listic
s
HU
D/D
DI
May 1, 1998 8Copyright (c) 1998 Naval Air Warfare Center
OSDI Components
VxWorksWind Kernel
VxWorks BSP
1553 Driver
HUD/DDI
Backplane
PPC Card DY-4 D654
Executive
Avionics Infrastructure
Navigation
Adv. Ballistics
Graphics Card
OpenGL Graphics Driver
May 1, 1998 9Copyright (c) 1998 Naval Air Warfare Center
Standards & Conformance
• National Body
• Company Proprietary
• Non-Standard
• Implementation
• Strict
• Conforming
• Conforming withextensions
• Non-conforming
Standards Conformance
May 1, 1998 10Copyright (c) 1998 Naval Air Warfare Center
Identify Interfaces
VxWorks Kernel
VxWorks BSP
1553 Driver
Backplane
DY-4 SVME-171
DY-4 D654
Executive
Avionics Infr.
Navigation
Adv. Ballistics
HUD/DDI
VxW
orks
Ker
nel
VxW
orks
BSP
1553
Dri
ver
Bac
kpla
ne
DY
-4 S
VM
E-1
71
DY
-4 D
654
Exe
cutiv
e
Avi
onic
s In
fr.
Nav
igat
ion
Adv
. Bal
listic
s
HU
D/D
DI
X
XX
X
X
X
X
X
X
X
X
X
X
X X
X
X
X X
X X XX
X
X
XX
XX
X
X X
X X
X
Gra
phic
s C
ard
Gra
phic
s D
rive
r
Graphics Card
Graphics Driver X
X
X
X
X
X X
X
X X
X
May 1, 1998 11Copyright (c) 1998 Naval Air Warfare Center
Identify Key Interfaces
VxWorks Kernel
VxWorks BSP
1553 Driver
Backplane
DY-4 SVME-171
DY-4 D654
Executive
Avionics Infr.
Navigation
Adv. Ballistics
HUD/DDI
VxW
orks
Ker
nel
VxW
orks
BSP
1553
Dri
ver
Bac
kpla
ne
DY
-4 S
VM
E-1
71
DY
-4 D
654
Avi
onic
s In
fr.
Nav
igat
ion
Adv
. Bal
listic
s
HU
D/D
DI
X(1)
X(4)
X(2) X(3)
X(5)
X
X(6)
X(7)
X(9)
X(10) X(11) X(12)
X(14)
X(13)
X(16) X(17)
X(19)E
xecu
tive
Gra
phic
s C
ard
Gra
phic
s D
rive
r
Graphics Card
Graphics Driver
X
X(8)
X(18)
X
X(15)
X
May 1, 1998 12Copyright (c) 1998 Naval Air Warfare Center
Key Open Standard Interfaces
VxWorks Kernel
VxWorks BSP
1553 Driver
Backplane
DY-4 SVME-171
DY-4 D654
Executive
Avionics Infr.
Navigation
Adv. Ballistics
HUD/DDI
VxW
orks
Ker
nel
VxW
orks
BSP
1553
Dri
ver
Bac
kpla
ne
DY
-4 S
VM
E-1
71
DY
-4 D
654
Avi
onic
s In
fr.
Nav
igat
ion
Adv
. Bal
listic
s
HU
D/D
DI
X(1)VME
POSIX POSIX
EABI
X
X(6)VME
MaxPack
X(10) X(11) X(12)
X(14)
X(13)
X(15) X(16)
X(18)E
xecu
tive
Gra
phic
s C
ard
Gra
phic
s D
rive
r
Graphics Card
Graphics Driver
OpenGL
X
VME
X(19)
X
X
May 1, 1998 13Copyright (c) 1998 Naval Air Warfare Center
The KOSI List
VxWorks Kernel - VxWorks BSP
VxWorks Kernel - 1553 Driver
VxWorks Kernel - OFP Executive
VxWorks BSP - Backplane
VxWorks BSP - DY-4 SVME-171
1553 Driver - Avionics Infrastructure
Backplane - DY-4 SVME-171
DY-4 SVME-171 - D654
OFP Executive - Avionics Infrastructure
KOSI Componenet Standard/Non-Standard Conformance Level Responsibility
OFP Executive - Navigation
OFP Executive - Advanced Ballistics
OFP Executive - HUD/DDI
1101.2 VME
EABI
Non-Standard
1101.2 VME
MaxPack
.h(implementation)
.h (implementation)
.h (implementation)
.h (implementation)
POSIX
POSIX
Non-Standard DY-4
DY-4
OSDI/DY-4
IEEE Strict
IEEE Strict
IEEE Strict
IEEE Strict
DY-4
????
DY-4
DY-4
OSDI
OSDI
OSDI
OSDI
ANSI Strict
X(1)
X(2)X(3)
X(5)
X(4)
X(7)
X(6)
X(9)
X(8)
X(10)
X(11)
X(12)
X(13)
Graphics Card - Backplane 1101.2 VME IEEE Strict Radstone
DY-4
Proprietary/Unknown
May 1, 1998 14Copyright (c) 1998 Naval Air Warfare Center
The KOSI List
Avionics Infrastructure - Navigation
Avionics Infrastructure - Adv. Ballist.
Navigation - Advanced Ballistics
Advanced Ballistics - HUD/DDI
KOSI Item Standard/Non-Standard Conformance Level Responsibility
BANav.h(impl.)
.h (implementation)
.h (implementation)
OpenGL
OSDI
OSDI
OSDI
RadstoneANSI Strict
Note: Header files are facades(a design pattern) that define critical software interfaces.
X(14)
X(15)
X(16)
X(17)
X(18)
X(19)
Avionics Infrastructure - Graphics Drv
Avionics Infrastructure - HUD/DDI .h (implementation)
OSDI
.h (implementation) OSDI
May 1, 1998 15Copyright (c) 1998 Naval Air Warfare Center
Benefits of KOSI Analysis
• Understand key interfaces & standards
• Non-conforming interfaces
• Standardization Vs. Optimization
• KOSI based product selection
• Valuable tool for system engineers
May 1, 1998 16Copyright (c) 1998 Naval Air Warfare Center
Benefits of KOSI Analysis
• Promotes technology insertion for increasedthroughput and memory requirements
• Reduced time-to-market
• KOSI based system is scalable, portable,interoperable, & plug & play compatible
• System kept “open” indefinitely
May 1, 1998 17Copyright (c) 1998 Naval Air Warfare Center
Recommendation #1
• Every new open system procured for the DoDshall have KOSI analysis as a SOWrequirement
• KOSI analysis shall be performed by a jointteam of prime, subs and DoD
• KOSI analysis shall be controlled andchanges tracked through the life of the system
May 1, 1998 18Copyright (c) 1998 Naval Air Warfare Center
OSDI Technical Architecture
Backplane COTS PPC Card COTS 1553 Card
Hardware
VxWorks BSP for Tornado 1.0.1
Hardware Dependent Software
Hardware Independent SoftwareOperational Flight Program
OpenGL Graphics Driver
VxWorks Wind Kernel for PPC
MIL-STD-1553 Driver
Graphics Card
May 1, 1998 19Copyright (c) 1998 Naval Air Warfare Center
Typical OS Technical Architecture
SystemInit/ResetBoot
BIT
I/O Bindings
Interrupts Timer 1553 VME Discretes
Extensions
RemoteProcedure
Call
MessagePassing
IPC
Operating System/Runtime Kernel
ProgramLanguageSupport Software
DevelopmentSupport
Open Systems API (OSAPI)
Hardware
May 1, 1998 20Copyright (c) 1998 Naval Air Warfare Center
Generic API Services
• System Initialization & Boot Loader
• Built-In Test (BIT)
• Device Drivers
– Interrupt
– Timers
– Backplane (VME)
– Legacy I/O (1553)
– High Speed I/O (Fibre Channel, PCI, SCI)
– Discrete I/O
– Bindings
• Operating system/Kernel
• Programming Language Runtime Support
• Software Development Interface
May 1, 1998 21Copyright (c) 1998 Naval Air Warfare Center
OSMC API - A Joint Venture
GDIS
Boeing
PMA-209
NAWCWPNS
Smith
Open Systems MissionComputer ApplicationProgramming InterfaceSpecification
OSMCAPI
May 1, 1998 22Copyright (c) 1998 Naval Air Warfare Center
Recommendation #2
• Joint Review of OSMC API
• Develop OSAPI Specification
• Encourage vendors to voluntarilyembrace OSAPI
• Validate COTS product conformanceto OSAPI
May 1, 1998 23Copyright (c) 1998 Naval Air Warfare Center
It Depends
Questions
May 1, 1998 24Copyright (c) 1998 Naval Air Warfare Center
top related