About the job

The systems analyst is responsible to research problems, plan solutions, recommend
solutions and coordinate development to meet the needs of business/other external
stakeholders.

The System Analyst will interact with product owners, business analysts or solution
strategists (when outsourced to business) and the QA Team. The Systems Analyst will also
be required to interact with other project team members like vendors (for systems),
project managers, project sponsors, product managers and project stakeholders.
The role will require several speciality domains as enumerated below. Each individual
project may require one or more of the undermentioned functions to be performed, and the
analyst may specialise in all or several of these functions.

Business Systems Analyst Responsibilities:
o Responsible for the analysis and design of new systems, major enhancements to
existing systems and general maintenance of systems.

o Leading and facilitating requirements gathering sessions across both the business
and technological domain to produce functional and system specifications. Ensure
that functional / systems requirements represents a common view among end-users.

o Participate in system design sessions to arrive at an optimal solution. Assist with the
identification of risks and issues within the project(s) and mitigation strategies.

o In conjunction with the Systems Architect or Developer, analyse and design:
o integration files or messages (e.g. web service definitions, XML schemas,
business functions, flat file or delimited files, API’s etc.)

o Help design and update system configurations (outside of the production
environment)

o Write SQL queries (not embedded in code), interrogate database tables for
analysis purposes and assist in designing database structures

o Analyse and participate in systems functional design sessions for ‘run the
bank’ enhancements and upgrades or migrations which require functional
expertise / analysis

o Participate in systems functional design sessions for ‘change the bank’ and
‘grow the bank’ initiatives as well as brand new products or capabilities

o Examine and analyse current process flows and recommend solutions for improving
and restructuring processes required to meet business objectives, and to address
industry changes and/or opportunities.

o Guide suggestions for appropriate solutions taking into account cost, risk, delivery
and feasibility.

o Modelling system designs to meet business objectives. These will include
behavioural and structural UML diagrams (like use case diagrams, activity diagrams,
sequence diagrams, timing and state machine diagrams, component diagrams, as
well as ERD diagrams and interface diagrams when needed).
Ensure that requirements models and analyses is done per internationally accepted
best practices (Use Case modelling and UML 2.5).

o Modelling and designing screens for usability, documenting screen flows and
designs.

o Where business requirements or user stories have already been provided, interpret
and provide system solutions to meet the requirement, along with the functional and
system documentation.

Cross Border Payments Industry Experience:
o Must have a solid understanding of traditional and emerging cross border payment
rails, like Swift.

o Must have a solid understanding of the ISO20022 payments message standards (i.e.
PAIN, PACS and CAMPT messages) as well as the equivalent Swift MT100, 200 and
900 series messages).

o Exposure to SAMOS and cross border ZAR payments will also be beneficial.

o Understands and keeps abreast of the payments modernisation industry changes.

Requirements