Business Analysis & Requirements Engineering

So software solves the right problem.

When goals, business rules and system boundaries remain unclear, developers have to resolve fundamental questions during implementation. KAN Service clarifies these relationships early and turns them into requirements that teams can work with.

Bern region hybrid across Switzerland

Adrian Wildermuth
Adrian WildermuthSenior Business Analyst / Requirements Engineer25+ years of experience in IT and software projects

From business need to requirement

Understand the problem. Prepare for implementation.

A documented request does not yet explain which rules apply, where exceptions occur or which systems are affected. KAN Service works through these questions with business, development and architecture teams.

Business Analysis and Requirements Engineering
01

Clarify goals and rules

Which problem needs to be solved? Which business rules apply, and where do expectations conflict?

02

Make dependencies visible

Which system owns which data? Where are the interfaces, responsibilities and outstanding decisions?

03

Make outcomes verifiable

Describe requirements, exceptions and acceptance criteria so that business and development teams share the same foundation.

Understand the business. Think through the software.

The critical questions lie in the detail.

Experience in software development and architecture brings a different perspective to business requirements. Data ownership, failure scenarios and technical dependencies become part of the analysis from the outset.

This allows outstanding decisions to be discussed before they become embedded in interfaces and code.

Technical Analysis and System Architecture
A simplified example
“The data must be up to date.”

Three questions that turn this into a verifiable requirement:

Time
What is the maximum acceptable age of the displayed data?
Responsibility
Which system provides the authoritative source?
Exception
What should happen if the source is unavailable?

A general request becomes specific rules for implementation and testing.

Suitable project situations

When your initiative needs clarity.

At the start of an initiative, before a significant decision or during implementation: the starting point depends on which questions will help your team move forward.

  • 01

    Define the scope of a new initiative

    Clarify goals, scope and affected systems before choosing a solution direction.

  • 02

    Develop existing requirements

    Address gaps, conflicting rules and outstanding decisions in existing documentation.

  • 03

    Bring business and IT together

    Work together to clarify differences in terminology, expectations and responsibilities.

  • 04

    Resolve recurring questions

    Investigate the causes of interpretation effort and rework in an ongoing project.

Working together: The focus is on longer-term assignments. Clearly scoped analysis and clarification engagements are also possible. Preferably in the Bern region, or across Switzerland with a suitable hybrid arrangement.

Experience

Experience where systems meet.

From electronics and software development through architecture to business analysis: Adrian Wildermuth understands the questions on both sides of implementation.

Profile and experience
International rail transport

Traffic management and complex system landscapes

Business analysis, requirements engineering and system architecture, alongside leadership of a nearshore development team.

Distributed systems

From interfaces to operations

Experience with control systems, real-time processing and highly available systems – from analysis and architecture through deployment and operational support.

Self-employed since 2003 · Qualifications in electrical and software engineering · MAS-IT

AI and Requirements Engineering

Faster implementation needs clear business decisions.

Faster code does not answer unresolved business questions.

AI-assisted development still needs clarity about the problem the software should solve, the rules that apply and how the result will be tested. KAN Service establishes this business foundation together with those involved.

Initial conversation

What does your team need to clarify next?

Describe your starting point. The first conversation explores the support you need and whether Adrian Wildermuth’s experience fits.

Discuss your initiative