Which details do I need to provide for a new project that allows you to create a DataMiner SRM service definition? I heard about parameters, profiles, functions for both the inputs and outputs as well as the "inner" part of those buildings blocks you need to create first before everything can be connected together.
In my opinion, it's essential to understand the goals of the orchestration and the underlying infrastructure. With this understanding in place, it should be possible to design the functions based on the existing drivers or ensure that a new driver development will contain the needed parameters.
It's an iterative process that might require multiple revisions to achieve a desired level of functionality for the intended orchestration. As you mention, it's necessary to document functions, profiles, parameters, and the system's general behavior, so at different stages, we can use specific documents to capture the requirements of the Service Definition.