Senior Business Analyst IRC300504
Summary
Analyze legacy mainframe systems (COBOL) to document business rules, pain points, and SLAs, using AI tools for discovery and assessment without code changes.
Job Description
Proven ability to elicit and document business rules embedded in legacy applications.
Experience analysing incident/ticket history to establish operational baselines and pain points.
Skilled at facilitating functional discovery workshops with mixed business and technical stakeholders.
Able to define and baseline SLAs, KPIs, and success metrics for a support engagement.
Comfortable using AI tooling to accelerate analysis while verifying outputs against source data.
Work on legacy or mission-critical systems.
Job Responsibilities
Lead functional discovery workshops to map what the mainframe applications do from a business perspective.
Document critical business rules, batch dependencies, and functional pain points tied to legacy code.
Analyse incident and backlog history, using AI-assisted clustering where useful, to establish a current-state support baseline.
Define SLA, KPI, and success-metric baselines for the proposed maintenance model.
Triage and prioritize candidate use cases for the maintenance pilot by business impact.
Consolidate current-state findings into the assessment deliverables alongside the architect.
Department/Project Description
The engagement supports a maintenance assessment and advisory for a legacy mainframe environment built primarily on COBOL, running mission-critical batch and online workloads. The objective is to establish a fact-based understanding of the current application estate and its support model, and to define a scoped, low risk maintenance pilot as the basis for a potential longer term managed services engagement.
The initial advisory phase is an assessment structured in three stages: a scope-alignment workshop to agree services, ownership, and boundaries; a current-state assessment of the code estate, data, batch/online flows, operations, and ticket history to establish baselines and pain points; and a pilot-identification stage to prioritize candidate use cases and define objectives and success metrics. The phase is diagnostic in nature — it covers evaluation, characterization, and effort estimation only, with no code remediation or production changes performed during assessment. Success depends heavily on timely access to client subject-matter experts and to the target environment.