SFS Suomen Standardit

 

The purpose of this standard is to specify the Systems Modeling Application Programming Interface (API) and Services that provide standard services to access, navigate, and operate on KerML-based models [KerML], and, in particular, SysML models [SysML]. The standard services facilitate interoperability both across SysML modeling environments and between SysML modeling environments and other engineering tools and enterprise services.

 

The Systems Modeling API and Services specifies the types and details of the requests that can be made and responses that can be received by software applications that are consuming the services to software applications that are providing the services.

 

The Systems Modeling API and Services specification includes the Platform Independent Model (PIM) - see Clause 7- and two Platform Specific Models (PSMs) - see Clause 8 : REST/HTTP PSM and OSLC PSM.

 

The purpose of this standard is to specify the Systems Modeling Language™ (SysML), to guide the implementation of conformant modeling tools, and to provide the basis for the development of material and other resources to train users in the application of SysML.

 

SysML is a general-purpose modeling language for modeling systems that is intended to facilitate a model-based systems engineering (MBSE) approach to engineer systems. It provides the capability to create and visualize models that represent many different aspects of a system. This includes representing the requirements, structure, and behavior of the system, and the specification of analysis cases and verification cases used to analyze and verify the system. The language is intended to support multiple systems engineering methods and practices. The specific methods and practices may impose additional constraints on how the language is used.

 

SysML is defined as an extension of the Kernel Modeling Language (KerML), which provides a common, domain independent language for building semantically rich and interoperable modeling languages. SysML also provides a capability to provide further language extensions. It is anticipated that SysML will be customized using this language extension mechanism to model more specialized domain-specific applications, such as automotive, aerospace, healthcare, and information systems, as well as discipline specific extensions such as safety and reliability.

 

Note. Definitions of system and systems engineering can be found in ISO/IEC 15288 Systems and Software Engineering – System Life Cycle Process.

 

The Structured Patterns Metamodel Standard (SPMS) specification defines a common standard for the definition and description of patterns as used in architecting, designing, and implementing software systems, working with software faults or security issues, and any situation where a pattern is appropriately applied.

 

SPMS has three main goals:

1) Sharing of pattern definitions in repositories or catalogs, including human-oriented specifications and machine oriented formalisms for automated tool use.

2) Sharing of pattern instances – indicators of the existence of a pattern within a model – regardless of how that pattern was determined, with traceability back to the methodology, and traceability to the model artifacts that prove its existence. if applicable. These instances may come from manual assertion, or from the results of an automated tool.

3) A visual representation for pattern instances that augments existing modeling representations and supports both automated production of graphical diagrams, and informal “line and box” style human-generated sketching.

 

The first goal is supported by the Definitions package, which defines a metamodel for defining and storing pattern specifications, suitable for use in tooling and repositories.

 

The second goal is supported by the Observations package, which defines a metamodel for pattern instances. The classes defined here offer support for both human-oriented use cases (consulting, investigation, education) and machine oriented use cases (automated analysis tools, automated results analysis, etc.).

 

Both goals are further supported by the Relationships package, which augments the Definitions package with metadata appropriate for a repository or catalog of patterns. This metadata offers a set of semantic relationships between pattern definitions and instances, enhancing searchability and other use cases appropriate to the domain. Again, both human oriented and machine-oriented use cases are supported in this package.

 

The Formalisms package supports the first goal more thoroughly for automated tool use cases and research purposes. It provides a mechanism for linking to a variety of formal metamodels such as Object Constraint Language (OCL), Knowledge Domain Metamodel (KDM), Abstract Syntax Tree Metamodel (ASTM), or Pattern Hierarchical Object Relation Metamodel Language (PHORML), depending on the needs of the modeler and community.

 

The third goal is supported by the Pattern Instance Notation (PIN) metamodel, which defines a common metamodel for the graphical depiction of pattern instances. It relies on the abstractions defined in SPMS. PIN and the corresponding elements in SPMS are equivalent in their expressive power, and have a one-to-one coherence of features.

 

