This article provides basic work instructions for the ConOps module in Relatics 5, including how to create and manage user processes, define (end) users, and add related user stories and scenarios. It also explains how to retrieve and manage associated elements to ensure a clear operational understanding of system use.
Introduction
In this module, you can define and manage all operational aspects of system use, including user processes, (end) users, user stories, and usage scenarios. These elements help to clarify how the system will be used in practice. Relatics enables you to document this information in a structured way—capturing user needs, roles, goals, and interactions—providing a clear and shared understanding of system usage from a user perspective.
Objective
The goal is to ensure traceability and alignment between system design and actual user needs. Without a structured approach, user expectations often remain implicit or are only discussed informally, making it harder to validate whether the final system meets real-world demands. Proper documentation supports communication, validation, and alignment with stakeholders.
Solution
Relatics supports a structured ConOps (Concept of Operations) process. By registering user processes, defining roles and responsibilities, and linking user stories and scenarios, you create a clear operational context for system development. This helps bridge the gap between users and technical teams, ensures functional relevance, and supports verification and validation throughout the project lifecycle.
Need help getting started?
In addition to this article, we’re happy to offer further support in using the Conops 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.
