I agree that the first important step is from drawing to modelling. Having a single model means that all your drawings are (and stay) consistent. The next step

I agree that the first important step is from drawing to modelling. Having a single model means that all your drawings are (and stay) consistent. The next step is the integration with the surroundings to keep the architecture model consistent with the code and the requirements. For the code, the usual way is generate code from the model. That is tricky and has a bad reputation because it is hard to get right. For requirements, the question is whether you actually track them (probably no in SaaS/Web environment; probably yes in embedded). What I'm not sure about: In theory the integration tests should be derived from the software architecture, but I have you to see even ideas for tool support there.