Business Analyst

Avatto > > DATA SCIENTIST > > SHORT QUESTIONS > > Business Analyst

Case studies usually require you to give a detailed analysis of the situation and to recommend possible future action or a new design. Your marker is looking for how well you analyze the situation and provide a realistic solution to the issues/problems.
Your marker would also look at the quality and reasonableness of your recommendations. Reasonableness includes that the recommendations could be achieved taking account of resources such as time and money. There are often many solutions to a problem but giving all possible solutions loses marks in a case study situation because it is considered unrealistic.
Your course description of the task should contain guidelines on the types of questions to ask when analyzing the case along with other issues/possibilities to consider in your analysis and discussion.
UML stands for Unified Modeling Language. It is the standard in the industry for visualizing, documenting, and constructing various components of a system.
The purpose of an activity diagram is to provide an outline of workflow in the business, including the action and activities that are completed. For example, with a company, there is likely to be more than one department, with various access levels to the system. If there are departments including HR, Medical, and Accounting, they only have access to the screens that relate to their work. An activity diagram will be used to highlight the differences in the departments, which is extremely helpful for developers when they are coding and designing.
These types of questions are always on the list. Do prepare for such questions as descriptive as possible. The sample answer could be “I have a good combination of strong technical skills, and the ability to build strong customer relationships. This allows me to use my knowledge and breakdown information to be more user-friendly”
The golden rule to measure the quality of a good requirement is the ‘SMART’ rule. According to this rule, a requirement should be:

Specific: The requirement should be specific so that it could be properly documented

Measurable: We should be able to measure the success criteria of the requirement by different parameters

Attainable: The requirement should be possible to attain with the given resources

Relevant: The requirement should be in line with the project’s business case

Timely: The requirement should be posed in time i.e. early in the project life cycle.