Sealark Solutions

For analysts used to capturing requirements primarily in text and supported by ad hoc diagrams created using tools such as Visio switching to using a modelling tool and building models (as opposed to creating drawings) to articulate requirements is a paradim shift.  SLS has a lot of experience in helping analysts and managers make the transition and some golden rules that ease the transition are as follows:

• Use a common industry standard notation (UML, BPMN, Archimate, ...) appropriate to what is being modelled.
• Pick a tool that has the following key characteristics:

1. supports the desired notation as per the specification
2. has a highly intuitive GUI for the analysts creating the diagrams and linking them to form models
3. can demonstrate support for industry standards for importing and exporting models
4. has an easy to use capability to create and generate reports
5. has an easy to use capability to export the models onto a internet or intranet site.

• Build up experience doing project modelling before moving to enterprise modelling.
• Draft an initial, simple, method that includes the following:

1. the subset of the selected notation that will be used
2. how the selected subset of notation will be used in the tool i.e. what it will represent
3. the protocol for creating content in the model repository which includes naming of objects, describing objects, how objects are grouped and how diagrams are used.
4. Use three models: Conceptual, Logical and Physical (Not all models may be needed e.g. if COTS no Physical, if bespoke Agile development maybe no Logical)
5. Capture three key views: Process, Data and Technology
6. Non functional requirements are captured and mapped as appropriate to define the quality, performance, etc. that the modelled systems must acheive.

• Have experienced modellers embedded in teams mentoring the analysts making the transition to modelling.
• Promote consistent modelling across all analysts.
• Update the method in line with modelling experience and as modelling maturity improves
• Merge models to form an architectural model when there is sufficient content at an adequate level of maturity.