《IEEE-1516.3-2003.pdf》由会员分享，可在线阅读，更多相关《IEEE-1516.3-2003.pdf（41页珍藏版）》请在三一文库上搜索。
1、IEEE Std 1516.3-2003 IEEE Standards 1516.3 TM IEEE Recommended Practice for High Level Architecture (HLA) Federation Development and Execution Process (FEDEP) Published by The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA 23 April 2003 IEEE Compu
2、ter Society Sponsored by the Simulation Interoperability Standards Committee IEEE Standards Print: SH95088 PDF: SS95088 Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/20
3、07 03:17:31 MDTNo reproduction or networking permitted without license from IHS -,-,- The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2003 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 2
4、3 April 2003. Printed in the United States of America. IEEE is a registered trademarks in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Note: Attention is called
5、to the possibility that implementation of this standard may require use of subject mat- ter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for id
6、entifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELice
7、nsee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 03:17:31 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright 2003 IEEE. All rights reserved. iii Introduction This introduction is not part of IEEE Std 1516.3-2003, IEEE Recommended Practice for Hig
8、h Level Architecture (HLA) Federation Development and Execution Process (FEDEP). The High Level Architecture (HLA) has been designed to facilitate interoperability among simulations and to promote reuse of simulations and their components. The HLA is composed of three major components: HLA rules: A
9、set of ten basic rules that together describe the general principles defi ning the HLA. HLA interface specifi cation: A description of the functional interface between simulations (feder- ates) and the HLA runtime infrastructure (RTI). HLA Object Model Template (OMT): A specifi cation of the common
10、format and structure for docu- menting HLA object models. In an HLA application, any number of physically distributed simulation systems can be brought together into a unifi ed simulation environment to address the needs of new applications. These types of environments are known as HLA federations.
11、The HLA specifi cations together defi ne an overarching framework for the construction and execution of federations. Within the various government and commercial organizations that comprise the HLA community, many dif- ferent approaches to project management and systems engineering are being used. S
12、uch practices, proce- dures, and methodologies have evolved over time based on how well they serve the different functional areas and user communities for which they are intended. Many of these approaches currently use modeling and simulation (M however, strict adherence to the HLA specifi cations i
13、s not, by itself, suffi cient to ensure a fully consistent, interoperable distributed simulation environment. For instance, issues such as the need for consistent environmental data- bases and for consistent behavior representations of objects modeled by more than one federate are critical to achiev
14、ing interoperability; however, these types of issues cannot be fully addressed solely through adher- ence to the HLA specifi cations. Although some technical or managerial issues may be unique to a given application, many other issues associated with building and executing a fully interoperable HLA
15、federation are more general in nature. The HLA FEDEP is offered to the HLA community as a starting framework for identifying and addressing these more general issues, as discussed within the context of a full end-to-end process model for the development and execution of distributed simulation enviro
16、nments (federations) that fully conform with the HLA specifi cations. This framework can and should be tailored as appropriate to address the unique issues, requirements, and practical constraints of each individual application. It is expected that this framework will provide a viable foundation for
17、 all HLA applications and will assist the users in defi ning the specifi c tasks and activities necessary to support their particular needs. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not
18、 for Resale, 04/25/2007 03:17:31 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright 2003 IEEE. All rights reserved. v Participants At the time this recommended practice was completed, the working group had the following membership: Robert Lutz, Chair Reed Little, Vic
19、e Chair Katherine L. Morse, Secretary Kevin Alix Tobias Almn Matt Aylward Jane Bachman Mike Bachmann Cynthia Ballard Geoff Barbier William Beavin Brian Beebe Jeff Bergenthal Richard Bernstein Ronald Bertin Donna Blake Bob Bolling Jake Borah Steve Boswell Christina Bouwens Karsten Brathen Tom Brown C
20、arl Byers Chris Catotti Bob Chapman Anders Christensen Doug Clark Will Clayton Mark Crooks Rick Davenport Lloyd Dean Arif Dhanidina Vic DiRienzo Uwe Dobrindt Richard Dobson Ray Drake Tedd Dugone Gary England Jeffrey Farber John Fay Francis Feldpausch Jason Ferreira Frank Fiedrich Keith Ford Masa Fur
21、uichi Peter Gabrielsson Steve Galloway Allan R. Gettman Dave Gill Daniel Girardot Jean Graffagnini Allison Griffi n Paul Gustavson Hans-Peter Gustavsson Rdiger Gutte Furman Haddix Susan Harkrider David Hayward Jeremy Hendrix Jim Hollenbach Gilbert Hu Wim Huiskamp Jean-Louis Igarza Magnus Johnsson Mi
22、chel Keuning Erik de Koster Joe Lacetera John Langworthy Kaj Lehtovaara Arjan Lemmers Mike Lightner Staffan Lf Bjrn Lfstrand Franklin Lu Aykut Manioglu Ted Marz Anders Mattson Michael McAndrew Mark McCall Hans-Peter Menzler Jack Michalek Michael Myjak Eckehard Neugebauer Anna Niklasson Tommy Nordqvi
23、st Eileen ODonnell Peter Ohlander Gunnar hlund Jennifer Park John Pearson Colin Petford Mikel Petty Pascal Peyronnet Kay Pixius Vic Polkowski Jonathan Prescott Balajee Ramakrishnananda Richard Reading Godfrey Rhodes John Roberts Maria Rossi Chris Rougt Randy Saunders Judy Schandua Thomas Schmatz Aar
24、on Schwartzbard Roy Scrudder Rick Severinghaus Mike Shafto Steven Sheasby Carl Simchick Joseph Steel Allen Stotz Marcy Stutzman Robert Swift Simon Taylor Georgios Theodoropoulos W. H. Thomas Chris Turrell Hartmut Ufer Branislav Vakos Chin Keng Wai Bill Waite Jim Watkins Mike Whitehorn John Woodyard
25、Philomena Zimmerman Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 03:17:31 MDTNo reproduction or networking permitted without license from IHS -,-,- vi Copyright 2
26、003 IEEE. All rights reserved. The following members of the balloting committee voted on this recommended practice. Balloters may have voted for approval, disapproval, or abstention. When the IEEE-SA Standards Board approved this recommended practice on 20 March 2003, it had the following membership
27、: Don Wright, Chair Howard M. Frazier, Vice Chair Judith Gorman, Secretary *Member Emeritus Also included are the following nonvoting IEEE-SA Standards Board liaisons: Alan Cookson, NIST Representative Satish K. Aggarwal, NRC Representative Andrew Ickowicz IEEE Standards Project Editor Brian Beebe E
28、mmet Beeker Jeff Bergenthal Mitchell Bonnett Jake Borah Christina Bouwens Marco de Vos Dr. Guru Dutt Dhingra Uwe Dobrindt Ray Drake Dr. Sourav Dutta Brian Goldiez Ronald Hofer James Ivers Pi-Cheng Law Kaj Lehtovaara Reed Little Robert Lutz Faramarz Maghsoodlou Ted Marz Mark McAuliffe Katherine L. Mo
29、rse Diane Moss Tom Mullins Chris Rougt Randy Saunders Terry Schmidt Roy Scrudder Graham Shanks Steven Sheasby Donald Shillcutt Susan Solick William Tucker Guy Zimmer Philomena Zimmerman William Zimmerman H. Stephen Berger Joe Bruder Bob Davis Richard DeBlasio Julian Forster* Toshio Fukuda Arnold M.
30、Greenspan Raymond Hapeman Donald M. Heirman Laura Hitchcock Richard H. Hulett Anant Jain Lowell G. Johnson Joseph L. Koepfi nger* Tom McGean Steve Mills Daleep C. Mohla William J. Moylan Paul Nikolich Gary Robinson Malcolm V. Thaden Geoffrey O. Thompson Doug Topping Howard L. Wolfman Copyright The I
31、nstitute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 03:17:31 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright 2003 IEEE. All rights reserved. vii Con
32、tents 1.Overview 1 1.1 Scope 1 1.2 Purpose. 1 2.References 1 3.Definitions, abbreviations, and acronyms 2 3.1 Definitions 2 3.2 Abbreviations and acronyms 3 4.FEDEP model: top-level view. 3 5.FEDEP model: detailed view. 5 5.1 Step 1: Define federation objectives 7 5.2 Step 2: Perform conceptual anal
33、ysis10 5.3 Step 3: Design federation. 14 5.4 Step 4: Develop federation. 18 5.5 Step 5: Plan, integrate, and test federation. 23 5.6 Step 6: Execute federation and prepare outputs. 26 5.7 Step 7: Analyze data and evaluate results 29 6.Conclusion. 31 Annex A (informative) Bibliography . 32 Copyright
34、The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 03:17:31 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright The Institute of Electrical and El
35、ectronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 03:17:31 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright 2003 IEEE. All rights reserved. 1 IEEE Recommended Practice for High
36、 Level Architecture (HLA) Federation Development and Execution Process (FEDEP) 1. Overview 1.1 Scope This recommended practice defi nes the processes and procedures that should be followed by users of the High Level Architecture (HLA) to develop and execute federations. It is not intended to replace
37、 low-level management and systems engineering practices native to HLA user organizations, but is rather intended as a higher-level framework into which such practices can be integrated and tailored for specifi c uses. 1.2 Purpose The HLA has been designed to be applicable across a wide range of func
38、tional applications. The purpose of this architecture is to facilitate interoperability among simulations and promote reuse of simulations and their components. A named set of applications (e.g., simulations, loggers, viewers) interacting via the services of the HLA runtime infrastructure (RTI) in a
39、ccordance with a common rule set and a common HLA Object Model (OM) is known as an HLA federation . The purpose of this recommended practice is to describe a high-level pro- cess by which HLA federations can be developed and executed to meet the needs of a federation user or sponsor. It is expected
40、that the guidelines provided in this recommended practice are generally relevant to and can facilitate the development of most HLA federations. 2. References The three specifi cations that together compose the HLA provide the technical foundation for designing and developing all HLA federations. The
41、se specifi cations are described in the following documents: HLA IEEE 1516 version IEEE Std 1516-2000, IEEE Standard for Modeling and Simulation (M the federation manager; technologists; security analysts; verifi cation, validation, and accreditation (VV functional area experts; federation designers
42、; execution planners; federation integrators; federation operators; federate representatives; and data analysts. Some roles (e.g., operators) are unique to a single activity in the process, while others are more pervasive throughout the process (e.g., federation man- ager). Since the applicability o
43、f a given role (as well as the set of activities it spans) varies from application to application, the activities described in this recommended practice specify the roles of individuals only in generic terms. A major source of variation in how the seven-step process is implemented relates to the deg
44、ree of reuse of existing federation products. In some cases, no previous work may exist, therefore a thoroughly original fed- eration may need to be developed using a newly defi ned set of requirements to identify an appropriate set of federates and to build the full set of federation products neede
45、d to support an execution. In other cases, users of federations with established long-standing requirements will receive additional requirements. In this cir- cumstance, the federation users can choose to reuse previous work, either in part or whole, along with the products of new developmental acti
46、vities. In these situations, federation developers can often meet new user Corrective Actions / Iterative Development 6 5 431 Perform Conceptual Analysis 2 Analyze Data and Evaluate Results 7 Define Federation Objectives Design Federation Develop Federation Plan, Integrate, and Test Federation Execu
47、te Federation and Prepare Outputs Figure 1Federation development and execution process (FEDEP), top-level view Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/25/2007 03:17:
48、31 MDTNo reproduction or networking permitted without license from IHS -,-,- IEEE FEDERATION DEVELOPMENT AND EXECUTION PROCESS (FEDEP)Std 1516.3-2003 Copyright 2003 IEEE. All rights reserved. 5 requirements by reusing a subset of an established core set of federates and defi ning appropriate modifi ca- tions to other reusable federation products within their domain (e.g., FOM, planning documents). When an appropriate management structure exists to facilitate this type of federation development environment, sig- nifi cant savings can be achieved in