An experience-proven blueprint method for information systems
In this last section, I would like to explain a method I have been using to create blueprints of information systems evolution that I have been perfecting in the past few years with several industrial customers. There’s nothing special in there, nor particularly innovative, as it is just applying common sense to reach function targets... but it is formalized enough so that I can imagine you finding value in the description of the steps used.
The full method is quite elaborate and would need a dedicated book, so I will concentrate on a case that is precisely the subject of the chapter, namely dealing with time and technical debt. The example I’ll use will involve extracting a monolith software application ridden with technical debt but sadly used as the core of the customer company’s business (yes, a worst-case scenario). A multi-year planned blueprint had to be created to extract this dependency while...
