-BSc (Computer Science), B Comm (Informatics/IM/Business Science), B Tech (IT/IM/FIS) or National Diploma (IT/IM/FIS), BSc Eng.(Electronic, Computer, IT)
-Experience and working knowledge of the following technologies/methodologies/notations -UML, BPMN using ARIS BPM/A or Metastorm -BPM/A, BABoK, and PMBoK/PMI.
-Experience and knowledge in areas such as: Process analysis/engineering
-Retail banking solutions
-Enterprise resources planning solutions
-Content management solutions
-Customer relationship management solutions
-Business intelligence/analytics solutions
-Enterprise systems management solutions
-Service oriented architecture solutions’
-Minimum of five (5) years IT experience and a minimum of five (5) years as a business analyst within a banking or financial services environment.
-Business analysis certification will be an added advantage.
-Basic project management principles, business writing skills, presentation and facilitation skills
-Software testing pack design, functional testing
-Customer service orientation, result orientation, conflict resolution, negotiation skills
-Time management, professional communication (written, verbal/presenting and listening) Creativeness, innovation, stress management, assertiveness, tenacity
-Must be advanced user of Microsoft Visio4
-Business case development
-Identify and highlight opportunities for improvement.
-Act as a consultant to the client on the application.
-Provide advice when a requirement is raised that does not fit in with the business strategy.
-Participate in client planning forums and advise on solutions.
-Challenge the business in their thinking, especially to understand the intent of the business requirement.
-Assist business in articulating the benefits they wish to derive from the solution.
-Facilitating the development of a Business Case; this may include a financial analysis
Customer requirements specification (BRDs) development
-Follow a structured process to understand and document client requirements.
-Facilitate activities like interviews or JAD sessions to expand the understanding of the business requirements.
-Perform analytical tasks, data extracts, run queries or any other form of analysis to gather information.
-Following up with clients to clear up ambiguity and possible misunderstanding;
-Documenting the requirements in a Business Requirements Specifications (BRS) document (which may include UML models, business process documents).
-Ensuring alignment between the Business Case and the BRS.
-Manage the quality of the documentation produced by the members in his or her team.
-Review the functional requirements with the client, using appropriate formats such as presentations and walk-through discussion.
-Obtain sign-off on BRDs.
-Conduct peer reviews of other business analysts’ requirements specifications.
Functional requirements specification (FRDs) development
-Validate the functional solution; this involves interpreting the BRD into a set of Functional Requirements Specifications (FRDs).
-Apply knowledge of the system, interfaces and dependencies to highlight integration aspects that must be considered.
-Identify a set of stakeholders that need to be involved in creating and validating the FRDs.
-Interview business and technical owners, as well as experienced members of the development/configuration team.
-Build and demonstrate GUI prototypes, to validate the designs.
-Utilize a range of techniques such as JAD, interviews, observations, questionnaires, GUI prototyping, benchmarking, data modelling, focus groups, and state diagrams.
-Highlight risks and benefits of alternative solutions.
– Provide advice to business on the impact of implementing the solution, specifically risk associated with resourcing or secondary impacts such as training needs and post-production support.
– Advise on compliance and legislative considerations.
-Identify and design a set of test cases/scripts, test scenario’s and test data sets to accompany the BRDs. Validate the FRDs and Test Basket with the client and identified stakeholders and obtain sign-off.
-Review the approved BRDs and FRDs with the development (or solution configuration) team.
-If required, revert back to client or other stakeholders if technical issues require business decisions in order to proceed