IEEE 1730-2010 en Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) (IEEE Computer Society)《分布式仿真工程和执行过程(DSEEP)的推荐实施规程》.pdf

《IEEE 1730-2010 en Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) (IEEE Computer Society)《分布式仿真工程和执行过程(DSEEP)的推荐实施规程》.pdf》由会员分享，可在线阅读，更多相关《IEEE 1730-2010 en Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) (IEEE Computer Society)《分布式仿真工程和执行过程(DSEEP)的推荐实施规程》.pdf（79页珍藏版）》请在麦多课文档分享上搜索。

1、g3g3g3IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) g3Sponsored by the Simulation Interoperability Standards Organization (SISO) g3IEEE 3 Park Avenue New York, NY 10016-5997 USA 24 January 2011 IEEE Computer Society IEEE Std 1730TM-2010(Revision ofIEE

2、E Std 1516.3-2003)IEEE Std 1730-2010 (Revision of IEEE Std 1516.3-2003) IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) Sponsor Simulation Interoperability Standards Organization (SISO) of the IEEE Computer Society Approved 30 September 2010 IEEE-SA Sta

3、ndards Board Approved 10 June 2011 American National Standards Institute Abstract: Recommended practice for Distributed Simulation Engineering and Execution Process (DSEEP) is described. The DSEEP is intended as a high-level process framework into which the lower-level systems engineering practices

4、native to any distributed simulation user can be easily integrated. Simulation architectures include Distributed Interactive Simulation (DIS), High Level Architecture (HLA), and Test and Training Enabling Architecture (TENA). Keywords: DIS, distributed simulation, engineering methodology, HLA, IEEE

5、1730, M +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. Introduction This introduction is not part of IEEE Std 1730-2010, IEEE Recommended Practice for Distributed Simulation Engin

6、eering and Execution Process (DSEEP). Modeling and simulation (M it is intended as a higher-level framework into which low-level management and systems engineering practices native to user organizations can be integrated and tailored for specific uses. 2. Definitions, acronyms, and abbreviations 2.1

7、 Definitions For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dictionary: Glossary of Terms responsible for certifying that a simulation environment has been verified and validated; and authorizes the use of the simulation environment for its intended

8、use. A major source of variation in how the seven-step process is implemented relates to the degree of reuse of existing products. In some cases, no previous work may exist; therefore a new simulation environment may need to be developed based on the defined requirements. In other cases, user commun

9、ities with established, persistent simulation environments will receive additional requirements. In this circumstance, the users can choose to reuse previous work (e.g., member applications, SDEMs, planning documents) either in part or whole, along with the products of new developmental activities.

10、When an appropriate management structure exists to facilitate this type of development environment, significant savings can be achieved in both cost and development time. The remainder of this document describes a structured, systems engineering approach to simulation environment development and exe

11、cution known as the Distributed Simulation Engineering and Execution Process (DSEEP). The seven-step process provides a top-level, process-flow view of the major steps of DSEEP. In the detailed product-flow view, each step is further decomposed into a set of interrelated lower-level activities and s

12、upporting information resources. Since the needs of distributed simulation users range from “first use” applications to experienced users, the DSEEP makes no assumptions about the existence of an established core set of member applications or the up-front availability of reusable products. Further,

13、there are no assumptions about the size of the simulation environment, as even users and developers of stand-alone (non-distributed) simulations can benefit from the guidance provided in this document. Although the intention is to define a comprehensive, generalized framework for the construction an

14、d execution of distributed simulation environments, it is important to recognize that users of this process model will normally need to adjust and modify the DSEEP as appropriate to address the unique requirements and constraints of their particular application area. 4. DSEEP: Detailed product flow

15、view The DSEEP describes a high-level framework for the development and execution of distributed simulation environments. The intent of the DSEEP is to specify a set of guidelines for the development and execution of these environments that stakeholders can leverage to achieve the needs of their app

16、lication. A detailed, product-flow view of the DSEEP is provided in Figure 2. This view illustrates the flow of information across the seven process steps identified in Figure 1. Data flow diagram notation is used in Figure 2 and throughout this document to represent activities (rounded rectangles),

17、 data stores (cylinders), and information flows and products (arrows) (see Scrudder et al. B1). 5 Copyright 2011 IEEE. All rights reserved. IEEE Std 1730-2010 IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) Define SimulationEnvironment Objectives1Perfor

