Linked.Archi ADMIT Framework Taxonomy

ADMIT Concept Scheme

• ▼Architecture Level
  Architecture level represents the scope boundary and granularity of details the architectural activity should take, based on organization hierarchy and communication audience.

  https://meta.linked.archi/admit/tax#ArchitectureLevel
  • 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.

    https://meta.linked.archi/admit/tax#EnterpriseArchitecture
  • 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.

    https://meta.linked.archi/admit/tax#SolutionArchitecture
  • 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.

    https://meta.linked.archi/admit/tax#SystemArchitecture
• ▼Architecture Domain
  IT architecture encompasses four domains from an information management perspective, based on the components of enterprise, solution, and system architectures.

  https://meta.linked.archi/admit/tax#ArchitectureDomain
  • 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.

    https://meta.linked.archi/admit/tax#BusinessArchitecture
  • 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.

    https://meta.linked.archi/admit/tax#InformationDataArchitecture
  • 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.

    https://meta.linked.archi/admit/tax#ApplicationServiceArchitecture
  • Technology/Technical Architecture (Where domain)
    Technology/Technical Architecture (Where domain) addresses the technology stack, data center, cloud delivery, network topology, and security architecture.

    https://meta.linked.archi/admit/tax#TechnologyTechnicalArchitecture
• ▼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.

  https://meta.linked.archi/admit/tax#ArchitectureAndResourceDimension
  • Workload
    Computational tasks being performed within the system, consuming available processor capacity.

    https://meta.linked.archi/admit/tax#Workload
  • Demand
    User load addressing average and peak capacities, mostly consuming memory for session, state and cache.

    https://meta.linked.archi/admit/tax#Demand
  • Throughput
    Volume of data transferred to and from storage, measured in I/O operations per second or megabytes per second.

    https://meta.linked.archi/admit/tax#Throughput
  • Latency
    Round-trip time and processing delay of network resources.

    https://meta.linked.archi/admit/tax#Latency
  • Capacity
    Raw resource power — CPU, memory, network, storage — contributing to vertical scaling.

    https://meta.linked.archi/admit/tax#Capacity
  • Redundancy
    Multiple machines sharing workloads or providing seamless failover, contributing to horizontal scaling.

    https://meta.linked.archi/admit/tax#Redundancy
• ▼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.

  https://meta.linked.archi/admit/tax#ArchitectureDesignForces
  • Business Force
    See Also: BusinessForce

    https://meta.linked.archi/admit/tax#BusinessForceConcept
  • Operation Force
    See Also: OperationForce

    https://meta.linked.archi/admit/tax#OperationForceConcept
  • Aestheticism Force
    See Also: AestheticismForce

    https://meta.linked.archi/admit/tax#AestheticismForceConcept
  • Future Force
    See Also: FutureForce

    https://meta.linked.archi/admit/tax#FutureForceConcept
  • Simplicity Force
    See Also: SimplicityForce

    https://meta.linked.archi/admit/tax#SimplicityForceConcept
  • Change Force
    See Also: ChangeForce

    https://meta.linked.archi/admit/tax#ChangeForceConcept
  • Process Force
    See Also: ProcessForce

    https://meta.linked.archi/admit/tax#ProcessForceConcept
  • Integration Force
    See Also: IntegrationForce

    https://meta.linked.archi/admit/tax#IntegrationForceConcept
  • Implementation/Pattern Force
    See Also: ImplementationPatternForce

    https://meta.linked.archi/admit/tax#ImplementationPatternForceConcept
  • Enterprise Force
    See Also: EnterpriseForce

    https://meta.linked.archi/admit/tax#EnterpriseForceConcept
  • Constraint/Environment Force
    See Also: ConstraintEnvironmentForce

    https://meta.linked.archi/admit/tax#ConstraintEnvironmentForceConcept
  • Failure Force
    See Also: FailureForce

    https://meta.linked.archi/admit/tax#FailureForceConcept
  • Channel Force
    See Also: ChannelForce

    https://meta.linked.archi/admit/tax#ChannelForceConcept
  • Content Force
    See Also: ContentForce

    https://meta.linked.archi/admit/tax#ContentForceConcept
  • Platform Force
    See Also: PlatformForce

    https://meta.linked.archi/admit/tax#PlatformForceConcept
  • Infrastructure Force
    See Also: InfrastructureForce

    https://meta.linked.archi/admit/tax#InfrastructureForceConcept
  • Network Force
    See Also: NetworkForce

    https://meta.linked.archi/admit/tax#NetworkForceConcept
  • Storage Force
    See Also: StorageForce

    https://meta.linked.archi/admit/tax#StorageForceConcept
  • Security Force
    See Also: SecurityForce

    https://meta.linked.archi/admit/tax#SecurityForceConcept
  • Cost Force
    See Also: CostForce

    https://meta.linked.archi/admit/tax#CostForceConcept
