Hi,
I am designing a product which needs to be scalable. The design is broken down into elements that are unique and others that are used multiple time and form a subsystem. I need to scale the design by specifying how many subsystems are present and handle the function/Component/Behavior interaction appropriately in the block diagrams and during transfer across the analysis and architectures levels.
Some of the unique elements interacting with the subsystems will need to be modified in order to support the intended number of subsystems.
Each subsystem is allocated one “Physical User”.
I have tried using REC and RPL at the Physical Architecture level and was able to get some success, but as soon as I need to make changes to the upper Architecture or Analysis levels and propagate the changes back to the Physical Architecture level, things started getting messy and I have lost design cohesion.
I have been experimenting with the use of the REC and RPL functions at the “System Analysis” level after I had already made some work at the lower Architecture levels. I yet again found myself in a corner trying to transfer functions across the different level of architectures and fix the “Realized Function” issues or lack of.
If I use REP/RPL at the “Physical Architecture” level, I don’t think I will be able to have all the functions realized, ultimately making the use of the “Validation Model” useless.
I know I have made a few operation errors during the elaboration of this Capella project, but I am sure I would be able to sort things out, given time.
In the meantime, I would like to know what would have been the proper approach to the elaboration of the project.
At which level do I need to introduce the concept of scalability so that it can be implemented at the right Analysis or Architecture level? As far as I understand, this has to be described at the “Operational Analysis” level, if so, how can I describe the need and how should it be implemented?
Regards,