REQUIREMENTS define the needs of the PROJECT(S) to provide best of its utility and benefits.
If they aren’t clear or analysis is not done properly, it might lead to failure of the project no matter how good the concept and design is.
Just as a system is composed of various functionalities, requirements too are identified in various forms. This categorization of requirements makes analysis process much simpler and clear for all the involved stakeholders. As per BABOK, the requirements are primarily categorized as:
A Simple Approach is to visualise 'prototype' the complete process and start step by step.
See Example below (Credit: Surbhi Mahnot)
When you plan to cook a meal, you first take in account for whom you are cooking. Is it for yourself or for your family or the kids? These define your Business Requirements. Once you decide this, you figured that you will sip wine along with the food and the kids won’t eat spicy food (stakeholder’s requirements). Next, you get all your ingredients for the meal (functional requirements) and you might also take in consideration the time you require to prepare the meal and preparation required for serving the food (Non-functional requirements). Finally, you prepare a delicious meal 'penne arrabbiata pasta, topped with oregano and basil leaves' (Technical requirements).
Contact us, if you want to know how to identify Enterprise Requirements for any Project using the Right Approach.
Would you like to be a sought-after business analyst?
We suggest you enrol for our BA Career Coaching.
Contact us at Jadetan Enterprises Ltd;
Tel: 0844 884 5311
Email: firstname.lastname@example.org or permalink: http://jadetan.com/bacareer
Website: http://www.jadetan.co.uk or http://www.jadetan.com