National Security Analysis Department HLA-E PDG Conform # 1 What is Conformance? u Specification of what it means when a piece of software claims to have.

Slides:



Advertisements
Similar presentations
Best Practices in Web Service Style, Data Binding and Validation (for use in Data-Centric Applications) David Meredith, Asif Akram, Rob Allan CCLRC Daresbury.
Advertisements

MCTS Guide to Microsoft Windows Server 2008 Network Infrastructure Configuration Chapter 6 Managing and Administering DNS in Windows Server 2008.
SIMWARE 4.X. Confidential 2 © NEXTEL AEROSPACE DEFENCE & SECURITY S.L., Reservados todos los derechos / All Rights Reserved 1. Capacities of SimWare.
Writing Quality Specifications July 9, 2004 Mark Skall Acting Director, Information Technology Laboratory National Institute of Standards and Technology.
Time Management in the High Level Architecture. Outline Overview of time management services Time constrained and time regulating federates Related object.
RTI: Federation Management Stephen c. Ulrich jr
Active Databases as Information Systems
Building Parallel Time-Constrained HLA Federates: A Case Study with the Parsec Parallel Simulation Language Winter Simulation Conference (WSC’98), Washington.
1 Software Testing and Quality Assurance Lecture 30 – Testing Systems.
IS 4420 Database Fundamentals Chapter 12: Data and Database Administration Leon Chen.
Configuration Management
1 Securing Network Resources Understanding NTFS Permissions Assigning NTFS Permissions Assigning Special Permissions Copying and Moving Files and Folders.
SCORM By: Akshay Kumar. SCORM 2 What we want? What is SCORM? What is SCORM? Connection with e-learning Connection with e-learning Application of XML Technology.
IHE-PCD , HL7 HC Dev WG, ISO/IEEE 11073, and NIST Medical Device Communication and IHE-PCD Cycle 4 Test Strategy IHE-PCD, HL7, ISO/IEEE Joint WG Meetings.
Working Group: Practical Policy Rainer Stotzka, Reagan Moore.
Profiling Metadata Specifications David Massart, EUN Budapest, Hungary – Nov. 2, 2009.
LXI Standard Evolution David Owen, Technical Committee Chair LXI Consortium Business Development Manager Pickering Interfaces
High Level Architecture Overview and Rules Thanks to: Dr. Judith Dahmann, and others from: Defense Modeling and Simulation Office phone: (703)
Scalable Systems Software Center Resource Management and Accounting Working Group Face-to-Face Meeting October 10-11, 2002.
Computer Science 340 Software Design & Testing UML Sequence Diagrams.
A Web-based Distributed Simulation System Christopher Taewan Ryu Computer Science Department California State University, Fullerton.
Software Testing and Quality Assurance Software Quality Assurance 1.
The High Level Architecture Introduction. Outline High Level Architecture (HLA): Background Rules Interface Specification –Overview –Class Based Subscription.
Parallel and Distributed Simulation Data Distribution I.
Parallel and Distributed Simulation Distributed Virtual Environments (DVE) & Software Introduction.
Framework of a Simulation Based Shop Floor Controller Using HLA Pramod Vijayakumar Systems and Industrial Engineering University of Arizona.
Data Distribution. Outline Fundamental concepts –Name space –Description expressions –Interest expressions Static Data Distribution: HLA Declaration Management.
High Level Architecture Time Management. Time management is a difficult subject There is no real time management in DIS (usually); things happen as packets.
© Drexel University Software Engineering Research Group (SERG) 1 The OASIS SOA Reference Model Brian Mitchell.
1 SISO SAC Report to IEEE CS SAB February 7, 2007 Vancouver, BC Katherine L. Morse, Ph.D., SAIC
Diistributed Data Management DDM in HLA. Distributed Data Management HLA by default does one sort of interest management: functional. Your federate can.
Doc.: IEEE /0841r0 Submission May 2011 Marc Emmelmann, Fraunhofer FOKUSSlide 1 Verification of TGai Requirements Date: Authors:
1 SAIC XMSF Update XMSF Workshop & MOVES Open House 4-5 August 2003 Katherine L. Morse, Ph.D., David L. Drake, Ryan.
2013 Spring Simulation Interoperability Workshop 13S-SIW-004 Extended FOM Module Merging Capabilities Bjo ̈ rn Mo ̈ ller Andy Bowers Mikael Karlsson Björn.
Fall ‘99 Simulation Interoperability Workshop RTI Interoperability Study Group Final Report Michael D. Myjak, Chair.
Eric Watz Lumir Research Institute, Inc
©MAK Technologies, Inc. The Dynamic-Link-Compatible C++ RTI API for IEEE 1516 Len Granowetter MÄK Technologies x121.
David Hatten Developer, UrbanCode 17 October 2013
to Help Meet Interoperability Standards for the
An Introduction to FOM Modules
Lesson 4: Configuring File and Share Access
STIX Interoperability
Requirements Analysis Scenes
Reuse of IEEE Content in Vendor Documentation
Chapter 8 – Software Testing
Sessions 1 & 3: Published Document Session Summary
Take Time to Obey the Rules
BOMs – Base Object Models
High Level Architecture
HMA SPS Mandatory I/F Development
Chapter 20 Additional Assurance Services: Other Information
User Interference Effect on Routing of Cognitive Radio Ad-Hoc Networks
Chapter 7: Designing the Architecture
Recall The Team Skills Analyzing the Problem (with 5 steps)
Chapter 20 Additional Assurance Services: Other Information
Event-Based Architecture Definition Language
Analysis models and design models
Software Connectors.
An Introduction to Software Architecture
HMA Follow On Task 4 - Order Final Presentation 21 June 2011
Reducing Service Debt via Accessible Procurement
REWARDS FOR INVOLVEMENT
Software interoperability in the NGN Service layer
High Level Architecture Module 2 Advanced Topics
Six Ways to Kill Interop
Chapter 7 Software Testing.
Overview of the recommendations on software updates
Tools to make the process safer : secured filing
Handling YANG Revisions – Discussion Kickoff
Proposed Changes for LB81 Comments
Presentation transcript:

