There is a requirement for the Enterprise Data
Architect to be involved in and consulted on all
non-functional, architectural and design-led
discussion and decision-making. The Architect is
responsible for:
Undertake a key technical role in the area
of advanced data techniques, including
data modelling, data access, data
integration, data visualisation, text mining,
data discovery, database design and
implementation.
Responsible for the definition and
implementation of the enterprise data
roadmap, including data modelling,
enterprise data warehousing and advanced
data analytics systems.
Responsible for creating the information
architecture and roadmaps to define the
corporate data framework and explain the
migration steps necessary to meet
evolving business requirements
Provide leadership in relation to the
design, documentation and establishment
of the storage and analytic environments
required for structured, semi-structured
and unstructured data.
Provide technical advice and support to
EARLY ENGAGEMENT PHASE:
Engagement – must take place at the earliest opportunity within
the project delivery.
Artefacts:
Contribution to Business Case preparation
Non-Functional Requirements document – consistent with
Digital Division standard NFRs – standalone and also as input
to ITT.
Options Paper
TENDER PHASE:
Engagement – Architect responsible for NFRs requires to engage
via Procurement in tender responses and information requests via
procurement in respect of suppliers Scoring of the ITT responses.
Artefacts:
Feedback responses collated by procurement
Individual scoring spreadsheets with detailed constructive
analysis/criticism of responses providing reasoning behind
scores which can be used to feed back to tenderer.
DESIGN & IMPLEMENTATION PHASE:
Engagement – Collaboration between supplier, project team &
stakeholders. Production/Review of the following artefacts:
Artefacts:
Developers and other Architects in matters
related to data architecture, to ensure that
developments meet required standards.
Analyse new business requirements from a
data architecture perspective to ensure
solutions meet standards for reliability,
scalability, and availability.
Be responsible for identifying the technical
and business risks associated with relevant
architectural decisions and technical
roadmaps.
Designs – High Level and Low Level Design Documents
showing how and where within the Police Scotland
environment the service will be hosted or how we connect to
the solution (if cloud hosted, etc.)
Options Paper – pros, cons, costs, effort, etc. (e.g. if there are
multiple options where systems should be hosted).
Other common diagrams produced/reviewed by the Enterprise
Data Architect during the Design & Implementation stage include:
High Level Context Diagram
Integrations Diagram
Deployment / Physical Design Diagram
Traffic / Data Flow Diagrams
Server Build request forms
Task raised to support build requirements from the design
Briefing Papers where technical considerations/ changes need
to be conveyed, raised and agreed with senior management
and business stakeholders. Format deconstructs technical
details to promote higher level understanding suitable for
non-technical staff.
Enterprise Data Architect contribute to the following Project
Deliverables:
Failover/ continuity documentation (Project Deliverable) –
Aspects of this will be present in design documentation but
greater detail will be required. This is a project deliverable
with a contribution from Enterprise Data Architect.
Project Plan (Project Deliverable) - input into the steps
required to build and deliver the documented design, any
cutover/BRC/go-live activities, plus any decommissioning.
High level presentations/overview of the solution, based on
the requirements of the audience, such as the business or
technical teams