Systems Analyst & Systems Designer

I make
complexity
buildable.

I translate complex business rules, organizational constraints, and raw ideas into coherent, implementation-ready software systems.

THE PRACTICE / 2026

Business understanding.
Engineering precision.

Inside my practice

A little less ambiguity.
A lot more structure.

Select a stage to explore the process.

03 / Find the structure

Connect processes, states, domain concepts, and system boundaries into one coherent model.

Banking systemsDomain expertise
AuthorizationDesign strength
RequirementsProblem framing
ArchitectureTechnical structure

01 / Selected work

Complex problems. Clear architecture.

Three perspectives on turning business constraints into systems that teams can build.

01

Authorization Architecture

Authorization & Access Management

Connecting organizational roles, contextual scope, and application permissions across service and interface layers.

Role mappingAuthorization flowData structure
Explore case study
02

Banking Systems

National Cheque Services

Refining banking services integrated with national cheque-clearing and verification platforms under regulatory constraints.

Service lifecycleValidation matrixAPI specification
Explore case study
03

Systems Analysis

Digital Identity Systems

Turning complex stakeholder requirements into shared process, domain, data, and service models across business and engineering teams.

BPMN / UMLDomain modelERD
Explore case study

02 / From the field notes

All writing
LATEST ARTICLE
Authorization Architecture

When RBAC Stops Being Enough: Role + Unit + Context Without Role Explosion

Separate capability, organizational scope, and runtime context in a practical authorization model, with interactive diagrams, a role simulator, and policy traces.

Read the field note

03 / How I work

Clarity is a design decision.

A disciplined path from the first unanswered question to implementation.

01

Structure ambiguity

Clarify the real problem, actors, assumptions, rules, exceptions, and missing decisions.

02

Design the system

Model processes, data, interfaces, authorization, states, and system boundaries.

03

Make it executable

Produce specifications, diagrams, service behavior, and acceptance criteria teams can implement.

04 / Experience

A practice built across disciplines.

Business, product, analysis, and technical design inform the same practice.

01

Sadad Informatics

System Analyst

Banking systems, cheque services, regulatory integration, and cross-system validation.

02

Dotin

Software Analyst & Systems Designer

Digital identity solutions, requirements engineering, domain modeling, and service design.

03

Peyk Asa

Senior R&D / Product Development

Product shaping, feasibility analysis, feature definition, and MVP boundaries.

04

FANAP Infrastructure

Business Development & Market Research

Connecting technical opportunity, market evidence, and business direction.

Engineering interests

Questions worth following deeper.

Areas where architecture, policy, security, and system behavior intersect.

01Software Architecture
02Authorization Systems
03Requirements Engineering
04Computer Architecture
05Secure Systems
06Logical & Digital Systems

One integrated story

Different disciplines. One recurring interest: understanding complex systems.

EconomicsSystems of incentives
eCommerceDigital business systems
Computer EngineeringTechnical structure
Systems AnalysisExecutable behavior
Read the full story