• ▼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.

  https://meta.linked.archi/admit/tax#ArchitectureDevelopmentLifecycle
  • ▼Development Area
    Encompasses the planning, design, and management phases of architecture development.

    https://meta.linked.archi/admit/tax#DevelopmentArea
    • ▼Planning/Strategy Phase
      Identifies business vision, stakeholder management, architecture strategy, and current state assessment.

      https://meta.linked.archi/admit/tax#PlanningStrategyPhase
      • Identify business vision and strategy
        Business vision and strategic plan are identified. Architecture is initiated by a business case and its objectives.

        https://meta.linked.archi/admit/tax#IdentifyBusinessVisionAndStrategy
      • Plan stakeholder management
        Stakeholders are identified. Managing their expectations, requirements, and communication needs are keys to success.

        https://meta.linked.archi/admit/tax#PlanStakeholderManagement
      • Define architecture and technology strategy
        Management and strategic direction are defined by technology standards, asset governance, and portfolio management.

        https://meta.linked.archi/admit/tax#DefineArchitectureAndTechnologyStrategy
      • Assess current architecture
        Architecture assessment is performed by reviewing requirements and comparing them with the current architecture state.

        https://meta.linked.archi/admit/tax#AssessCurrentArchitecture
    • ▼Design/Execution Phase
      Develops target architecture, conducts gap analysis, builds roadmaps, and creates reference architectures.

      https://meta.linked.archi/admit/tax#DesignExecutionPhase
      • Design target architecture
        The target architecture with future processes is developed using architecture design forces.

        https://meta.linked.archi/admit/tax#DesignTargetArchitecture
      • Conduct gap analysis
        Current and target architectures are compared and gaps between them are identified.

        https://meta.linked.archi/admit/tax#ConductGapAnalysis
      • Develop execution roadmap
        An execution roadmap with project initiatives and sequencing is developed based on business priorities.

        https://meta.linked.archi/admit/tax#DevelopExecutionRoadmap
      • Build reference architecture
        Reference architecture provides architectural foundation and guidance via solution blueprints and models.

        See Also: ReferenceArchitecture

        https://meta.linked.archi/admit/tax#BuildReferenceArchitecture
    • ▼Management/Governance Phase
      Reviews architecture with stakeholders, initiates projects, performs governance, and manages lifecycle changes.

      https://meta.linked.archi/admit/tax#ManagementGovernancePhase
      • Review architecture with stakeholders
        Architecture views and roadmap are reviewed with stakeholders and validated for viability and feasibility.

        https://meta.linked.archi/admit/tax#ReviewArchitectureWithStakeholders
      • Initiate a quick-win project
        Begin with a foundation project that emphasizes accelerating time-to-market to realize business value quickly.

        https://meta.linked.archi/admit/tax#InitiateQuickWinProject
      • Perform implementation governance
        Architecture team manages and monitors that standards and guidelines are followed by delivery teams.

        https://meta.linked.archi/admit/tax#PerformImplementationGovernance
      • Manage lifecycle changes
        Architecture responds to changing business needs. Changes are evaluated for impact and managed proactively.

        https://meta.linked.archi/admit/tax#ManageLifecycleChanges
      • Manage architecture assets
        Deliverable artifacts such as views, models, catalogs are recorded and managed within a content repository.

        https://meta.linked.archi/admit/tax#ManageArchitectureAssets
  • ▼Optimization Area
    Focuses on continuous improvement of architecture and processes.

    https://meta.linked.archi/admit/tax#OptimizationArea
    • ▼Optimization Phase
      Focuses on continuous improvement of architecture products and development processes.

      https://meta.linked.archi/admit/tax#OptimizationPhase
      • Improve architecture and process continuously
        Architectures are improved and optimized iteratively to maximize their value to the business.

        https://meta.linked.archi/admit/tax#ImproveArchitectureAndProcessContinuously
  • ▼Automation Area
    Focuses on using tools and technology to streamline architecture development.

    https://meta.linked.archi/admit/tax#AutomationArea
    • ▼Automation Phase
      Leverages tools and technologies to automate parts of the architecture development lifecycle.

      https://meta.linked.archi/admit/tax#AutomationPhase
      • Automate lifecycle with tool and technology
        Appropriate tools and technologies should be used to automate parts of the development lifecycle.

        https://meta.linked.archi/admit/tax#AutomateLifecycleWithToolAndTechnology