Tip: Keep ARXML files as small as possible.
In addition to reducing the risk of merge conflicts when files have less content, file comparison tools are more likely to provide correct line alignment of the XML content if files are small. One extreme would be to store e.g. each Service Interface in a separate file, while the opposite would be to use a monolith file to store the entire model. While some advantages of having many small files have been described in the section Separation of Responsibility, some disadvantages include the risk of someone adding content to the wrong file by mistake and inability to create file structure that is consistent with that of other tools in case those tools produce ARXML files of a coarser granularity. The granularity that is most suitable needs to be decided in each respective environment.