The business analyst reads your desires from your lips and translates these into requirements for development and testing.
The business analyst, next to the project and quality managers, is the third person to successfully plan the launch of your project. Without the requirement, developers and testers may sit in an idle loop.
The business analysis describes the process of illuminating
- inventory software by means of a test case analysis and functional analysis,
- of processes (process analysis)
- regulatory/legal requirements (e.g., from payment transactions or concerning Internet security standards) technical requirements (performance, robustness, throughput)
- operational requirements (scalability, robustness)
- Security and risk requirements (from reporting to hardening)
- conceptual, technical requirements (requirement engineering)
In this regard, granularity determines practicability. The requirements are the smallest dimension: The Requirement describes a function – a navigation point, a field code, a user exit, etc.
Requirements are the basis of test management to write test cases; for development, to implement them; and lastly, for documentation, to explain the function to the user.
According Specific-Group's competency model, the business analyst is the introduction, the senior business analyst and the expert describe the arc to industry and methodology experts.
The strength of business analysts is in analysing and understanding requirements: they have in-depth knowledge of the industry and can identify requirements and comprehend tests. In scrum development projects, the business analyst as project owner is the communication interface between development, quality management and client. He has excellent communication skills and can think outside the box.