18、m ConceptualAnalysis2Design SimulationEnvironment3Develop SimulationEnvironment4ExecuteSimulation 6Integrate & TestSimulation Environment 5Analyze Data andEvaluate Results 7Inf o onAvailable ResourcesProgramGoalsExistingDomain DescriptionsInitial Planning DocumentsObjectives StatementSimulation Envi

19、ronment RequirementsScenario(s)Conceptual ModelSimulation Environment Test CriteriaMember & SimEnvironmentDesignsDerived OutputsTestedSimulationEnvironmentExecution Environment DescriptionSimulationEnvironment AgreementsReusableProductsLessonsLearnedFinalReportExisting ScenariosAuthoritative DomainI

20、nf ormationExistingConceptualModelsData Dictionary ElementsExistingSimulation Data Exchange ModelsSupportingResourcesScenario InstancesSimulation Data Exchange ModelModified/NewMember ApplicationsSupporting DatabasesImplemented SimulationEnvironment InfrastructureMultiple Items:List of Selected (exi

21、sting) Member ApplicationsDetailed Planning DocumentsMemberApplicationDocumentationFigure 2 Distributed Simulation Engineering and Execution Process (DSEEP), detailed product flow view The following subclauses describe the lower-level activities associated with each of the seven major development an

22、d execution steps. A tabular view of the activities inherent to each major step is provided in Table 1. Activity descriptions and potential inputs and outputs for the activity and a representative list of recommended tasks are provided. Graphical illustrations of the interrelationships among the act

23、ivities within each step are also provided. Whenever outputs from one DSEEP activity represent a major input to one or more other activities, the arrow labels explicitly identify the activities that use these outputs. The arrow labels also identify the activities that produce inputs. However, there

24、is a presumption embodied within the DSEEP that once a DSEEP product has been created, it will be available for all subsequent activities, even though the product may not be identified as an input in the activity description. Additionally, once a product is developed, the product may be modified or

25、updated by subsequent activities without such modifications being explicitly identified either as a task or output. This is the natural cause and effect of iterative and incremental development, which is supported by the DSEEP. Input and output arrows without activity number labels are those in whic

26、h the information originates from outside or is used outside the scope of the DSEEP. 6 Copyright 2011 IEEE. All rights reserved. IEEE Std 1730-2010 IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) Table 1 Tabular view of the DSEEP Step (1) Define simulat

27、ion environ-ment objectives (2) Perform conceptual analysis (3) Design simulation environment (4) Develop simulation environment (5) Integrate and test simulation environment (6) Execute simulation (7) Analyze data and evaluate results Activities Identify user/ sponsor needs Develop objectives Condu

28、ct initial planning Develop scenario Develop conceptual model Develop simulation environment requirements Select member applications Design simulation environment Prepare detailed plan Develop simulation data exchange model Establish simulation environment agreements Implement member application des

29、igns Implement simulation environment infrastructure Plan execution Integrate simulation environment Test simulation environment Execute simulation Prepare simulation environment outputs Analyze data Evaluate and feedback results Although many of the activities represented in the DSEEP diagram and t

30、abular view appear highly sequential, the intention is not to suggest a strict waterfall approach to development and execution. Rather, this process illustration is simply intended to highlight the major activities that occur during development and execution and approximately when such activities ar

31、e first initiated relative to other development activities. In fact, experience has shown that many of the activities shown in Figure 2 as sequential are actually cyclic and/or concurrent, as was indicated earlier in Figure 1 via the dotted feedback arrows. In general, the lower level activities wil