PIN was developed hand in hand with the Patterns package of SPMS and provides a simple and human-oriented approach for quickly depicting instances of patterns, how they work in concert, and how they are expressed in an implementation or further design document. Most notably, PIN can be used entirely by itself to illustrate pattern interactions independent of an implementation, or used as an annotation with the variety of other graphical notations, such as UML diagrams. 

 

This document specifies a method for the enumeration of the characteristic microorganisms Lactobacillus delbrueckii subsp. bulgaricus (in short: L. bulgaricus) and Streptococcus thermophilus (in short: S. thermophilus) by means of the colony-count technique. The method is applicable to yoghurts (for the definition see CXS 243-2003). The colony-count technique (pour plates) is suitable for, but not limited to, the enumeration of L. bulgaricus and S. thermophilus in test samples with a minimum of 10 colonies counted on a plate. This corresponds to a level of the characteristic microorganisms L. bulgaricus and S. thermophilus that is expected to be higher than 100 cfu/g. The colony-count technique (spread plates) is suitable for, but not limited to, the enumeration of L. bulgaricus and S. thermophilus in test samples with a minimum of 10 colonies counted on a plate. This corresponds to a level of the characteristic microorganisms L. bulgaricus and S. thermophilus that is expected to be higher than 1 000 cfu/g.

 

This document provides terminology, concepts, requirements, and guidance for humanoversight of AI systems. It is primarily intended for organizations placing on the market or putting into service AI systems and is not specific to any particular sector;

 

This document describes an analytical procedure for the determination of platinum in platinum alloys with a nominal content up to 990 ‰ (parts per thousand), including alloys according to ISO 9202.

 

This document describes an analytical procedure for the determination of palladium in palladium alloys with a nominal content up to 990 ? (parts per thousand), including alloys according to ISO 9202.

 

 

 

This document specifies safety requirements and test methods for bathing aids intended to be used in a domestic bathtub or washbasin and to elevated shower aids. This document does not cover bathing aids designed for children with special needs. Bathing aids that are intended to be used only in conjunction with a child’s bathtub are not covered by this standard. NOTE 1 Bathing aids that are intended to be used only in conjunction with a child’s bathtub are covered in prEN 17072:2026, Child care articles — Bath tubs, stands and non-standalone bathing aids — Safety requirements and test methods. NOTE 2 Where the product has several functions or can be converted into another function, it is due to comply with relevant standard(s).

 

This document specifies safety requirements and test methods for children’s bath tubs and stands and for bathing aid accessories that are designed and intended to be used only in conjunction with a children’s bath tub. This document does not cover children’s bath tubs and stands and bathing aid accessories designed for children with special needs. NOTE 1 Bathing aids are covered in EN 17022. NOTE 2 Where the product has several functions or can be converted into another function it is due to comply with relevant standard(s).

 

This European Standard specifies performance requirements, validation methods and provides general instructions on the use of diffusive samplers for the determination of the concentration of gases in ambient air. This standard applies to all stages of the measuring procedure, including preparation, deployment, transportation and storage. It includes general principles applicable to diffusive sampling and analysis. It enables manufacturers and users to adopt a consistent approach to sampler validation and provides a framework for the assessment of sampler performance.

 

 

RISC-V (pronounced “risk-five”) is a new instruction-set architecture (ISA) that was originally designed to support computer architecture research and education, but which we now hope will also become a standard free and open architecture for industry implementations. Our goals in defining RISC-V include:

 

• Acompletely open ISA that is freely available to academia and industry. • Areal ISA suitable for direct native hardware implementation, not just simulation or binary translation.

• An ISA that avoids “over-architecting” for a particular microarchitecture style (e.g., mi crocoded, in-order, decoupled, out-of-order) or implementation technology (e.g., full-custom, ASIC, FPGA), but which allows efficient implementation in any of these.

• An ISA separated into a small base integer ISA, usable by itself as a base for customized accelerators or for educational purposes, and optional standard extensions, to support general purpose software development.

• Support for the revised 2008 IEEE-754 floating-point standard [5]. • An ISA supporting extensive ISA extensions and specialized variants. • Both 32-bit and 64-bit address space variants for applications, operating system kernels, and hardware implementations.

• An ISA with support for highly-parallel multicore or manycore implementations, including heterogeneous multiprocessors.

