Describe your experience working as a systems analyst: what artifacts did you create, how did you work with requirements?

As a systems analyst, I was involved in gathering, analyzing, and documenting system requirements. The main artifacts I created included:

• Technical specifications (TS) — detailed descriptions of functional and non-functional requirements.
• UML diagrams (e.g., use case, class, sequence diagrams) for visualizing processes and system structure.
• User Stories and Acceptance Criteria — for Agile projects, to describe requirements from the user's perspective.
• Requirements traceability matrix — to track the compliance between requirements, tests, and implementation.

The work with requirements included:

• Meetings with clients and users to clarify and agree on requirements.
• Business process analysis and identification of bottlenecks.
• Prioritization of requirements jointly with the development team and the client.
• Maintaining the relevance of documentation during the development process.

This approach helped ensure transparency of requirements and reduce the risks of misunderstandings between the business and developers.