National Security Analysis Department HLA-E PDG Conform # 1 What is Conformance? u Specification of what it means when a piece of software claims to have adopted the Standard. v vs “Compatible” which means the software doesn’t disrupt the simultaneous use of Standard conforming software. v vs “Compliant” which means the software has followed the direction of the Standard, according to it’s authors/vendor. v Why? u Adding a Conformance requirement to the Standards gives software producers defined criteria by which their compliance can be proven.

National Security Analysis Department HLA-E PDG Conform # 2 What is HLA Conformance? u There are many possible conformance requirements that the PDG could choose to incorporate into our Standards. A) Complete Implementation of all features. w Most work to build. w Least differentiated. w All vendors are selling the same thing. w Most interoperable B) Implementation tailored to profiles of use. w More diversity of RTI implementations. w Vendors more responsive to market. w Less interoperable u Today HLA has (B), but everybody claims we have (A). We must choose!

National Security Analysis Department HLA-E PDG Conform # 3 Suppose we want (A) u We write a conformance section that says conforming RTIs must implement every feature exactly according to the specs. u Verification tests that RTIs perform in this way. u RTIs are prohibited from having features which cause them to behave in a non- conforming way. ie.: v RID file settings to enable “connectionless” operation. (VTC/SAIC) v Settings to disable RTI features or permit the user to override RTI functions (M Ä K) v Just because I can’t think of a Pitch example doesn’t mean they are immune.

National Security Analysis Department HLA-E PDG Conform # 4 Suppose we want (B) u We agree on a scheme for identifying RTI subsets that are useful to our communities. u We write a conformance section that states when RTIs are permitted to have subset implementations. u We define how an RTI vendor makes claims about which subsets they implement. u Verification tests that RTIs act as they claim they act. u RTIs with several profiles can be tested several times to assure that each profile works.

National Security Analysis Department HLA-E PDG Conform # 5 Starting Proposal 1 of 2 Set NameFunctionalityStandard § ExecutionEstablish a federation execution and have federates join it § Fed SyncDefine sync points and achieve them § ; § 4.9 Save & RestoreRTI-managed simulation state save and restore operations § Object DeclarationIdentify and express interest in object classes and their attributes § & ; § 4.2 Interaction DeclarationIdentify and express interest in interaction classes and their parameters § & ; § 4.3 Object ManipulationCreate, update, and delete object instances and their attributes § , & ; § 4.4 Interaction ManipulationSend and receive interactions and their parameters § & 6.14; § 4.5 Ownership Management Allow attributes to be updated by federates other than their object instance creator under suitably controlled conditions § 7 Time MarkingAssociate a joined federate’s activities with the HLA time axis by assigning time stamps to the messages representing those activities. Timestamp parameter in the other feature sets. Time SynchronizationMaintenance of synchronized time across the federation and delivery of attributes and interactions within time constraints § 8; § 4.7 Data Distribution Management Selective distribution and reception of attributes and parameters through dynamic spaces § 9, , 10.17, ; § 4.6 Lookup OperationsTransformation of names to handles and handles to names § , & RTI Dynamic ControlsDynamically control the behavior of the RTI with respect to advisories, switches and callbacks § , , , , ; § 4.11 Management Object Model Visibility into the RTI internal representation of objects, interactions, federates, and state § 11

National Security Analysis Department HLA-E PDG Conform # 6 Starting Proposal 2 of 2

National Security Analysis Department HLA-E PDG Conform # 7 Path Ahead u Incorporate the Conformance section provided. u Expect comments to the next draft on both the feature sets identified and the rules expressed in the Conformance section.

National Security Analysis Department HLA-E PDG Conform # 8

HLA Evolved PDG Position Brief – Conformance Johns Hopkins University Applied Physics Laboratory National Security Analysis Department