This article provides basic work instructions for the Systems (SBS) module in Relatics 5, including how to create and manage physical objects, define their hierarchy and types, and link them to related elements such as functions, requirements, and actions.
Introduction
In this module, you can define and manage all physical objects relevant to the project. These objects represent the tangible components of the system and often serve as the foundation for structuring requirements, defining functions, and understanding the system’s architecture. Relatics enables you to document each object in a structured way—capturing its identity, hierarchy, type, and relationships with other elements—ensuring clarity and consistency throughout the project.
Objective
The aim is to ensure complete traceability and a clear understanding of all physical objects within the project or system. Without a structured breakdown and proper relationship mapping, it becomes difficult to manage complexity, align system design with functional needs, or verify whether all stakeholder requirements are addressed. Well-defined objects improve integration between design, requirements, and system behavior.
Solution
Relatics supports a structured approach to managing physical objects. By registering objects in this module, assigning types, organizing them hierarchically, and linking them to related elements—such as functions, actions, and requirements—you create a transparent and verifiable object model. This strengthens system understanding, enhances traceability, and supports a controlled and well-aligned system development process.
Need help getting started?
In addition to this article, we’re happy to offer further support in using the Systems (SBS) module. We can also provide a Relatics training tailored to your project or team. Simply leave your phone number in the ‘Get in Touch’ form below, and we’ll contact you shortly.