32、l be conducted in the order implied by the information flow between these activities, but the actual timing of these activities is not absolute and is dependent upon the systems engineering practices actually being used. In addition to the DSEEP products, there are recommended simulation management

33、planning areas for which persistent documentation is key when using incremental development. A summarized list of these planning areas and resulting documents that are recommended follows: Development and execution planning. The resulting document from this activity identifies the overall plan of ac

34、tion and milestones for the simulation development and execution. There can be multiple views created to depict the schedule of activities, including detailed task and milestone identification for a particular simulation build. Verification and validation (V&V) planning. The resulting document from

35、this activity identifies the methodology and guidelines for verifying and validating the simulation environment. Test planning. The resulting document from this activity identifies the methodology and guidelines for executing and evaluating the simulation environment via a formal test. It should inc

36、lude the test criteria 7 Copyright 2011 IEEE. All rights reserved. IEEE Std 1730-2010 IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) imposed on the simulation environment as well as specific test requirements for participating member applications. Conf

37、iguration management planning. The resulting document from this activity identifies the methodology and guidelines for establishing and managing configuration baselines. It should indicate the process by which design changes to the simulation environment can be made and the version control utilized

38、by participating member applications. Security planning. The resulting document from this activity identifies the level of security imposed on the development and execution of the simulation environment. It should also identify the specific security requirements required by participating member appl

39、ications and possible designated approval authority required by participating member applications. Integration planning. The resulting document from this activity identifies the methodology and guidance for integration throughout the simulation development. Data management planning. The resulting do

40、cument from this activity identifies the strategy for data collection, management, and analysis of the simulation environment as well as the member applications. The plan information identified above may be captured in distinct documents or folded into other documents that are being mapped in the pr

41、ocess, and potentially stored in appropriate repositories. It should be noted that more than one individual may be required to populate and mature these documents as there may be specific program expertise or simulation expertise required. A suggestion for management of the planning documentation is

42、 to nominate individuals to maintain and update the documents on a periodic basis or as new information is obtained. Throughout the DSEEP, there will be areas in which additional information could provide useful guidance in the management, maintenance, and development of a simulation environment. Th

43、is information should be produced as required in a format that complements the documentation structure being used in the specific process implementation. The information can be captured in distinct documents or folded in to other documents that are being managed in the process. Areas in which additi

44、onal information may be captured include the following: Management tools. Identify what management tools have been selected to support the DSEEP activities (such as scenario development, requirements, conceptual analysis, VV&A, and configuration management) and how they are being utilized. Reusable

45、products. Identify the reusable products that have been produced or consumed in the DSEEP activities, such as designs, specifications, source code, documentation, test suites, manuals, procedures, etc. Simulation environment support tools. Identify what support tools have been selected for the simul

46、ation environment (such as data reduction tools, visualization, and simulation environment manager) and how those tools are being utilized in the simulation environment. Users of the DSEEP should be aware that the activities described in this document, while being generally applicable to most simula

47、tion environments, are intended to be tailored to meet the needs of each individual application. For example, DSEEP users should not feel constrained by the products explicitly identified in this document, but rather should produce whatever additional documentation is necessary to support their appl

48、ication. Specific tailorings of the DSEEP based on the native systems engineering processes inherent to certain widely-used distributed simulation architectures Distributed Interactive Simulation (DIS), High Level Architecture (HLA), and Test and Training Enabling Architecture (TENA) are included as

49、 annexes to this document. In general, the recommended practices provided in this document should be used as a starting point for developing the most appropriate approach to development and execution for the intended application. 8 Copyright 2011 IEEE. All rights reserved. IEEE Std 1730-2010 IEEE Recommended Practice for Distributed Simulation Engineering and Execution Process (DSEEP) In the subclauses that follow, the description of activities for each DSEEP step is provided and includes a supporting data flow diagram. Each data flow diagram identifies at least one indivi