Home / BA (page 6)

BA

FISHBONE DIAGRAM

FISHBONE DIAGRAM HISTORY Dr. Kaoru Ishikawa,A Japanese quality control expert has invented the fishbone diagram to help employees.To avoid solutions that hardly address the symptoms of a much larger problem. INTRODUCTION A fishbone diagram, also called a cause and effect diagram or Ishikawa diagram.it is a visualization tool for capturing …

Read More »

HANDLING CHANGE REQUEST AS A BUSINESS ANALYST

Business Analysts should be aware of handling change requests at any point of time. It is very obvious that the Requirements are inbuilt to change and it will continue throughout the life. It is because people change their minds, tastes etc over day to day life. Let us suppose that …

Read More »

OBJECT ORIENTED APPROACH

LEARNING OOA CLASS: A class can be defined as a skeleton for an object or blueprint for an object or template for an object. A class defines all the variables and methods, an object should have. An object is an instance of a class. Consider an example, let ‘fruit’ be …

Read More »

What Are Use cases?

In my opinion, or you can say that in an easy manner a use case is a technique that captures requirements for a software application. If you have analytical mindset then this work is for you. But still, the question is same that what is a usecase and how to write them …

Read More »

Requirement Traceability Matrix

The Requirements Traceability Matrix is a document that maps and traces user requirement with test cases. The basic  purpose of the Requirements Traceability Matrix is to ensure that all requirements defined for a system are tested in the particular test protocols. A tool is used by the validation team, to ensure that the …

Read More »

Competencies of a Business Analyst

The basic definition of Competence is the ability of an individual to do a job properly. A competency is a set of defined behaviors that provide a structured guide enabling the identification, evaluation and development of the behaviors in individual employees . When it comes to the ability of  business analyst, …

Read More »

NEEDS VS. REQUIREMENTS

NEED: A need is something that is important to your organization or your users. Some examples of a need are: To show my board that our fundraising income has increased. To track my communications with major gift prospects. To send emails to my organization’s contacts. While articulating your organization’s needs …

Read More »

Tips for Requirement documentation

1) For good requirement documentation we should define one requirement a time. Don’t use any conjunctions like AND,OR,ALSO,WITH and THE LIKE and also avoid using let out classes like but, except and if necessary. Because words like there can cause developers and testers to miss out on requirement. We can …

Read More »

RISK ANALYSIS & MANAGEMENT

RISK ANALYSIS & MANAGEMENT Any uncertainty event (Flood, fire, rains) or condition(unavailable of resources or theft) that may impact the cost, technology, scope, time, quality is risk analysis. Risk analysis is done to determine how much more the project carries more risk and if the organisation has the capacity to …

Read More »

Stakeholder Analysis

Stakeholder analysis is an important process during requirement gathering which helps to identify the stakeholders and analyzing their needs. Stakeholders can be grouped into 2 categories: Internal stakeholders and External stakeholders. Internal stakeholders are internal to organization like a sponsor, the project team, program manager, admin manager, etc. They might …

Read More »

Watch Dragon ball super