posix/aos delta document background • background: jsf, os-jtf, disa (ajpo), and usaf wright lab...
TRANSCRIPT
Curtis Royster, Jr.Curtis Royster, Jr.DISA, Center for StandardsDISA, Center for Standards
([email protected])([email protected])
Minerva RodriguezMinerva RodriguezRaytheon Systems CompanyRaytheon Systems Company
([email protected])([email protected])
POSIX/AOS Delta DocumentOpen 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)xx-xx-1998 to xx-xx-1998
4. TITLE AND SUBTITLEPOSIX/AOS Delta DocumentUnclassified
5a. CONTRACT NUMBER5b. GRANT NUMBER5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S)Royster, Jr., curtis ;Rodriguez, Minerva ;
5d. PROJECT NUMBER5e. TASK NUMBER5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME AND ADDRESSDISA, Center for Standardsxxxxxxxxxx, xxxxxxx
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 PAGES12
19. NAME OF RESPONSIBLE PERSONhttp://www.acq.osd.mil/osjtf/library/library_alpha.html,(blank)[email protected]
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
2
Background
• Background: JSF, OS-JTF, DISA (AJPO), andUSAF Wright Lab funded Hughes to evaluate anddetermine the suitability of the POSIX and AOSAPIs, and Ada 95 features for real-time embeddedsoftware
– Areas of Interest: availability, performance, security, andsupportability tradeoffs
– Provide a Delta Document comparing POSIX, AOS andAda 95 (1996 - 1997)
– Received Funding to pursue implementation of the DeltaDocument Findings (1998 )
• The Delta Document provides information neededto decide if POSIX is feasible in real-time militaryavionics?
3
The Delta Document Flow
Delta Document:•Req’t Desc.•API Evaluation•Comparison Matrix
•POSIX•Ada-95•AOS
API
POSIX W/G
OtherStudies
RTOS
SAERequirements
AdaBindings
DistributedCommunications
Standard
Updated Profiles
Revised Real-TimeStandard
Real-TimeAvionicsStandard
4
SAE-AS5 OS API WGRequirements
File Management Data Conversion Built-In TestBootup/Initialization/
ShutdownMemory ManagementProgram Support
CommunicationTask Control InstrumentationInput / Output Configuration Reinitialization
Fault ManagementData Security Timer ServicesSynchronization Non-Operational SupportSpecial Devices
5
API Comparison
FunctionalityFunctionality-
•17 Functional Areas•Based on fulfilling 75% of The Requirements in a Functional Area
RequirementsRequirements-
•277 Total Requirements•17 Functional Areas•Failed, Unknown, and Not Applicable Req’s not Counted As Fulfilled
P O S IX AOS A d a - 9 50
2
4
6
8
1 0
1 2
1 4
1 6
P O S IX AOS A d a - 9 5
A P I F u n c tio n a lity
P O S IX A O S A d a - 9 50 %
2 0 %
4 0 %
6 0 %
8 0 %
1 0 0 %
P O S IX A O S A d a - 9 5
R e q u ire m e n ts
6
Category 1: POSIX Meets TheRequirements
RequirementsRequirements:
•Synchronization•Task Control•Timer Services•File Management
Number of RequirementsNumber of Requirements:•60 Total Requirements
FindingsFindings:
POSIX: Minor Modifications needed to:•Synchronization•Task control•Timer Services•File Management
RecommendationsRecommendations:
•Present List of Minor Changes to POSIXReal-Time Working Group.Example: Semaphores as NotificationMechanism.
• Write PAR. Implement Changes into Real-Time Standard.
•Evaluate the Four POSIX Military ProfilesFor Avionics Feasibility.
POSIX A O S A d a - 9 50 %
2 0 %
4 0 %
6 0 %
8 0 %
1 0 0 %
POSIX A O S A d a - 9 5
P O S I X M e e ts R e q u i r e m e n ts
7
Category 2: POSIX NearlyMeets Requirements
RequirementsRequirements:
•Communication
Number of RequirementsNumber of Requirements:•59 Total Requirements
FindingsFindings:
•The POSIX Capability for themajority of Communication wasUnknown at the Time of TheEvaluation.
•NOTE: Need to review the POSIXDistributed CommunicationStandard
RecommendationsRecommendations:
•Compare Distributed Comm withDelta Document requirements
–Recommend The Implementation ofAda Bindings of Any RelevantRequirements.
POSIX AOS Ada-950%
20%
40%
60%
80%
100%
POSIX AOS Ada-95
POSIX Nearly Meets Requirements
8
Category 3: POSIX ShouldAddress
RequirementsRequirements:> Program Support > Data Security> Memory Mgmt > Input Output> Data Conversion > Fault Mgmt>Non-Operational Support
Number of RequirementsNumber of Requirements:•108 Total Requirements
FindingsFindings:
•Significant Deficiencies Found in:•Program Support•Data Security•Memory Management•Input Output•Data Conversion•Fault Management•Non-Operational Support
RecommendationRecommendation:
•Present The Missing Requirements toThe Real-Time Working Group.
•Get a Consensus on The NeededRequirements & Implement
•Migrate Any Requirements That havenot Been Agreed-on to Category 4.
P O S IX A O S A d a - 9 50 %
2 0 %
4 0 %
6 0 %
8 0 %
1 0 0 %
P O S IX A O S A d a - 9 5
P O S IX S h o u l d A d d r e s s
9
Category 4: POSIX Should NotAddress
RequirementsRequirements:•Special Devices > Configuration•Built-In Test > Instrumentation•Bootup / Initialization / Shutdown•Reinitialization
Number of RequirementsNumber of Requirements:•50 Total Requirements
FindingsFindings:
•Significant Deficiencies Found in:•Special Devices•Configuration•Built-In Test•Instrumentation•Bootup / Initialization / Shutdown•Reinitialization
RecommendationRecommendation:
•Present The Missing Requirements toThe Real-Time Working Group.
•Get a Consensus on TheRequirements.
•Ask JSF OSA to Define an API forAvionics Specific Requirements.
P O S IX A O S A d a - 9 50 %
2 0 %
4 0 %
6 0 %
8 0 %
1 0 0 %
P O S IX A O S A d a - 9 5
P O S I X S h o u l d N o t A d d r e s s
10
Ada’s Real Time Capabilities
(F-14)
(F-15)
(F-18)
Others (B-2)
(JSF)
Ada 83Ada 83
•Tasking•Exceptions
(F-22)
(Commanche)
Ada 95Ada 95
•Semaphores•Real-Time Services
OS Ada0%
20%40%60%80%
100%
OS Ada
Pre-Ada
OS Ada0%
20%40%60%80%
100%
OS Ada
Ada-83
OS Ada0%
20%40%60%80%
100%
OS Ada
Ada-95
11
The Trend in ApplicationProgramming I/Fs (API)
Ada + POSIXAda + POSIX•Real-Time Functionality Lacking in OS, POSIX, and Ada•Considerable Overlap in OS, POSIX, and Ada
Ada + POSIXAda + POSIX•High Order Functionality in Ada•General OS Functionality in POSIX•Hardware Specific Functionality in RTOS
POSIX RTOS HOL0%
20%
40%
60%
80%
100%
POSIX RTOS HOL
Past
POSIX RTOS Ada-950%
20%
40%
60%
80%
100%
POSIX RTOS Ada-95
Present
POSIX RTOS Ada-950%
20%
40%
60%
80%
100%
POSIX RTOS Ada-95
Future
12
FY98 Planned Tasks
• Task 1: Support The OSJTF Test Suite IndustryWide Certification Program.
» Beta Test
» Conformance Statement Questionnaire
• Task 2: Support POSIX Real-Time Standard.» Bring Delta Doc findings to RT System Services WG
» Write PARs and participate in WG
• Task 3: Update the Delta Document and provide toJSF.
» Update Delta Doc to include RT Distributed Communication
» Provide to JSF for DII/COE RT consideration