Systems Analysis skills

This skill group covers the core systems analysis activities that help teams understand, document, and improve how data and entities behave across enterprise and SAP landscapes. It focuses on two complementary areas: the internal lifecycle of an entity (states, events, transitions, guards) and the external requirements for data crossing system boundaries (what data, in which direction, under what conditions, with what quality and error handling).

The skills here are designed to be used by humans and AI agents together. Each page includes decision rules, templates, quality checklists, and explicit agent instructions. They are not framework encyclopedias. They are methods for producing reviewable artifacts and making defensible decisions before design or configuration begins.

• A sales order, business partner, or material master is stuck in an unexpected status and you need to understand how it got there.
• You are designing a new interface and need to define what data crosses the boundary before technical design begins.
• An incident reveals a race condition between parallel workflows or statuses for the same entity.
• A data quality issue at a system boundary is recurring and the root cause is unclear.
• You need to validate that a new document type or workflow has no deadlocks, invalid states, or missing transitions.
• An AI agent is helping you produce analysis artifacts and you need structured instructions to guide its output.

1. State and Lifecycle Analysis maps the internal behavior of an entity — the states it occupies, the events that move it, and the guards that protect each transition.
2. Interface Requirement Analysis defines what data crosses the boundary when that entity or its related data must move to another system.
3. System Context Mapping (from Architecture) provides the surrounding system boundaries that both skills operate within.
4. Process Analysis (from Business Analysis) provides the business process context that gives meaning to the states and transitions.

These skills are often used alongside System Context Mapping, Process Analysis, and API Integration.

• Architecture — System Context Mapping defines the boundaries; Systems Analysis defines the behavior inside and across those boundaries.
• Integration Architecture — API Integration and Interface Ownership turn interface requirements into technical design and operational accountability.
• Business Analysis — Process Analysis and Requirements Elicitation provide the business events and stakeholder needs that drive both lifecycle and interface analysis.
• SAP AMS — Change Impact Analysis and Incident Triage use lifecycle and interface maps to diagnose failures and plan corrections.

This skill group is a public working interpretation of systems analysis practice. It is not official BABOK, UML, or SAP documentation. It focuses on the subset of systems analysis work that produces immediate, reviewable artifacts for enterprise and SAP support contexts. It does not cover detailed formal modeling, simulation, or comprehensive enterprise architecture. Use these skills as structured starting points for lifecycle and interface analysis, not as authoritative framework substitutes.