|Re: Reverse engineering a system [message #1818635 is a reply to message #1818390]
||Fri, 20 December 2019 20:42
| Stephane LACRAMPE
Registered: July 2009
You are right, I am not sure we have an actual video or tutorial showing how to use Capella and Arcadia in a reverse engineering example. For a methodological viewpoint, you can for sure use Arcadia in reverse engineering contexts, this is actually very often used in this situation. The Arcadia book from Jean Luc Voirin provides some methodological explanations on this, for instance on how to perform functional analysis in this case.
In Capella, nothing forces you to start by Operational analysis od System analysis, you can start by modeling your Physical Architecture for instance. So I don't see any problem with you starting to create physical components and function for your single sensor.
I am not sure exactly what you mean by "using it in a broader diagram". But let's say you have created an architecture diagram with your sensor, showing physical components, functions, and exchanges. you can still create new components in your diagrams, or create other diagrams where you can display other things and your single sensor as well. Maybe your question is about reusing your sensor model in other Capella projects/models. In that case, that would involve moving your sensor model into a Capella library, making it a REC, and then you can reuse it in other Capella projects/models.
But going back to doing reverse engineering with Capella: the typical use case would be that you have an existing system that you may want to modernize. So what you would do is start by reverse engineering it (physical architecture, physical functions....) but ideally, you would also reverse-engineer the needs, so System Analysis maybe. And from that, you would add the new systems functions at the SA level (this is what my modernized system needs to do now), and see how your reverse-engineered architecture may support the new functions, or how you need to evolve it.
While doing reverse-engineering of your system, you're discovering all your system components and functions. It is a good methodological habit to then spend some time grouping those components and functions in higher level (grouping) components and functions, enabling you to discover/reverse engineer the actual architecture of your system, making your inpact analysis much more efficient when adding new functions.
I hope that helps.
All the best,
Powered by FUDForum
. Page generated in 0.01714 seconds