LiSA (Lightweight Solution Architecture) is a minimal, collaborative, and adaptive practice for designing solutions within a living sociotechnical environment. Its purpose is to help teams make well‑reasoned architectural decisions, maintain coherence across evolving systems, and support continuous change without the overhead of traditional enterprise architecture frameworks.
LiSA focuses strictly on solution design, not enterprise strategy. It operates inside a dynamic ecosystem and provides a lightweight, repeatable way to transform requirements into coherent architectural outputs.
Haz clic en las diferentes áreas del diagrama para navegar a las secciones
Framework
LiSA is defined by three structural dimensions:
- Interfaces: the formal inputs and outputs of the practice
- Ecosystem & Core Building Blocks: the internal components that enable and execute LiSA
- Architecture: the final deliverable produced by the lifecycle
Together, these elements form a complete solution‑design system.
Interfaces
Requirements (Inputs)
The formal entry point into the LiSA Lifecycle. These inputs provide the purpose, constraints, and expectations that guide solution design.
Includes:
- Purpose & Drivers of the solution
- Functional and non‑functional requirements
- Constraints (technical, regulatory, operational)
- Business rules
- Assumptions and dependencies
These inputs initiate the lifecycle and are stored as artifacts in the Knowledge Base.
Architecture (Final Output)
The formal deliverable produced by LiSA. It represents the validated, coherent, and justifiable design of the solution.
Includes:
- Views (context, components, interactions, quality attributes, etc.)
- Architectural decisions and rationale
- Compliance with requirements
- Coherence assessment
- Evolution and transition scenarios
The Architecture Output is the culmination of the lifecycle and the primary value delivered by LiSA.
Ecosystem and Core Building Blocks
Ecosystem (Living System)
The Ecosystem is the outer boundary of LiSA. It represents the sociotechnical environment in which solutions are conceived, designed, delivered, and evolved.
Includes:
- People, teams, and organizational structures
- Technology platforms and systems
- Processes, constraints, and operational realities
- Continuous feedback from usage and change
LiSA exists inside the ecosystem and adapts to it continuously.
LiSA Practice & Actors
Defines the organizational capability that operates LiSA.
Includes:
- Roles involved in solution design
- Responsibilities and collaboration patterns
- Lightweight governance
- Community, training, and continuous improvement
This block ensures that LiSA is actionable and sustainable.
LiSA Lifecycle (Engine)
The Lifecycle is the engine of LiSA. It is a continuous, iterative flow of activities that guide the design and evolution of solutions.
Lifecycle activities:
- Define Purpose & Drivers
- Identify Stakeholders & Concerns
- Select & Tailor Viewpoints
- Create & Evolve Views
- Make & Record Decisions
- Assess Coherence
- Guide Evolution
- Improve the Practice
The lifecycle is lightweight and integrates naturally with delivery processes.
LiSA Content & Knowledge Base
This building block represents both:
- The architectural artifacts produced by the lifecycle, and
- The guidance that enables the practice to operate consistently and effectively.
It is the backbone of LiSA's shared knowledge.
Lifecycle Artifacts
All outputs generated through the lifecycle, including:
- Requirements & Drivers
- Stakeholders and Concerns
- Viewpoints
- Views
- Architectural Decisions
- Quality attributes and scenarios
- Coherence assessments
- Evolution scenarios
- Lessons learned
- Reusable examples and case references
Practice Guidance
The standards, rules, and reusable knowledge that guide the practice.
Includes:
- Modeling guidelines
- Viewpoint definitions and tailoring rules
- Naming conventions
- Documentation standards
- Quality criteria and review checklists
- Architectural patterns and anti‑patterns
- Reference architectures
- Templates and starter kits
- Contribution guidelines
- Governance and escalation rules
This guidance ensures consistency, quality, and repeatability across all solutions designed with LiSA.
Architecture
Architecture is the final, coherent representation of the solution produced by LiSA. It is the output interface of the framework and the primary artifact consumed by teams, stakeholders, and delivery processes.
Characteristics of the Architecture Output:
- Derived from requirements and ecosystem constraints
- Built through the LiSA Lifecycle
- Documented using viewpoints and views
- Justified through architectural decisions
- Evaluated for coherence and feasibility
- Positioned for evolution through scenarios and transitions
The Architecture Output is not a single document but a set of interconnected artifacts that collectively describe the solution.