Glossary

• LAF uses four basic concepts that have many meanings depending on the context in the IT world. These are:
• Application – a software program or a group of software programs that are designed for the end user.
• Component – a software program or a group of software programs that have an implementation of one or more capabilities. The most common components are Applications, but the definition also includes cloud services, integration services, microservices, and others.
• Capability – the ability of an Application or Component to carry out the fundamental functions required by an organization. These capabilities often represent key business processes, tasks, or data sources depending on the needs of the organization; usually, it is the main role and functionality of the Application or Component.
• Requirements – the requirements that the business defines for Applications and Components.

Although Component is a more general definition, the definitions of Applications and Components are treated interchangeably due to the fact that they participate in the same architectural practices. The use of the word Application makes this document easier to understand.

1. Introduction

The pace, frequency and scope of changes in the world around us force a change in the approach to change management. Since change management has become a new standard, not an emergency, it means that only a continuous transformation of the company will allow it to survive nowadays. 

Artificial intelligence is increasingly becoming a central driver of this transformation. AI agents now actively participate across the software development life cycle—from generating code to proposing architectural solutions. LAF addresses this shift explicitly in Section 5, extending its roles and artifacts so that architecture remains effective, cohesive, and well-governed when software development is carried out by both AI and human teams.

The Lean Architecture Framework is a collection of good practices thanks to which the IT environment will respond consistently and quickly to a changing business situation while maintaining its structural consistency. It does this by appropriately placing the Architect in the software development life cycle. An architect with the right knowledge can quickly make good decisions. All LAF elements also work very well in the process of purchasing applications or services. The newly purchased solution will be consistent with the entire environment.

LAF not only contributes to the implementation of continuous transformation; it also actively supports it. LAF does this through constant changes in architectural goals and continually striving to achieve them.

LAF supports the commitment of all architects and business stakeholders by building agreements between them, striving to establish a lasting, healthy relationship. Thanks to this, it fosters the personal development of architects working in the organization, which in turn has a direct impact on making good decisions regarding the IT environment.

Innovation is at the heart of LAF. Day after day, the architect has the opportunity to propose new solutions during direct cooperation with the business. LAF supports the dissemination and implementation of business ideas throughout the organization.

The main characteristics of LAF are:

Simple	LAF is simple, concise, and easy to understand.
Pragmatic	LAF concentrates only on activities that provide value and nothing more.
Adaptable	LAF is easy to adapt to the specifics and needs of the organization.
Complete	LAF is used to manage all aspects of a complex IT architecture environment; it is a full-fledged solution containing proven guidelines to support it.
Enables Architectural Agility	LAF supports a constant response to the current situation of an organization and adaptation to a changing business environment.

2. Why good architecture is needed

Every large organization needs to manage its IT architecture, especially the Application landscape, to stay cost-efficient, flexible, and open to change across the entire organization rather than just within a single business area or Application.

The LAF framework responds to these needs by providing full guidelines that define roles, events, and artifacts.

• The main goals of implementing LAF in organizations are to:
• Control the complexity of the IT Application landscape by preventing uncontrolled growth and duplication of functional capabilities within the organization,
• Deliver architectural paths enabling business and technological growth within the organization,
• Keep the Component stack up to date, preventing technical degradation, legacy systems, and technical debt,
• Embed organization goals and mission into the software development life cycle, providing a better understanding of them across the organization,
• Support organizational flexibility for adoption, resiliency to demanding markets, and continuous competition,
• Keep costs at an optimal level, and
• Protect the organization from technical bankruptcy.

LAF acknowledges the fact that today’s organizations are under constant pressure from demanding markets and competitors. That is why organizations need to undergo continuous transformation instead of relying on big transformational projects that can hardly keep up with a changing market. As a result of properly managed IT architecture, organizations become cost-optimal with a consistent environment ready for further growth and extension, enabling business momentum.

Every organization has its own software delivery process (SDLC)—whether based on Agile methodologies like Scrum, XP, LeSS, SAFe, etc., or more traditional approaches like Waterfall—but all of them need architectural guardrails to stay consistent and be ready for change.

As the pace of building AI-enabled solutions accelerates, a solid architectural description becomes a critical component of their implementation, ensuring a consistent and harmonized environment.