January 19th, 2009
mail from Alan Paull
We are currently working on the Archimate and systems thinking stuff.
The Archimate work is proving very interesting.Â As the current system
is paper-based, we have no actual Enterprise Architecture type
structures (no ICT), which means the COVARM-in-Archimate will be
business layer only.Â We will have some comments on the COVARM model as
it stands, having discovered one or two dangling threads!
I would like to make a note here about complexity and the purpose of our
process modelling.Â The COVARM model of MMU processes is complicated and
reflects their complex nature.Â The purpose of the COVARM model was to
enable the project team to analyse the processes alongside processes at
other institutions in order to create a generic course validation model,
so it is not very accessible to other audiences.Â On the other hand our
purposes are four, I believe, at the moment:
(1)Â Â Â To gain an understanding of the whole process, with a view to …
(2)Â Â Â Presenting potential interventions (ICT tools and process
improvements) to a wide audience and …
(3)Â Â Â Modifying these in the light of comments and experience, and
(4)Â Â Â Recording the changed processes, with the engagement of the
community in the maintenance of the models.
This means that the parameters of our models might be these:
The viewpoints need to cover the concepts relating to the HEI staff
practitioners, those involved in the processes, rather than from the
viewpoint of application developers.Â Viewpoint from employer would also
Understanding of the current processes, indication of intervention
points and presentation of any new or revised processes will mean the
focus is probably not as fine-detailed as the COVARM version.
Concentration should be on the main flow of processes, with only a
passing mention of exceptions or alternative flows.
The models will be iterative and therefore subject to change as we
receive stakeholder comments.
We will keep a clear split between our ‘as is’ model and our ‘to be’
The model will not provide all the answers!Â I think this is important.
Witness that the COVARM model does not include a lot of highly pertinent
information, for example the extent and nature of the documentation
referred to, which will colour perceptions of those actually involved in
doing the processes.