Answer.

System analysis tools and methodologies allow for clear structuring of requirements and facilitate communication between all project participants. The main tools include:

• UML Diagrams (Use Case, Class, Activity): Allow for the structuring and visual representation of system requirements and architecture.

• BPMN Diagrams: Used for describing and optimizing business processes.

• User Stories, specifications and requirements in Gherkin format: Suitable for Agile projects, providing maximum detail of expected behavior.

• Traceability matrices: For monitoring compliance of implemented functionality with requirements.

• Confluence, Jira, Enterprise Architect, Draw.io: Platforms and tools for storing and visualizing requirements and facilitating collaboration.

The choice of tool depends on: the complexity of the product, the type of project (waterfall or agile), the maturity of the team, and the modeling task (describing processes, scenarios, classes, data).

Trick Questions.

Are UML diagrams and BPMN interchangeable tools?

No. UML is used for modeling software architecture (systems, classes, interactions), while BPMN is for describing business processes. They serve different purposes and complement each other.

Is it mandatory to use graphical diagrams in every project?

Not necessarily. In some small projects, textual descriptions or user stories may be sufficient. For complex integrations, graphical models help identify connections.

Is User Story the same as Use Case?

No. A User Story briefly describes the user’s need and business value, while a Use Case details interactions between the user and the system. Use Cases are used for more in-depth analysis of processes.

Typical Mistakes and Anti-Patterns

• Overloading documentation — creating complex and confusing diagrams without business value.
• Incorrect choice of model for the analysis task (e.g., BPMN instead of UML where architecture is needed).
• Storing requirements descriptions in different unconnected places.

Real-life Example

Negative Case: The team describes processes only in plain text, without diagrams. This leads to confusion in approvals, frequent misunderstandings between developers and business. Pros: Tasks are documented quickly — cons: Many clarifications, incompleteness of requirements, bugs at interfaces.

Positive Case: The analyst builds BPMN for business processes, Use Case diagrams for user interactions, maintains the relevance of models, stores them in a shared repository. Pros: Stakeholders quickly understand the logic, errors decrease — cons: Requires knowledge of tools and time to learn them.