Quality is the primary business differentiator in IT. Studies such as the Chaos Report (disorder) show that the most common cause of low quality is having inadequate, or poorly understood, requirements of customers thoughts. Other common causes are poor design, unmanaged code, and improper installation method. We always must remember the prevention of defects is the best cure in any project. Also, identifying and fixing the defects/errors/mistakes as early as possible is critical. Some of the duties and responsibilities for doing that falls on the Business Analyst (BA).
Therefore, concentrate initially on the validation techniques for correct planning:
- Client requirements and understanding the needs
- Keep the system at the business level (functional and usability testing)
- Communication acceptance (understanding)
- Business purpose (stakeholder satisfaction with the production product)
This Report is a piece of simple information you to learn the importance of achieving quality and your role in doing so. You must understand the project and product factors affect the two components of risk (likelihood and impact). Also, you must learn to apply those to various real-life validation situations using a case study and practicing testing decision-making.
You can have an idea of the following techniques:
- Validating requirements or checklist or any text-based product (such as procedures or plans)
- Testing functional and manual requirements
- Assessing and testing usability
You have to plan functional and usability testing at the business level and the essential elements to document that planning. You can examine your role in Acceptance, including Acceptance of an outsourced product, and you have to determine how to assess stakeholder satisfaction with the product in production.
Exercises in risk assessment and all the primary validation techniques are an integral part of this info.
While the involvement of BAs in testing varies widely across companies, this Report assumes maximum participation at the business level (excluding nonfunctional testing except for usability). Each member can tailor the content to suit a specific company's policies.