The Business works as a liaison among stakeholders in order to elicit, analyze, communicate and validate requirements for changes to business processes, policies and information systems. The business analyst understands business problems and opportunities in the context of the requirements and recommends solutions that enable the organization to achieve its goals.

The business analyst consulting is a vital role in any program or project. The analyst will cover no less than:

• Analysis of the business requirements be they operational, departmental, divisional or organizational.

The Kleiter Consultancy business analyst will source information from the customer’s organization and, where required from third party suppliers and customers. To be more specific:

Functional Requirements describe what the system, process, or product/service must do in order to fulfil the business requirements. These are often referred to as System Requirements although some functionality could be manual and not system based, e.g., create notes or work instructions.

See the 4 key core activities of business analysis:

• User Requirements are a very important part of the deliverables; the needs of the stakeholders will have to be correctly interpreted. This deliverable can also reflect how the product will be designed, developed, and define how test cases must be formulated. The Business Analyst will record requirements in a Requirements Management Tool; This will be done in a simple spreadsheet and / or a log-issue server application.
• Non Functional Requirements are requirements that do not perform a specific function for the business requirement but are needed to support the functionality. Like: system / user performance, scalability, quality of service (QoS) and SLA (Service Level Agreements), security and usability. Report Specifications define the purpose of a report, its justification, attributes and columns, owners and runtime specifications.
• The Traceability Matrix is a cross matrix for recording the requirements through each stage of the requirements gathering process. High level concepts will be matched to scope items which will map to individual requirements which will map to corresponding functions. This matrix should also take into account any changes in scope during the life of the project. At the end of a project, this matrix should show each function built into a system, its source and the reason that any stated requirements may not have been delivered.
• The Business Analyst is involved in User Acceptance Testing (UAT), including developing the UAT Plan and UAT Script. This UAT information will feed the Mid Stage Assessment & End Stage Assessment in the project.