BS EN 16603-40-07:2020
$215.11
Space engineering. Simulation modelling platform
Published By | Publication Date | Number of Pages |
BSI | 2020 | 146 |
ECSS-E-ST-40-07 is a standard based on ECSS-E-ST-40 for the engineering of simulation software.
ECSS-E-ST-40-07 complements ECSS-E-ST-40 in being more specific to simulation software. Simulation software include both Simulation environments and simulation models. The standard enables the effective reuse of simulation models within and between space projects and their stakeholders. In particular, the standard supports model reuse across different simulation environments and exchange between different organizations and missions.
This standard can be used as an additional standard to ECSS-E-ST-40 providing the additional requirements which are specific to simulation software.
This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.
Applicability
This standard lays down requirements for simulation software including both Simulation environments and simulation models. The requirements cover simulation models’ interfaces and simulation environment interfaces for the purpose of model re-use and exchange to allow simulation models to be run in any conformant simulation environment.
A consequence of being compliant to this standard for a model is the possibility of being reused in several simulation facilities or even in several projects. However, adherence to this standard does not imply or guarantees model reusability, it is only a precondition. Other characteristics of the model, to be defined outside this standard, such as its functional interfaces and behaviour, its configuration data as well as quality, suitability and performance, etc. are also heavily affecting the potential for a model to be reused. In addition, agreements need to be reached on simulation environments compatibility, model validation status as well as legal issues and export control restrictions.
Therefore, this standard enables but does not mandate, impose nor guarantee successful model re-use and exchange.
Model reuse in this standard is meant both at source-code and binary level, with the latter restricted to a fixed platform.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
11 | 1 Scope |
12 | 2 Normative references |
13 | 3 Terms, definitions and abbreviated terms 3.1 Terms from other standards 3.2 Terms specific to the present standard |
18 | 3.3 Abbreviated terms 3.4 Nomenclature |
19 | 4 Principles 4.1 Objectives 4.2 Common Concepts and common types |
20 | 4.3 Architecture |
21 | 4.4 Time handling principle |
22 | 4.5 Simulation lifecycle |
23 | 4.6 Simulation method 4.6.1 Discrete-event simulation (DES) |
24 | 4.6.2 Parallelization and distribution 4.6.3 Inter component communication 4.6.3.1 Overview 4.6.3.2 Interface based communication 4.6.3.3 Data flow based communication |
25 | 4.6.3.4 Event Based communication 4.7 Models, Services and Components 4.7.1 Objects |
27 | 4.7.2 Components |
29 | 4.7.3 Factories 4.7.4 Models and Services |
30 | 4.8 Publication and Persistence |
31 | 4.9 Dynamic invocation |
33 | 4.10 Components meta data 4.10.1 Catalogue 4.10.2 Package |
34 | 4.10.3 Configuration 4.11 Model exchanges considerations 4.11.1 Overview 4.11.2 SMP Bundle |
35 | 5 Interface requirements 5.1 Common 5.1.1 Primitive Types specification |
37 | 5.1.2 Time Kinds |
38 | 5.1.3 Path string |
39 | 5.1.4 Universally Unique Identifiers (UUID) 5.1.5 Exception specification 5.2 Components and Objects interfaces 5.2.1 Object Specification (IObject) |
40 | 5.2.2 Collection Specification (ICollection) |
41 | 5.2.3 Component Specification 5.2.3.1 Component (IComponent) |
44 | 5.2.3.2 Model (IModel) 5.2.3.3 Service (IService) 5.2.3.4 Linking Component (ILinkingComponent) 5.2.4 Aggregation 5.2.4.1 Aggregation interface (IAggregate) |
45 | 5.2.4.2 Reference Interface (IReference) |
47 | 5.2.5 Composition 5.2.5.1 Composition interface (IComposite) 5.2.5.2 Container interface (IContainer) |
49 | 5.2.6 Events 5.2.6.1 Sink of events interface (IEventSink) |
50 | 5.2.6.2 Source of events interface (IEventSource) |
51 | 5.2.6.3 Consumer of events interface (IEventConsumer) 5.2.6.4 Provider of events interface (IEventProvider) |
52 | 5.2.7 Entry points 5.2.7.1 Entry points calling interface (IEntryPoint) 5.2.7.2 Entry Points publisher interface (IEntryPointPublisher) 5.2.8 Dynamic Invocation 5.2.8.1 Dynamic invocation interface (IDynamicInvocation) |
54 | 5.2.8.2 IRequest |
56 | 5.2.9 Persistence (IPersist) |
57 | 5.2.10 Failures 5.2.10.1 Failure interface (IFailure) 5.2.10.2 Model failure state interface (IFallibleModel) |
58 | 5.2.11 Field interfaces 5.2.11.1 ISimpleField |
59 | 5.2.11.2 IStructureField 5.2.11.3 IArrayField 5.2.11.4 ISimpleArrayField |
61 | 5.2.11.5 IField 5.2.11.6 IForcibleField |
62 | 5.2.11.7 IDataflowField |
64 | 5.2.12 Requirements on utilization of Simulation Environments interfaces by components 5.2.12.1 ILogger interface utilization 5.2.12.2 IPublication interface |
65 | 5.2.12.3 ISimulator interface 5.3 Simulation Environment interfaces 5.3.1 Logger (ILogger interface) |
67 | 5.3.2 Time Keeper (ITimeKeeper) |
69 | 5.3.3 Scheduler (IScheduler) |
77 | 5.3.4 Event Manager (IEventManager) |
81 | 5.3.5 Resolver (IResolver) |
82 | 5.3.6 Link Registry (ILinkRegistry) |
84 | 5.3.7 Simulator (ISimulator) |
96 | 5.3.8 Persistence 5.3.8.1 Storage Reader Interface (IStorageReader) |
97 | 5.3.8.2 Storage Writer Interface (IStorageWrite) 5.3.9 Publication 5.3.9.1 IPublication |
103 | 5.3.9.2 IPublishOperation |
104 | 5.3.10 Type Registry 5.3.10.1 ITypeRegistry |
107 | 5.3.10.2 IType |
108 | 5.3.10.3 IStructureType 5.3.10.4 IClassType |
109 | 5.3.10.5 IArrayType 5.3.10.6 IEnumerationType 5.3.11 Component Factory (IFactory) |
110 | 5.4 Meta data 5.4.1 Catalogue 5.4.1.1 File format specification 5.4.1.2 Validation rules |
113 | 5.4.1.3 Requirements on utilization of Catalogue |
114 | 5.4.2 Package 5.4.2.1 File format specification 5.4.2.2 Validation rules 5.4.3 Configuration data 5.4.3.1 File format 5.4.3.2 Validation rules |
115 | 6 Implementation mapping 6.1 Catalogue to C++ 6.1.1 Mapping templates |
118 | 6.1.2 Namespaces and files 6.1.3 Element and Type Visibility Kind |
119 | 6.1.4 Mapping of elements 6.1.4.1 Value elements 6.1.4.2 Constant 6.1.4.3 Field |
120 | 6.1.4.4 Association |
121 | 6.1.4.5 Parameter |
122 | 6.1.4.6 Property |
124 | 6.1.4.7 Operation |
127 | 6.1.4.8 EntryPoint 6.1.4.9 EventSink 6.1.4.10 EventSource |
128 | 6.1.4.11 Container 6.1.4.12 Reference 6.1.5 Basic Value Types 6.1.5.1 Common specification |
129 | 6.1.5.2 Enumeration 6.1.5.3 Integer 6.1.5.4 Float 6.1.5.5 String 6.1.5.6 Array |
130 | 6.1.6 Compound Value Types 6.1.6.1 Common specification 6.1.6.2 Structure 6.1.6.3 Class |
131 | 6.1.6.4 Exception |
132 | 6.1.7 Reference Types 6.1.7.1 Common specification 6.1.7.2 Interface |
133 | 6.1.7.3 Model |
134 | 6.1.7.4 Service |
135 | 6.2 Package to library 6.2.1 Mapping templates 6.2.2 Common to Unix and Windows |
136 | 6.2.3 Unix (Shared object) |
137 | 6.2.4 Addendum for Windows Dynamic Link Library (DLL) |
138 | 6.2.5 SMP Bundle |