Pros and Cons for a Parent Application Modeller

[drubiano]

Hi, When working with a bigger application (a ERP system such as SAP or something similar). What is the best practice when setting up the Application Modeller?

Some like to have a Basic Action object that contains the Application Modellerer. The rest of the objects then inherit that (Using "Share the Application Model of another object")

But what if the plan is to ramp up and have several developers using this application? Because right now, only a single developer can edit in the Application Modeller at a time. Is it better separate the Application Modeller for each window?

 

[veldew]

The best approach is to have a layered design architecture.
That way your application model won't explode, and you can manage your components and objects in a proper way and have excellent reusability.

 

[drubiano]

The best approach is to have a layered design architecture.
That way your application model won't explode, and you can manage your components and objects in a proper way and have excellent reusability.

So “Layered design” is one application modeller but in a structured way? The reusabillity I understand. But scaling up with several developers. How can we handle that issue?

 

[veldew]

No, Layered design exists of the Application modeller is 1 layer, then create objects and components both a layer, and on top your process/subprocesses also layers. Benefit is that each developer can work in his layer without disturbing the others.

https://info.symphonyhq.com/hubfs/RPABible.pdf