• Optional variable-length instructions to both expand available instruction encoding space and to support an optional dense instruction encoding for improved performance, static code size, and energy efficiency.

• An ISA that simplifies experiments with new privileged architecture designs.

 

The RISC-V ISA is defined avoiding implementation details as much as possible (although com mentary is included on implementation-driven decisions) and should be read as the software-visible interface to a wide variety of implementations rather than as the design of a particular hardware artifact. The RISC-V manual is structured in two volumes. This volume covers the design of the base unprivileged instructions, including optional unprivileged ISA extensions. Unprivileged instructions are those that are generally usable in all privilege modes in all privileged architectures, though behavior might vary depending on privilege mode and privilege architecture. The second volume provides the design of the first (“classic”) privileged architecture. The manuals use IEC 80000-13:2008 conventions, with a byte of 8 bits.

 

 

This document describes the RISC-V privileged architecture, which covers all aspects of RISC V systems beyond the unprivileged ISA, including privileged instructions as well as additional functionality required for running operating systems and attaching external devices.

 

This document establishes minimum performance, classification, and labelling requirements for gloves worn by operators and re-entry workers handling pesticide products to protect the hands or hands and forearms against contact with those products. Gloves covered by this document include gloves made with elastomeric and polymeric materials in the areas that provide protection. This document does not address protection against fumigants. This document needs to be used in conjunction with ISO 21420.

 

This document provides a temporal management reference model for feature-based software and systems product line engineering (feature-based PLE) as defined in ISO/IEC 26580:2021, expanding on the basic configuration management operations, tasks, and methods specified there. Because a PLE factory in ISO/IEC 26580 aggregates shared assets across multiple lifecycle stages and tools, such as requirements, models, source code, mechanical design, electrical design, documentation, test cases, calibration data, and so forth, the version management capabilities of the different lifecycle disciplines, as well as the feature catalogue and bill-of-features portfolio, need to be integrated into a holistic solution. We refer to this integrated PLE factory solution as Temporal Management (TM). As the name implies, the scope of temporal management is product line variation in time, in the context of feature-based PLE as prescribed in ISO/IEC 26580. The reference model for temporal management specifies an alignment-of-systems, where the temporal management system is an aggregation of the constituent version management systems for each of the individual elements in a PLE factory, including shared assets across all lifecycle stages, the feature catalogue, and the bills-of-features. Version management for each of the individual elements in the PLE factory is handled by the version management tools and methods associated with each of the elements, which are elaborated elsewhere and not repeated in this document.[2][3][4][5][6][7][8][10][11] Appendix A provides harmonization with this document and these representative version management methods, in the context of broader systems and software configuration management standards. Organizations may incorporate an overall temporal management approach for their temporal management solution that best matches their engineering processes, such as ASME Y14.35[5] and ASME Y14.100[6] for organizations primarily focused on mechanical engineering processes or IEEE Std 828[4] for organizations primarily focused on systems and software engineering processes. The intended audience for this document comprises: — technology providers who wish to provide temporal management for their feature-based PLE factory; — champions within an organization who wish to introduce feature-based PLE into their organization; — IT staff within a PLE organization who introduce and maintain the necessary technology to support temporal management in feature-based PLE; — practitioner stakeholders who use the temporal management tools and methods to practice feature-based PLE; — technical and business managers who sponsor and direct the methods necessary to practice temporal management in feature-based PLE; — university professors, researchers, corporate trainers, and other educators who create and share pedagogical materials and benefits regarding temporal management in feature-based PLE.

 

This document specifies the “as-built” data used for demonstrating completion of the build process and conformity of the product to type design. This document defines the minimum set of information to be archived to serve as a complete representation of an organization’s as-built data.

 

This document specifies the characteristics of tab washers for flight control rods. These tab washers are intended to immobilise the rod end in relation to the rod body, whilst allowing a positional adjustment of 1/2 a turn.

 

This document establishes the basis for testing and classifying free-standing safes, safe plinths, built-in safes (floor and wall), ATM safes and ATM bases, strongroom doors and strongrooms (with or without a door) according to their burglary resistance. This document does not cover testing and classifying Deposit Systems and ATM systems.