Lars Ugleberg

Business capabilities

lars@ugleberg.dk — Tue, 30 Jun 2026 06:58:05 +0000

Zzz…

Web app design principles

lars@ugleberg.dk — Sun, 03 May 2026 18:52:02 +0000

As en enterprise and solution architect, I rarely participate hands-on in development. But I work closely with the developers in my clients’ projects, so I need to maintain my programming and technology skills to unify project managers, business experts, and developers. Therefore, I’m continually developing a few useful web apps: My work adheres to the following design principles…

Source

Enterprise architecture

lars@ugleberg.dk — Wed, 19 Nov 2025 07:37:50 +0000

In short, your enterprise architecture is your setup for executing your business model. It follows that you always have an enterprise architecture, regardless of whether it is the random and undocumented result of endless chaotic decisions over time or has been optimally designed and documented to serve your business model execution efficiently and effectively. The usefulness of your current…

Source

Check your project readiness

lars@ugleberg.dk — Wed, 12 Nov 2025 21:46:20 +0000

This checklist helps you evaluate your organization’s readiness to run a development project efficiently. A solid enterprise architecture practice offers significant advantages to the project: A weak or no enterprise architecture practice means that the project faces an uphill battle on all fronts. Much more business analysis work is necessary to uncover the business model…

Source

Development process

lars@ugleberg.dk — Tue, 09 Dec 2025 10:09:32 +0000

The development process standardizes how your projects work to make changes to your enterprise architecture. An efficient and lean development process focuses on the creation of specific work products that serve as input for the development of other necessary work products, ultimately leading to the implementation of new and improved processes supported by new and improved IT systems.

Source

Monte Carlo simulations

lars@ugleberg.dk — Tue, 03 Mar 2026 20:59:48 +0000

Traditionally, a business case includes a calculation of the costs and benefits based on best guesses. Sometimes, three calculations are made – the worst, the best, and the most likely scenarios. The problem with both these approaches is that neither hints to the actual probability of any scenario being more likely than another. The solution is to use the Monte Carlo method[Wikipedia] to…

Source

Solution architecture

lars@ugleberg.dk — Mon, 15 Dec 2025 20:57:59 +0000

Solution architecture is a subset of your enterprise architecture. When you set out to develop and implement changes to your enterprise architecture, it’s practical to design and document the emerging changes in the context of a solution, which is edited into your enterprise architecture documentation as the new solution is implemented into your business and IT architecture. The order of the…

Source

Understand the business model

lars@ugleberg.dk — Thu, 30 Oct 2025 07:54:44 +0000

Business analysts develop requirements for systems, which architects can design to support key processes in the company’s business model. It follows that understanding a company’s business model is very helpful in both these disciplines. A business model is just a standardized view of the elements that make your business tick. The standardized view is based on the business model canvas.

Source

Business analysis

lars@ugleberg.dk — Tue, 13 Jan 2026 08:04:02 +0000

A process is a sequence of activities that lead to an intended and desirable result. Activities involve performing one or more tasks, each of which can be detailed in any numer of steps. Inspiration: The Difficult Process of Identifying Processes Example: online bookshop. Chained business models: Writer -> Publisher -> Bookshop -> Shipping company -> Reader. Activities…

Source

UML

lars@ugleberg.dk — Tue, 10 Feb 2026 06:01:34 +0000

UML (Unified Modelling Language) is my preferred standard for illustrating various aspects of solution architecture. Other standards are gaining popularity, particularly ArchiMate, which I find fairly impractical. When using UML, I rarely adhere strictly to the formal specification, since almost no one actually fully knows it. I often draw UML diagrams in draw.io…

Source