The Community Blog for Business Analysts

Heta Raval
Heta Raval

How to write an effective Approach for Requirement Analysis

It is essential to write an impressive approach which helps you to make a client convinced about your understanding of his requirement. The satisfactory approach would help you to be on the same page with the client. So, your chances to get the contract/project would raise. In order to provide a technical solution, a business analyst needs to recognize the demand and purpose of the business.


The approach writing focuses only on the process to achieve the business requirement. Here are some significant steps to write an authoritative approach.


  1. Identify the Core requirement
    • Once the analysis part, the first step while writing an approach shall be the identification of the heart of the requirement. Write the basic understanding with the core identification of the scope of business.
    • At the first stage of an approach, the client should feel satisfied enough from our understanding of the core part of the requirement. The client should feel that we would provide an essential solution.
    • Explain the basic functionalities of the proposed business in such an impressive and in a brief way. Nowadays people don't like to read long phrases, explanations, understanding for the same points. Therefore the scanty strategy is adapted to impress the client.
  2. Appoint Business Cases
    1. Identify the possible business cases which are obligatory to consider to achieve the solution. List down all the business cases and divide the requirement into individual modules.
    2. These modules shall be providing the explanation/understanding of the relevant functionalities.
    3. These business cases shall be written in such a way, that it covers the need of business cases with their risks and benefits. The business cases are going to be the base of the requirement. Therefore they shall be written clear and concise sufficiently as they will be used to communicate the intended audience.
    4. Include different types of business case diagrams wherever require, which would provide the acceptance as “Short and Sweet” judgments that would be helpful to highlight the work done from your side.
  3. Solution Evaluation and Implementation
    1. Once all the business cases are defined, one should write up the way of how those cases will be implemented. Write solution for each business case that how it is going to be implemented, which technology will be used and why. Also, write about the reasoning for the selected strategy as a solution chosen.
    2. The workflow shall be written as a guideline in a seamless and obvious way to a non-technical reader as well.
    3. The workflow shall be clear and precise that would help to win the client’s mind with an impressive way. As being a service provider, you should be able to convince the client that you have thorough knowledge about the problem which the client has and you will provide the perfect solution.
  4. Core Assumptions
    1. It is essential as well to keep a ball in your court. Therefore, each and every assumption shall write in the approach. With these assumptions, you are clearing all the crucial points which match the client’s requirements but, which are not clearly mentioned by the client.
    2. Why the assumptions are necessary is because they are offering a faith of you to be true in the future.
    3. Make assumptions based on the knowledge you have, your past experiences, and the information is available from the client.
    4. They are anticipated conclusions or circumstances which are expected to occur during the project's life cycle.
  5. Relevant & Required Queries
    1. One should ask all the doubts and queries for the unclear functionalities and workflow.
    2. Being a service provider, you should ask queries which are related to the functionalities and for the project. The queries should be specific, relevant, and easily recognizable.
    3. Always include polite and kind words in the queries, when you are requesting if something is totally not clear or you need the client’s inputs.
    4. The queries shall be written in such a way that after, you are totally clear with all the functionalities related to project. More relevant queries would show good analysis practice.


Concluding Considerations


The project proposal approach shall be the one such document which covers all the elaboration for requirement analysis with evaluation, assumptions, and queries. It must be convincing and impressive enough as per the document’s name suggested, you are going to approach someone with whom you want to collaborate your work. With the conclusion, an approach should be precise, simple, and qualified to achieve the desired project.

This entry was published on Aug 16, 2019 / Heta Raval. Posted in Requirements Analysis (BABOK KA) . Bookmark the Permalink or E-mail it to a friend.
Like this article:
  12 members liked this article

Related Articles


Omar posted on Friday, August 30, 2019 1:08 AM
Very Well Written!
DATYRA posted on Friday, October 18, 2019 9:38 AM
The approach writing focuses only on the process to achieve the business requirement. Here are some significant steps to write an authoritative approach.

Heta Raval posted on Monday, October 21, 2019 4:03 AM
Thank You for the appreciation.
Heta Raval
Only registered users may post comments.

Modern Analyst Blog Latests

As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...
Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...
Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN


Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.


Copyright 2006-2024 by Modern Analyst Media LLC