The Governance Architect
At one stage I was exploring moving the Detroubulator into the ABAP stack and provided a design to do this. The following link shows you how I approached that which apart from screen design, covers most of the steps discussed in this blog to a degree.h3. Final Sell Point Firstly, doing a high-level design like above is great for:
- Being able to reuse and enhance your existing code base if it's all within the same UML repository.
- It saves you time for any non-trivial development.
How often have you come across genius introverted developers that can do anything but when you look at how they did it; you realise that very few people in the world will understand the concepts used and basically, they've just developed an unsupportable application.
So secondly, if you are in a governed world; it's important to understand what the GA is looking to approve. The description that has worked best for me is that the design needs to be written in such a way that you are happy to give this to another developer to develop and know that for the most part; the design will deliver the required solution (the developer still needs to design parts of the solution, but the design decisions should be more trivial and not require GA approval).
For me, from a GA perspective, the above approach gives me a design that I can easily understand and approve. Alternatively, from a developer perspective, I use this approach personally and can really say that it's incredible how much better the solutions are when you approach it this way.
