Join the social network of Tech Nerds, increase skill rank, get work, manage projects...
 
  • Factors that should be taken care while Requirement Gathering

    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 437
    Comment on it

    As per company hierarchy a Business Analyst is the person who is responsible for Requirement Gathering, he/she is the person who completely analyze the Client’s requirements with the plethora of activities with due course of time.

    There are few factors which should be taken care of while doing the requirement gathering

    • Researching the competing application : Whenever, a Client approach for any project, he has something in his mind, which he discusses with the Business Analyst. He also gives few reference applications in that matter. The main role of the Business Analyst should be such that, they should completely understand the ideas of the Client and develop it into prototype. For example, Client wants to make an E-Commerce application which have a feature of auction, in that case Business Analyst should analyze all popular E-Commerce applications like FlipKart, Myntra, Amazon, SnapDeal and so on. The Business Analyst should analyze the best features of all the apps and combine it as a whole in the E-commerce application. This as a result, helps to develop an app with an innovative idea and a fruitful product arises.

    • Analyzing the Age Group : It’s very important to target the audience who is going to use the application. For example, Dating Apps like Tinder which will be maximum used by Tenagers and Youths who belongs to the age range of 18 to 35, on the other hand middle age people and old people will partially use the dating app. In that case, it is viable that maximum targeting audience are Youths and Tenagers, therefore there are few factors which should be taken care off, for example the color schema of the application should be appealing with those age group who will be using the app, therefore a bright and appealing color should be used. This helps to give the application an appealing look and target more audience.

    • Analyzing the Geographical location : It is indeed one of the important criteria that should be taken care off. It's always better to know the geography of the place, the application should always show the touch of the locality, this may be in terms of the User Interface, special attractions and events across the vicinity and so on. For example, if we consider India, a vibrant place with wide culture, cuisine, language, so if there is an application of a restaurant to build, it should be taken care of. This in care helps the application to get a global appeal.

    • Pictorial Representation of the application : Reading is a boring job, only few have patience to go through a documentation, therefore it's better if we can represent an application in a pictorial way in the form of Wire-frames, diagrams and prototype, this helps a lot to understand the functional behaviour of the software and easy demonstration of the application. It also helps the Testing Engineers to prepare the Use Cases and Test Cases with ease as well as Project Managers and Software Engineers can easily understand the functional requirements.

    • Explicit and Implicit Requirements :  This is one of the important part of Business Analysis process. Explicit Requirement are those, which are cleared and provided by Client / Stakeholders on the other hand, Implicit Requirement are those which Business Analyst should take care of. For instance, let's say there is a registration form with a field First Name in this case the Explicit Requirement is that, it’s a compulsory field on the other hand, the implicit requirement includes, it should be alphabetic, it should have a limitation and should not contain special characters and so on. This Client won’t ask for but it's the role of Business Analyst,  QA engineers and Project Managers to determine it and execute it for an appealing output.

    • Determining the Risk Factor of a Project : Some projects may be simple and some may be challenging. Challenge on the sense means the risk factor involved in it. Analyzing the risk factor in the beginning of the project is the criteria for successful project completion otherwise lead to chaos and ambiguities later on. So, this should always be considered. For example, there is an iPad application of an ECommerce app where it helps the user to design his own T-Shirts with a customized design toolbar. In this case the developing of Custom Toolbar with attributes for T-Shirt design is a risk factor. Therefore, it's better to determine the risk factor in the beginning of the project, develop a prototype of it so that it can be implemented in the project.

     

 0 Comment(s)

Sign In
                           OR                           
                           OR                           
Register

Sign up using

                           OR                           
Forgot Password
Fill out the form below and instructions to reset your password will be emailed to you:
Reset Password
Fill out the form below and reset your password: