Prof. Dr. Larry AdamsAcademic, Author & Researcher
Information Technology — Level 7 · 12 slides

Presentation · 12 slides

Information Technology — Level 7

Enterprise Architecture, Data, Cloud, Software Delivery, Governance and Digital Strategy

Prof. Dr. Larry Adams

A Level 7 teaching deck on Information Technology: Enterprise Architecture, Data, Cloud, Software Delivery, Governance and Digital Strategy.

Free to view online and to download for teaching, with acknowledgement of the author. To reproduce or adapt any part of a deck, please request permission through the contact page beforehand.

  1. Information Technology — Level 7

    UKVAA • ADVANCED STUDY SERIES

    Level 7 Information Technology

    Enterprise Architecture, Data, Cloud, Software Delivery, Governance and Digital Strategy

    Level 7 | Strategic and critical application

    Teaching presentation • First edition • 2026

    01
  2. Learning outcomes

    • Evaluate IT strategy and enterprise architecture against organisational objectives.
    • Design resilient, secure, interoperable and supportable services.
    • Apply data governance, software delivery and cloud decision principles.
    • Assess technology risk, procurement, change and service performance.
    • Develop a digital transformation roadmap with measurable benefits.
    02
  3. IT strategy and enterprise architecture

    • IT enables business processes, customer experience, decision-making and new operating models.
    • Technology value depends on adoption, process redesign, data quality and governance.
    • Map business capabilities, processes, information, applications, infrastructure and dependencies.
    • Use current and target architectures to expose duplication, gaps and migration risk.
    • Apply principles of modularity, interoperability, security, accessibility and lifecycle support.
    03
  4. Requirements and software delivery

    • Start with stakeholder needs, business outcomes, constraints and measurable acceptance criteria.
    • Model processes, data flows, interfaces, user journeys and exception paths.
    • Prioritise requirements by value, risk, dependency and cost of delay.
    • Use version control, code review, automated testing and reproducible builds.
    • Plan staged rollout, rollback, monitoring and technical-debt remediation.
    04
  5. Data architecture and governance

    • Define data owners, stewards, quality rules, lineage, retention and permitted uses.
    • Choose databases, warehouses, lakes or domain platforms according to needs and operating model.
    • Assess accuracy, completeness, consistency, timeliness, uniqueness and validity.
    • Use metadata and master/reference data management for reliable definitions.
    • Protect privacy and confidentiality throughout collection, use, sharing and disposal.
    05
  6. Cloud and infrastructure

    • Compare public, private, hybrid and multi-cloud by workload, risk, latency, cost and capability.
    • Provider security does not remove customer configuration and access responsibilities.
    • Plan identity, network segmentation, encryption, logging, backup and recovery before migration.
    • Model egress, licensing, support, skills and exit costs in total cost of ownership.
    • Document portability and exit options where vendor lock-in creates material risk.
    06
  7. IT service management and resilience

    • Define service owners, service-level objectives, incident severity and escalation routes.
    • Separate incident restoration, root-cause analysis, change enablement and request fulfilment.
    • Use runbooks, monitoring, knowledge management and post-incident reviews.
    • Measure availability, latency, change failure rate, recovery time and user experience.
    • Set recovery objectives and test backup restoration, failover and continuity dependencies.
    07
  8. Cybersecurity and privacy by design

    • Apply least privilege, secure defaults, defence in depth and separation of duties.
    • Use threat modelling and risk assessment early in design.
    • Protect identity, endpoint, network, application, data and supplier layers.
    • Integrate vulnerability management, secure development, logging and incident response.
    • Security and privacy are shared responsibilities supported by specialist expertise.
    08
  9. Integration, AI and procurement

    • Document API contracts, authentication, rate limits, error handling and versioning.
    • Handle retries, duplicate messages, partial failure and schema changes safely.
    • Select AI/automation for a defined problem and test accuracy, fairness, privacy and impact.
    • Use human review, fallback paths and monitoring for high-impact or uncertain outputs.
    • Assess vendors for security, support, data ownership, subcontractors, exit and total cost.
    09
  10. Digital transformation roadmap workshop

    • Present business drivers, current-state architecture and priority pain points.
    • Propose target architecture, phases, dependencies and transition approach.
    • Set data, security, service management, continuity and vendor controls.
    • Build cost, capacity, skills and change-adoption assumptions.
    • Define benefits, owners, risk triggers and governance gates.
    10
  11. End-text references and further reading (1)

    • AXELOS (2019). ITIL Foundation: ITIL 4 Edition. TSO.
    • COBIT (2019). COBIT Framework. ISACA.
    • DAMA International (2017). DAMA-DMBOK (2nd ed.). Technics Publications.
    • Fielding, R.T. (2000). Architectural Styles and the Design of Network-based Software Architectures. UC Irvine dissertation.
    • Fowler, M. (2018). Refactoring (2nd ed.). Addison-Wesley.
    • UKVAA | References for further reading; check current editions and local requirements
    • UKVAA | References for further reading; check current editions and local requirements
    11
  12. End-text references and further reading (2)

    • ISO 22301:2019; ISO/IEC 27001:2022; ISO/IEC 38500:2024; ISO/IEC 42001:2023.
    • NIST (2024). Cybersecurity Framework 2.0; NIST (2023). AI Risk Management Framework; NIST SP 800-53 Rev. 5.
    • Sommerville, I. (2016). Software Engineering (10th ed.). Pearson.
    • The Open Group (2022). TOGAF Standard, 10th Edition.
    • Weill, P. & Ross, J.W. (2004). IT Governance. Harvard Business School Press; Westerman, G. et al. (2014). Leading Digital.
    • UKVAA | References for further reading; check current editions and local requirements
    • UKVAA | References for further reading; check current editions and local requirements
    12
01 / 12