Model Coproduction with Prolaborate

By Matthew Thomas System Design Architect | Paul Lynham President of the Institution of Analysts and Programmers

Unshackle your organization from deep cultural reservations about putting your EA models (and your IP) in the Cloud, by taking this novel approach to model coproduction with your clients and suppliers. Prove the benefits, overcome the barriers!

Session Recording

Downloads

Model Coproduction With Prolaborate (PPTX)

Questions and Answers

In my last experience in a Bank, the COLABORATION in devoloping or, even. tuning a MODEL was jeopardised by the very small expertise in reading and interpreting MODELS, with the uderlying nrequired knowledge of UML and BPM standards; do you experiment the same ? how do you solve this gap ?

The key thing here is in having a standard set of artefacts that are pertinent to the different stakeholder concerns, and our standard (TOGAF-based) architecture repository provides a framework for addressing this concern. If you'd like to know more, please see www.architrace.co.uk where we can be contacted to discuss this in more detail

What attributes/tagged values are you using to actually approve proposed architectural changes after all collaborations done? And on what level? is it per element/connector? or some bigger blocks, like whole set of changes?

If I correctly understand the question, it relates to Prolaborate. In Prolaborate, there is considerable customisation allowed. Regarding gap analysis back in the architecture repository, the gaps are per element / connector and wrapped up under and across entirely different states of the architecture. If you'd like to know more, please see www.architrace.co.uk where we can be contacted to discuss this in more detail.

After you publish your "proposed" architecture transformation bits, there probably some collaboration between architects and stakeholders should take place. After all discussions settled, and required changes made, who and how verifies that proposed transformation should be implemented as it now is? Is it an architect who is changing state element-by-element? Or is it a stakeholder responsible for the agreed-upon bit of architecture doing it for elements he responsible of?

This is a process / RACI question. We do not mandate a particular process / RACI but can advise on one to suit you. The Coproduction workspace and building block / gap analysis approach overlay any process / RACI. No strong interdependency i.e. it will fit how you work. Any further queries, please see https://architrace.co.uk

Could you outline the benefits, in a way that I can explain it to the team I'm with at the moment?

The main point : you can collaborate WITHIN your organisation and get the knowledge capital that is there, or you can collaborate BEYOND your organisation to get the input of suppliers, clients, user focus groups - even the public. If you do only the former, and you’re needing to interwork with your supply chain, the following opportunities are not as fully accessible: agreement over the art of the possible; rounded evaluation of options; direct consideration of user experience; commitment by all parties to the joint vision.

Speakers Bio

Matthew Thomas

System Design Architect

Enterprise Architecture framework and modelling consultant, ready to listen to your EA pain points

Paul Lynham

President of the Institution of Analysts and Programmers

President and Fellow of the Institution of Analysts and Programmers, whose vision is to improve software for society