Linked.Archi ADMIT Framework Taxonomy
SKOS taxonomy of ADMIT framework concepts — architecture levels, domains, resource dimensions, design forces classification, and the architecture development lifecycle (ADLC) with its phases and processes.
Linked.Archi
ADMIT Framework (Prasad Rao, InfoQ 2014)
ADMIT Concept Scheme
Classification of architecture concepts from the ADMIT framework.
Architecture Level
Architecture level represents the scope boundary and granularity of details the architectural activity should take, based on organization hierarchy and communication audience.
Enterprise Architecture
Company level
Enterprise Architecture (Company level) aligns technological strategies and execution plans with business visions and objectives by providing architectural oversight and guidance. Enterprise architecture also drives consolidation, reuse, and economy of scale by addressing company-wide goals in a holistic way across all IT projects.
Solution Architecture
Department level
Solution Architecture (Department level) models a solution vision that defines the IT systems, business processes and reusable services for a specific business unit, spanning across business and technology architectures.
System Architecture
Team level
System Architecture (Team level) defines the structure of an information system in terms of various subsystem components and their relationships with internal and external systems. System architecture focuses on application, data, and technology, and is called software architecture in some organizations.
Architecture Domain
IT architecture encompasses four domains from an information management perspective, based on the components of enterprise, solution, and system architectures.
Business Architecture
Why domain
Business Architecture (Why domain) represents the business-centric view of the enterprise from a functional perspective. Business processes, business services, and business rules are defined and designed along with the business operating model, business performance goals, and organizational structure.
Information/Data Architecture
What domain
Information/Data Architecture (What domain) describes the data assets and management resources, such as information catalogs, data models, data-flows, data quality, and data security, to support critical business functions and the governance models to share data across enterprise.
Application/Service Architecture
How domain
Application/Service Architecture (How domain) provides the blueprint for applications and services and their alignment with other business processes and services.
Technology/Technical Architecture
Where domain
Technology/Technical Architecture (Where domain) addresses the technology stack, data center, cloud delivery, network topology, and security architecture.
Architecture and Resource Dimension
Technology architecture prepares the infrastructure environment by optimizing the use of system resources to meet key business demands. A balanced mix of workload, demand, throughput, and latency for a desired capacity and redundancy is required.
Workload
Computational tasks being performed within the system, consuming available processor capacity.
Demand
User load addressing average and peak capacities, mostly consuming memory for session, state and cache.
Throughput
Volume of data transferred to and from storage, measured in I/O operations per second or megabytes per second.
Latency
Round-trip time and processing delay of network resources.
Capacity
Raw resource power — CPU, memory, network, storage — contributing to vertical scaling.
Redundancy
Multiple machines sharing workloads or providing seamless failover, contributing to horizontal scaling.
Architecture Design Forces
ADF
Design forces focus on the strategies and techniques of developing the architecture systematically. ADFs are used to drive the methodical development of any architecture.
Business Force
Operation Force
Aestheticism Force
Future Force
Simplicity Force
Change Force
Process Force
Integration Force
Implementation/Pattern Force
Enterprise Force
Constraint/Environment Force
Failure Force
Channel Force
Content Force
Platform Force
Infrastructure Force
Network Force
Storage Force
Security Force
Cost Force
Architecture Development Lifecycle
ADLC
Lifecycle defines the phases and processes of managing the architecture development. Fifteen processes are grouped into five phases across three areas: development, optimization, and automation.
Development Area
Encompasses the planning, design, and management phases of architecture development.
Optimization Area
Focuses on continuous improvement of architecture and processes.
Automation Area
Focuses on using tools and technology to streamline architecture development.
Planning/Strategy Phase
Identifies business vision, stakeholder management, architecture strategy, and current state assessment.
Design/Execution Phase
Develops target architecture, conducts gap analysis, builds roadmaps, and creates reference architectures.
Management/Governance Phase
Reviews architecture with stakeholders, initiates projects, performs governance, and manages lifecycle changes.
Optimization Phase
Focuses on continuous improvement of architecture products and development processes.
Automation Phase
Leverages tools and technologies to automate parts of the architecture development lifecycle.
Identify business vision and strategy
Business vision and strategic plan are identified. Architecture is initiated by a business case and its objectives.
Plan stakeholder management
Stakeholders are identified. Managing their expectations, requirements, and communication needs are keys to success.
Define architecture and technology strategy
Management and strategic direction are defined by technology standards, asset governance, and portfolio management.
Assess current architecture
Architecture assessment is performed by reviewing requirements and comparing them with the current architecture state.
Design target architecture
The target architecture with future processes is developed using architecture design forces.
Conduct gap analysis
Current and target architectures are compared and gaps between them are identified.
Develop execution roadmap
An execution roadmap with project initiatives and sequencing is developed based on business priorities.
Build reference architecture
Reference architecture provides architectural foundation and guidance via solution blueprints and models.
Review architecture with stakeholders
Architecture views and roadmap are reviewed with stakeholders and validated for viability and feasibility.
Initiate a quick-win project
Begin with a foundation project that emphasizes accelerating time-to-market to realize business value quickly.
Perform implementation governance
Architecture team manages and monitors that standards and guidelines are followed by delivery teams.
Manage lifecycle changes
Architecture responds to changing business needs. Changes are evaluated for impact and managed proactively.
Manage architecture assets
Deliverable artifacts such as views, models, catalogs are recorded and managed within a content repository.
Improve architecture and process continuously
Architectures are improved and optimized iteratively to maximize their value to the business.
Automate lifecycle with tool and technology
Appropriate tools and technologies should be used to automate parts of the development lifecycle.