Overview of architecture mapping

Once your council has confirmed which critical systems are in scope for your CAF for local government self-assessment, you can start architecture mapping.

What architecture mapping involves

Download the architecture mapping workbook (.xlsx, 113KB)
Gather existing documentation on your chosen critical system and its supporting infrastructure
Complete your architecture mapping workbook with the technical and architectural scoping of your critical systems – document the components breakdown, dependencies and system boundaries
Make sure your team considers important architecture scoping decisions
Create architecture map(s) for each critical system – follow the step by step guide. These should be high level diagrams
Check your architecture workbook and map(s) for quality and accuracy
Finalise your architecture workbook and map(s) and share with your independent assurer

Timescales

Mapping your architecture will take approximately 15 to 25 hours per critical system for your team to complete. This will vary depending on your existing understanding, current documentation and expertise available to support mapping each critical system.

Who should be involved

You will need dedicated technical support for this activity. Collaborate with system mappers – usually a specialist role within your IT team, or the service provider responsible for the system in scope.

support the network and systems discovery work
create network architecture map(s) for each critical system

You will also need to collaborate with technical specialists and subject matter experts.

If you do not have this expertise within your council, you may need to seek external support.

About the architecture mapping workbook

Architecture mapping involves architecture scoping and creating architecture maps. Use the workbook to document the information required and to create these maps.

Your high level diagrams can be maintained beyond the CAF for local government. They support best practice around technical documentation maintenance as part of effective technical risk management.

The workbook includes templates for your:

architecture scoping – use this to identify and document details for your architecture maps, including components breakdown, dependencies and system boundaries
architecture maps – use this to share your diagrams with your independent assurer. Maps should show the boundaries of what your council will assess, and what your independent assurers will focus on during your self-assessment

If you have previously completed an architecture mapping exercise, review it and make sure it is still accurate before starting your critical systems self-assessment.