I’ve just been following a fascinating discussion on the IIBA (Business Analysts) Linked in Group. One BA asked the group for advice on System Migration – to be met with a wealth of experience / advice from capable people who have struggled with this sensitive process over the years. So much so that many BA’s think they should simply stay clear – leave it to the DBA or coders. What a shame! The BA is the ideal role to take their understanding of System / Service Requirements and take them to conclusion – completed / running services. So how to achieve this?
XPOR is built for the BA to create business / system models (objects and associations) from which everything follows! BA’s already know this but are generally stuck with having to use other skillsets to expose and present the data and function required. Not with XPOR. A non-technical person can build the whole thing.
This only (!) leaves the importing of legacy data into this new system. Often that might be an old spreadsheet, or a simple database, right through to an old custom ERP! But the BA understands the system model – the structure of the organisations processes and higher level purpose. So the first problem is to (export) and understand that old data. Most BA’s would understand the simple CSV,TXT structure. Better still, XML or json. This data, and its’ fields, describes the objects taken from the old system. Now, with XPOR, you simply import them into a container, which will create all of the new objects. Then, using XFLOW, relocate / connect them to other relevant object in your new system. All legacy data imported, validated and re-connected - No Developer Required!