Architecture / Architecture Operating Models / Lifecycle
02 · Intervention
The through-life value stream
Architecture starts before design and continues after go-live across business, information systems and technology.
10lifecycle stages
3architecture layers
30role-by-stage views
One lifecycle, three architectural lenses
Business architecture asks what value and capability must change; information systems architecture shapes applications and data; technology architecture shapes the platforms that sustain them.
flowchart LR TITLE["<b>Business architecture layer</b>"]:::title P1["<b>Strategy</b><br/><small>Define vision, drivers and goals</small>"] P2["<b>Planning</b><br/><small>Capture stakeholder needs</small>"] P3["<b>Design</b><br/><small>Model capabilities and value</small>"] P4["<b>Development</b><br/><small>Translate needs to specifications</small>"] P5["<b>Deployment</b><br/><small>Prepare business adoption</small>"] P6["<b>Transition</b><br/><small>Enable organisational change</small>"] P7["<b>Operation</b><br/><small>Monitor business services</small>"] P8["<b>Maintenance</b><br/><small>Maintain business processes</small>"] P9["<b>Optimisation</b><br/><small>Improve performance</small>"] P10["<b>Retirement</b><br/><small>Retire capabilities safely</small>"] TITLE -.-> P1 P1 --> P2 --> P3 --> P4 --> P5 --> P6 --> P7 --> P8 --> P9 --> P10 classDef title fill:#122f3b,stroke:#122f3b,color:#fff classDef default fill:#f7f4ee,stroke:#204e5f,color:#172226
flowchart LR TITLE["<b>Information systems architecture layer</b>"]:::title P1["<b>Strategy</b><br/><small>Set application and data direction</small>"] P2["<b>Planning</b><br/><small>Capture system requirements</small>"] P3["<b>Design</b><br/><small>Design application and data models</small>"] P4["<b>Development</b><br/><small>Build systems and data</small>"] P5["<b>Deployment</b><br/><small>Introduce services to production</small>"] P6["<b>Transition</b><br/><small>Make systems operationally ready</small>"] P7["<b>Operation</b><br/><small>Run applications and data</small>"] P8["<b>Maintenance</b><br/><small>Update systems and data models</small>"] P9["<b>Optimisation</b><br/><small>Improve efficiency</small>"] P10["<b>Retirement</b><br/><small>Decommission and archive</small>"] TITLE -.-> P1 P1 --> P2 --> P3 --> P4 --> P5 --> P6 --> P7 --> P8 --> P9 --> P10 classDef title fill:#122f3b,stroke:#122f3b,color:#fff classDef default fill:#f7f4ee,stroke:#204e5f,color:#172226
flowchart LR TITLE["<b>Technology architecture layer</b>"]:::title P1["<b>Strategy</b><br/><small>Set technology direction</small>"] P2["<b>Planning</b><br/><small>Capture infrastructure needs</small>"] P3["<b>Design</b><br/><small>Design target infrastructure</small>"] P4["<b>Development</b><br/><small>Build platforms</small>"] P5["<b>Deployment</b><br/><small>Deploy to production</small>"] P6["<b>Transition</b><br/><small>Complete technology handover</small>"] P7["<b>Operation</b><br/><small>Operate infrastructure</small>"] P8["<b>Maintenance</b><br/><small>Patch and upgrade</small>"] P9["<b>Optimisation</b><br/><small>Improve efficiency</small>"] P10["<b>Retirement</b><br/><small>Decommission components</small>"] TITLE -.-> P1 P1 --> P2 --> P3 --> P4 --> P5 --> P6 --> P7 --> P8 --> P9 --> P10 classDef title fill:#122f3b,stroke:#122f3b,color:#fff classDef default fill:#f7f4ee,stroke:#204e5f,color:#172226
Completeness method
Process Lifecycle Completeness
A process map is not complete until the thing being governed has been examined across every lifecycle phase and architectural layer. Assess all 30 phase–layer intersections. A process need not exist in every cell, but every cell must have a decision; use N/A — rationale required only where non-applicability is evidenced.
BusinessDecisions, governance, roles, value and organisational workflow.
Information SystemsApplications, data, integration, information and automated workflow.
TechnologyInfrastructure, platforms, deployment, operation and technical automation.
Assessment sequence
- Identify the thing being governed and the outcome required.
- Examine all 30 phase–layer intersections.
- Identify the processes required at each applicable intersection.
- Define ownership, controls, evidence and hand-offs.
- Record missing or immature processes as gaps and assign actions.
- Validate implementation and measurement, then improve the process using evidence.
flowchart LR
A["1 · Identify the thing<br/>and required outcome"] --> B["2 · Examine all<br/><b>10 lifecycle phases</b>"]
B --> L1["Business<br/><small>decisions · governance · roles · value</small>"]
B --> L2["Information Systems<br/><small>applications · data · integration · workflow</small>"]
B --> L3["Technology<br/><small>platforms · deployment · operation · automation</small>"]
L1 --> C{"Process required<br/>at this intersection?"}
L2 --> C
L3 --> C
C -- Yes --> D["Define owner · outcome · inputs · outputs<br/>controls · evidence · hand-offs"]
C -- No --> E["Record evidenced N/A<br/>with rationale"]
D --> F["Record and remediate gaps"]
E --> G["Validate coverage,<br/>implementation and measures"]
F --> G
G -. improve .-> A
classDef start fill:#122f3b,stroke:#122f3b,color:#fff
classDef layer fill:#e7f0ed,stroke:#204e5f,color:#172226
classDef decision fill:#fff2cc,stroke:#b85f2e,color:#172226
classDef complete fill:#d8f6e7,stroke:#22845b,color:#172226
class A start
class L1,L2,L3 layer
class C decision
class G completeCompletion rule: an applicable process is not complete without an accountable owner, intended outcome, inputs, outputs, controls and evidence, and predecessor/successor hand-offs. The toolkit distinguishes an evidenced N/A from an unassessed gap and provides the register, definitions and remediation views needed to retain the decision.
Workbook source · Through Life Description
The ten stages
A common stage definition used throughout the model.
| Phase | Phase Name | Short Description | Comprehensive Description |
|---|---|---|---|
| 1 | Strategy | Define strategic direction and service portfolio aligned with business objectives | The Strategy phase establishes the foundational direction for service delivery by defining strategic objectives, assessing market opportunities, and determining which services to offer. This includes service portfolio management, demand analysis, financial planning, and business relationship management. Key activities involve understanding customer needs, conducting market assessments, developing service strategies that align with organisational goals, and establishing the business case for service investments. The phase ensures that all subsequent activities are strategically aligned and commercially viable. |
| 2 | Planning | Plan and coordinate resources, timelines, and deliverables for service implementation | The Planning phase translates strategic objectives into actionable plans with defined timelines, resource allocation, and success criteria. This involves detailed project planning, capacity planning, risk assessment, and stakeholder coordination. Key activities include developing comprehensive project plans, establishing governance structures, defining roles and responsibilities, creating communication plans, and setting up monitoring frameworks. The phase ensures proper preparation and coordination across all teams and stakeholders involved in service delivery. |
| 3 | Design | Design service architecture, processes, and governance frameworks | The Design phase creates detailed blueprints for service delivery, including technical architecture, process workflows, and governance frameworks. This encompasses service catalogue development, service level agreements definition, capacity management planning, availability design, security architecture, and supplier management frameworks. Key activities involve designing service components, establishing quality standards, creating documentation standards, and ensuring services are fit for purpose and use. The phase provides the foundation for successful service implementation. |
| 4 | Development | Build, develop, and configure service components and solutions | The Development phase involves building, configuring, and creating the actual service components and solutions. This includes application development, system configuration, infrastructure setup, process implementation, and documentation creation. Key activities encompass coding and development work, system integration, testing preparation, knowledge transfer preparation, and quality assurance processes. The phase transforms design specifications into tangible deliverables ready for deployment. |
| 5 | Deployment | Deploy services into production environment with controlled rollout | The Deployment phase manages the controlled rollout of services into the production environment. This involves deployment planning, environment preparation, data migration, system configuration, and go-live activities. Key activities include coordinating deployment activities, managing deployment risks, ensuring system readiness, conducting final testing, and executing cutover procedures. The phase ensures services are successfully moved from development to live operational status. |
| 6 | Transition | Manage transition of services from development to operational state | The Transition phase manages the handover from development teams to operational teams, ensuring knowledge transfer and operational readiness. This includes change management, service validation, knowledge management, and operational readiness assessment. Key activities involve conducting operational readiness reviews, transferring documentation and knowledge, establishing support procedures, training operational staff, and ensuring smooth transition to operational state. The phase bridges the gap between deployment and full operational capability. |
| 7 | Operation | Execute day-to-day service delivery and support operations | The Operation phase encompasses the day-to-day delivery and management of live services to end users. This includes incident management, service request fulfilment, problem management, access management, and service monitoring. Key activities involve managing service desk operations, resolving incidents and problems, fulfilling service requests, monitoring service performance, and ensuring agreed service levels are maintained. The phase focuses on maintaining service availability, performance, and user satisfaction. |
| 8 | Maintenance | Perform ongoing maintenance, updates, and corrective actions | The Maintenance phase ensures ongoing service health through regular updates, patches, preventive maintenance, and corrective actions. This includes scheduled maintenance activities, security updates, performance tuning, capacity monitoring, and proactive maintenance. Key activities involve conducting regular health checks, applying updates and patches, performing preventive maintenance, monitoring system performance, and addressing maintenance requirements. The phase ensures services remain secure, stable, and performant over time. |
| 9 | Optimisation | Continuously improve service performance and efficiency | The Optimisation phase continuously improves service performance, efficiency, and value delivery through systematic analysis and enhancement. This includes performance monitoring, process improvement, cost optimisation, and service enhancement initiatives. Key activities involve measuring service metrics, identifying improvement opportunities, implementing process enhancements, optimising resource utilisation, and driving continuous improvement initiatives. The phase ensures services evolve to meet changing requirements and deliver maximum value. |
| 10 | Retirement | Decommission services at end-of-life whilst ensuring smooth transition | The Retirement phase manages the controlled decommissioning of services at their end-of-life, ensuring minimal disruption and proper transition arrangements. This includes retirement planning, data migration or archival, system decommissioning, and transition to alternative services. Key activities involve developing retirement plans, communicating with stakeholders, migrating or archiving data, decommissioning infrastructure, and ensuring continuity through alternative arrangements. The phase ensures orderly service cessation whilst protecting business continuity and data integrity. |
Workbook source · Through Life
Role accountabilities by layer and stage
The full EA, SA and OA responsibility matrix.
Business Architecture
The Business Architecture layer focuses on defining the business strategy, governance, organisation, and key business processes. It serves as the foundation for aligning business goals with IT strategies, ensuring that all technology investments support business objectives. Within this layer, several core components are typically addressed. These include business capabilities, which outline what the organisation needs to do to achieve its strategic goals, and value streams, which map out the end-to-end activities that deliver value to stakeholders. Additionally, the Business Architecture layer defines the organisation's structure and relationships between various business units, providing a clear roadmap for implementing change and achieving business transformation.
| Phase | Description | Enterprise Architect Role | Solutions Architect Role | Operational Architect Role |
|---|---|---|---|---|
| 1. Strategy | Define business vision, drivers, and goals. Establish strategic intent and value proposition. Align with enterprise mission and long-term business direction. | Shape and maintain alignment between enterprise business strategy and the target architecture. Ensure architectural direction enables strategic outcomes. | Provide solution-level input into strategic business initiatives, ensuring that proposed solutions are feasible and aligned with the enterprise vision. | Advise on operational constraints and legacy landscape considerations that may influence strategic business decisions or capability direction. |
| 2. Planning | Capture stakeholder needs and business requirements. Conduct business capability assessment, gap analysis, and prioritise initiatives based on feasibility and value. | Define and maintain business capability models and value streams. Ensure business change initiatives align with architectural roadmaps and capability evolution. | Translate high-level business needs into solution options that address capability gaps. Support feasibility assessments and solution scoping. | Identify operational dependencies, risks, and constraints that should be considered during business capability planning and prioritisation. |
| 3. Design | Develop conceptual models for business capabilities, processes, value streams, and organisation structure. Define target business architecture and assess impacts. | Own the definition of target business architecture, including capabilities, organisation structure, and value streams. Ensure alignment with strategic objectives. | Design solution-level business processes and capabilities that realise the target architecture. Ensure traceability from business requirements to solution design. | Validate that new or changed business processes are compatible with operational reality. Highlight any operational impacts or risks arising from business design choices. |
| 4. Development | Translate business requirements into functional specifications. Support development of business services and validate alignment with business capability models. | Govern alignment between business service development and the target architecture. Ensure developed services support intended business outcomes and capability gaps. | Ensure solution development activities are consistent with business requirements and architectural standards. Resolve conflicts between business needs and technical constraints. | Ensure that business processes and services being developed incorporate operational considerations such as support models, monitoring, and handover requirements. |
| 5. Deployment | Oversee readiness for business adoption. Validate organisational preparedness, user enablement, and alignment with business processes and outcomes. | Validate that deployed business services and organisational changes remain aligned with the target business architecture and strategic direction. | Support business readiness and change management activities to ensure solution deployment delivers intended business value with minimal disruption. | Ensure that operational processes, training, and support models are ready to sustain new or changed business services and capabilities post-deployment. |
| 6. Transition | Enable organisational change. Support communication, training, and adoption of new business processes. Ensure business continuity and governance alignment. | Ensure that business transformation activities are consistent with architectural principles and roadmaps. Oversee capability realisation and benefits tracking. | Facilitate solution transition into the operational environment, ensuring that business processes, data, and supporting technology integrate effectively. | Lead operational readiness activities, including updates to processes, tooling, and teams. Ensure operational stability during and after the transition. |
| 7. Operation | Monitor performance of business services and processes. Evaluate business value delivery, customer satisfaction, and alignment with KPIs. | Monitor ongoing business operations from an architectural perspective. Identify areas where architectural evolution or optimisation is required. | Provide support for operational troubleshooting and business performance improvements where linked to solution design. Identify improvement opportunities. | Maintain operational processes, tooling, and support models to ensure business services run effectively. Provide operational metrics to support continuous improvement. |
| 8. Maintenance | Manage business process updates, refine capabilities in response to change, and maintain alignment with business goals and market demands. | Guide refinement of business architecture to reflect evolving business needs and market conditions. Ensure architectural integrity during incremental change. | Assess the impact of business process or capability changes on existing solutions. Lead solution updates to maintain alignment with evolving business requirements. | Ensure operational processes, systems, and capabilities remain aligned with updated business processes. Implement changes to maintain operational effectiveness. |
| 9. Optimisation | Identify performance improvements, process inefficiencies, and opportunities for innovation. Support continuous improvement and evolution of business models. | Drive business model evolution and continuous improvement through architectural innovation. Identify opportunities to simplify, integrate, or enhance capabilities. | Contribute to business process optimisation by proposing solution enhancements or technology enablers that drive business efficiency and innovation. | Provide operational insight, incident trends, and process performance data to inform business-led optimisation initiatives. Support the operationalisation of improvements. |
| 10. Retirement | Manage controlled retirement of business capabilities or services. Ensure transition strategies and lessons learned support future planning. | Govern the retirement of business capabilities and services to ensure strategic alignment, risk mitigation, and architectural coherence. | Support planning and execution of solution decommissioning. Ensure business continuity, data management, and downstream impacts are addressed. | Execute operational decommissioning activities related to retired business services or processes. Manage residual operational risks and update support models as needed. |
Information Systems Architecture
The Information Systems Architecture layer defines the structure and interactions of the core systems that support business functions. It consists of two key domains: Application Architecture and Data Architecture. The Application Architecture outlines the individual applications required to support business processes, detailing how they interact and align with business capabilities. It ensures that the organisation’s software ecosystem is efficient, interoperable, and scalable. This includes considerations around integration (e.g., APIs, messaging), lifecycle management, and system dependencies. The Data Architecture focuses on structuring the organisation’s data assets to support operational and analytical needs. It defines key data entities, their relationships, and how data flows across the enterprise. This includes governance aspects such as data ownership, classification, quality, and compliance - especially important under regulations like GDPR. Together, these architectures create a cohesive view of how applications and data enable the business, ensuring IT solutions are strategically aligned and technically robust.
| Phase | Information Systems Architecture Focus (TOGAF) | Enterprise Architect Role | Solutions Architect Role | Operational Architect Role |
|---|---|---|---|---|
| 1. Strategy | Define strategic direction for applications and data. Identify key systems needed to support business goals. Align technology with business value and regulatory context. | Ensure strategic alignment of applications and data with enterprise architecture. Define principles for system integration and information management. | Contribute to defining solution-level requirements for applications and data. Ensure proposed solutions align with enterprise direction. | Provide input on current systems' constraints and operational considerations to inform strategic planning for applications and data. |
| 2. Planning | Capture information system requirements. Conduct data flow and application capability gap analysis. Identify dependencies and integration points. | Define architectural roadmaps for applications and data, considering secure integration, dependencies, and business alignment. | Translate requirements into solution designs for applications and data, addressing integration, performance, and security needs. | Identify operational risks, constraints, and integration challenges that should inform system requirements and architectural decisions. |
| 3. Design | Develop logical data and application models. Define system interfaces, data entities, and application services. Align with architecture principles. | Own the logical architecture for applications and data. Ensure system models and interfaces align with enterprise standards and enable secure interoperability. | Design application and data models that align with enterprise architecture and security principles. Ensure interfaces and services are properly defined. | Validate system designs against operational capabilities. Ensure proposed solutions can be supported effectively in the production environment. |
| 4. Development | Construct applications and implement data models. Validate systems against functional and data integrity requirements. | Oversee development alignment with architectural standards and principles. Ensure application and data designs are implemented as intended. | Lead solution development, ensuring secure coding practices, data integrity controls, and alignment with design specifications. | Ensure operational readiness is considered during development. Confirm monitoring, logging, and support models are integrated. |
| 5. Deployment | Introduce applications and data services into the production environment. Validate integration and data exchange with live systems. | Validate that deployed systems align with architectural direction and enable secure, efficient operation within the enterprise landscape. | Support deployment activities, validating system configuration, data handling, and integration with existing solutions. | Prepare operational tooling and processes for application and data system support. Validate operational handover and incident readiness. |
| 6. Transition | Ensure systems are operationally ready. Support knowledge transfer and data handover. Confirm governance and lifecycle controls. | Ensure system transition activities maintain architectural integrity. Oversee capability realisation and support governance handover. | Facilitate handover of solution knowledge, ensuring operational teams understand application and data-related responsibilities. | Accept operational responsibility for new or changed systems. Ensure security monitoring, logging, and incident processes are established. |
| 7. Operation | Applications and data systems are in full use. Support ongoing performance, data accuracy, and integration with enterprise systems. | Monitor system performance and integration effectiveness. Identify areas for architectural improvement to support business and technical outcomes. | Support resolution of operational issues related to solution design. Identify opportunities for solution-level improvements. | Operate and maintain secure, stable systems. Provide operational metrics to inform system performance and improvement opportunities. |
| 8. Maintenance | Update applications and data models to reflect changes in requirements or performance insights. Patch and optimise systems. | Guide architectural evolution of applications and data. Ensure updates maintain alignment with enterprise principles and secure system operation. | Assess impact of system changes on solution design. Lead updates to maintain performance, security, and architectural alignment. | Implement updates, patches, and configuration changes securely. Maintain operational alignment with evolving system requirements. |
| 9. Optimisation | Evaluate performance and improve system efficiency. Rationalise application landscape and optimise data usage. | Drive rationalisation and optimisation initiatives. Ensure simplification or replacement activities support enterprise efficiency and security. | Support solution optimisation, redesign, or consolidation activities. Ensure control integration and performance improvements are addressed. | Contribute operational insights to system optimisation efforts. Support secure configuration management and performance tuning. |
| 10. Retirement | Decommission systems and archive or migrate data. Ensure compliance with retention and disposal policies. | Oversee secure and orderly system retirement. Ensure data is managed according to policy and architectural dependencies are addressed. | Lead decommissioning of solutions, ensuring data is handled appropriately and dependent systems are managed. | Execute secure system decommissioning. Remove access, sanitise data, and ensure operational risks are addressed. |
Technology Architecture
The Technology Architecture layer focuses on the infrastructure necessary to support the deployment of applications and data. It defines the hardware, software, networks, and other foundational components that form the IT environment. This layer ensures that the infrastructure is reliable, scalable, and secure, providing a stable foundation for business operations. Key components include servers, storage systems, networking equipment, and virtualisation technologies. Moreover, the Technology Architecture layer addresses standards and protocols to ensure interoperability and future-proofing. It also considers performance, availability, and security requirements, aligning them with business needs. This ensures that the technology environment not only supports current operations but can also adapt to future demands.
| Phase | Technology Architecture Focus (TOGAF) | Enterprise Architect Role | Solutions Architect Role | Operational Architect Role |
|---|---|---|---|---|
| 1. Strategy | Define strategic technology direction. Identify key platforms, infrastructure trends, and target environments to support business objectives. | Define and communicate the strategic direction for the technology environment. Ensure infrastructure vision aligns with business strategy and enterprise standards. | Contribute to defining technology capabilities required to deliver business and solution needs. Ensure alignment with enterprise technology strategy. | Provide insights on existing infrastructure capabilities and constraints to inform strategic technology direction and platform choices. |
| 2. Planning | Capture infrastructure requirements. Conduct capability assessments and determine infrastructure services needed for future-state operations. | Establish technology standards, principles, and reference models to guide infrastructure evolution. Provide architectural governance for platform selection. | Translate solution requirements into infrastructure specifications, addressing performance, scalability, and interoperability needs. | Identify operational requirements and risks that should inform infrastructure planning, capability assessments, and design decisions. |
| 3. Design | Design the target infrastructure architecture, including networks, compute, storage, and hosting environments. Ensure scalability, security, and resilience. | Own the target technology architecture, ensuring it supports scalability, interoperability, and business objectives. Maintain alignment with enterprise principles. | Design infrastructure components and configurations that support solution requirements and align with enterprise architectural standards. | Validate infrastructure designs for operational feasibility. Ensure monitoring, maintenance, and support models are practical and effective. |
| 4. Development | Build infrastructure platforms, configure services, and conduct component-level testing. Establish secure environments. | Oversee infrastructure development to ensure alignment with architectural standards. Resolve conflicts between technical constraints and target architecture. | Lead infrastructure build and configuration activities, ensuring compatibility with solution needs and technical standards. | Ensure operational requirements are incorporated into infrastructure build activities. Prepare monitoring, management, and support tooling. |
| 5. Deployment | Deploy infrastructure into production environments. Ensure compatibility, resilience, and secure integration. | Validate that deployed infrastructure conforms to the architectural vision and supports business and operational requirements. | Support infrastructure deployment, ensuring smooth integration with solutions and existing technology environment. | Validate operational readiness of infrastructure for deployment, including support processes and performance monitoring. |
| 6. Transition | Finalise technology handover. Validate resilience, failover, backup strategies, and support readiness. | Ensure the transition to operational teams maintains architectural integrity. Oversee capability realisation and technology readiness. | Facilitate knowledge transfer for infrastructure components supporting solutions. Ensure operational teams are prepared for handover. | Accept infrastructure into operational support. Ensure teams are equipped to manage and maintain infrastructure effectively. |
| 7. Operation | Manage day-to-day infrastructure operations. Monitor performance, reliability, and maintain service availability. | Monitor infrastructure performance and operational outcomes. Identify areas for architectural evolution to support efficiency and resilience. | Support resolution of infrastructure-related issues impacting solution performance or availability. Identify opportunities for technical improvement. | Manage day-to-day infrastructure operations. Provide performance data and operational insights to inform future architectural decisions. |
| 8. Maintenance | Apply patches, upgrade infrastructure, and support evolving requirements. Ensure availability and resilience. | Guide ongoing infrastructure improvements to maintain alignment with enterprise direction and evolving technology trends. | Assess the impact of infrastructure changes on solutions. Lead updates to maintain solution performance and alignment with technology direction. | Implement infrastructure updates and upgrades in line with operational requirements. Maintain system availability and performance. |
| 9. Optimisation | Enhance infrastructure efficiency, rationalise platforms, and adopt emerging technologies where beneficial. | Drive platform optimisation, rationalisation, and adoption of new technologies. Ensure infrastructure remains efficient, scalable, and future-proof. | Contribute to infrastructure optimisation, ensuring platform changes continue to support solution performance and efficiency. | Contribute operational metrics and experience to infrastructure optimisation initiatives. Ensure platform changes are supportable and efficient. |
| 10. Retirement | Decommission infrastructure components. Remove dependencies and ensure secure disposal of technology assets. | Oversee decommissioning of infrastructure components to ensure alignment with enterprise lifecycle management and future-state architecture. | Support decommissioning of infrastructure linked to solutions. Update solution designs and manage downstream impacts. | Execute infrastructure decommissioning from an operational perspective. Ensure safe removal, dependency management, and knowledge capture. |