Vladimir Lovtsov / Leadership notebook
#systems analysis
Practice, analysis and observations on this topic.
Articles: 11
EventStorming: Benefits, Limits, and Practice
A practical guide to EventStorming: what the method helps a team discover, where it falls short, and how to prepare a session that produces useful outcomes.
Can an Overly Detailed Specification Weaken Engineering Initiative?
A working hypothesis about the relationship between requirement detail, delivery predictability, and team autonomy.
Five Common Systems Analysis Mistakes on IT Projects
Common systems analysis mistakes on large banking and fintech projects: vague requirements, legacy integrations, regulation, failure scenarios, and late validation.
Data Exchange Formats: JSON, XML, Protobuf, Avro, and MessagePack
Choose a format through contract evolution, backward and forward compatibility, tooling, and measured processing cost rather than fashion.
UML in Practice: When a Diagram Helps and When It Does Not
Choosing a UML diagram for a specific question, defining how long it should live, and keeping modelling from becoming a project of its own.
Microservices or a Modular Monolith? A Decision Checklist
A concise decision guide based on domain boundaries, independent releases, scaling, data consistency, and the cost of operating a distributed system.
User Stories: From Need to Acceptance Criteria
How to frame a user story around who, what, and why, add testable acceptance criteria, and avoid turning it into a miniature specification.
Word of the Day: Idempotency
What idempotency actually means in HTTP and distributed systems, why a UUID alone is not enough, and how to handle retries safely.
SQL in Practice: Your First PostgreSQL Queries
A self-contained SQL exercise for analysts: create two tables and practise SELECT, filtering, JOINs, aggregates, data changes, and transactions.
Analyst Roles in IT: A Map Without a Ranking
A practical, author-defined map of analysis roles based on the subject of the work, expected outcome, technical depth, and route into the field.
How to Interview a Client When You're the Analyst on an IT Team (a Checklist)
A step-by-step algorithm for interviewing a client when there is no business analyst on the team: preparation, running the interview, analysis, and confirming requirements.
No articles found. Try another phrase or select all topics.
Short observations and new writing in my Telegram channel (in Russian).
@it_underside ↗