Save Different Required with airSlate SignNow

Save different required

hi everyone and welcome back to my channel so in today's video I'm so excited to share the 4 different types of requirements as defined by AB a Bock so for those of you who are unfamiliar with Babic it actually stands for business analysis body of knowledge so basically it's a framework that you can use in order for you to facilitate or to help your understanding throughout business analysis phase of an implementation or a project so as you're aware these requirements are typically conducted at the beginning stage of a project or an initiative so these different types of requirements need to be captured and documented throughout your business analysis stage in order to really ensure that you are actually solving the problem that is stated by the business or your customer so I'm very excited to share today's video because I have an awesome diagram that's going to show the different types of requirements and what they're used for and some of the examples as well so I'm not just going to talk about what those four requirements are but I'm going to also talk about what are some of the real examples and how they're defined in bad luck as well so if this is something that you want to find out more and then just keep on watching I mentioned before there are four main different types of requirements starting with business requirements stakeholder requirements solution requirements and transition requirements however in this diagram there's two more requirements and those two requirements are called functional requirements and non functional requirements the reason why I didn't mention these two requirements before is because they are actually subcategories under solution requirements so when we talk about solution requirements we actually talk about both functional and non-functional requirements that make up the solution requirements and as you can see from the top we start off with business requirements which is more at the high level and then as we go down towards the bottom where functional non-functional and transition requirements are these are very specific requirements so we start from top very high level and then we work our way down so when we do our analysis we normally start off with business requirements and then we move into stakeholder solution and then into transition requirements so now let's take a look at the diagram essentially the definition of business requirements is statement of goals objectives and outcomes that describe why a change has been initiated this can apply to a high level enterprise or it could be a specific business area or a project or initiative basis business requirements are typically high level business goals and objectives as I mentioned before so an example can be such as we would like to automate our vendor management system so that we can streamline end to end process it so that the vendor lead time is reduced by 50% in the next 12 months so next next one is stakeholder requirements as you can see business requirements must support stakeholder requirements and essentially stakeholder requirements is describing the needs of stakeholders that must be met in order to achieve the business requirements for example it can be such as we would like to have a mechanism to monitor the response time for each and every vendor process on a daily basis in order to reduce the lead time the report should be generated daily monthly or on ad-hoc basis in order to monitor this trend so there can be various types of stakeholder requirements but it is important to remember that business requirements must support stakeholder requirements and stakeholder requirements are achieved by business requirements in this in this cycle okay the next one we're gonna move on to business rules so business rules are policies that direct and constrain the organization so it can include different types of policies calculations authorizations limitations any triggers or constraints so these business rules actually directly influence solution requirements so when you're trying to come up with solution requirements or when you're brainstorming for ideas for your solution requirements you have to take business rules into account because there might be some functional or non-functional requirements that may have to be tweaked a little bit or change in order to accommodate business rules so solution requirements refer to the expected features and behavior of the system or product it describes the capabilities and qualities of a solution that meets the stakeholder requirements they provide the appropriate level of detail to allow for the development and implementation of the solutions so as I mentioned before there are two main types of solution requirements which are functional and non-functional so the functional requirements are what's expected features of the system or a product so it could be things I stirring a new user making a bid online using vendor self-service and being able to print various types of reports etc but as you can see it could be a list of anything because functional requirements essentially refer to the question of what must the solution do so if there is any specific feature or enhancement that you're looking for in this specific product then you have to make sure to capture them on the other hand non-functional requirements are the requirements which are related to the behavior the system so conditions of the environment in which the solution must operate so this includes privacy compliance security and access documentation usability and traceability accessibility some of the examples could be really page should load in five to ten seconds or how often the information is going to be saved when a new vendor enrolls or data security so any of these requirements can be classified as non-functional requirements under the solution requirements last but not least we have transition requirements so these are unique in nature because they describe the capabilities that the solution must have and the conditions the solutions must meet in order to facilitate transition from the current state to the future state so it's only going to be available for the interim period but once the change is complete then it's no longer going to be needed so it's very temporary in nature examples are things like user cheat sheet data migration from old system to the new system so these are transitional requirements that must be thought of or prepared before we have or implement a new process or a new change but once users become familiar with the system they no longer one day will gonna require cheat sheets right because they're going to be accustomed to the new system and the same thing with data migration once you move data migration from an old system to the new system then you're not going to require this data migration because everyone's going to adopt the new system and they're going to input the data in the new system so this is why these two examples are good transition requirements so I wanted to share this one page of diagram with you because these are some of the models or diagrams that business analysts can use in order to help throughout the process of business analysis as well as capturing requirements so once we gather requirements we can often put them into different diagrams in order to help us with our understanding and confirm that we have we have a pretty solid understanding of what the requirements are so under the solution scope I am most familiar with business process model and use kiss use case diagram so I'm gonna in the follow-up meeting I'm going to talk about a business process model specifically because there are just so many different aspects that I want to include in the follow-up video but I just wanted to give you a sense that throughout this requirements phase there are so many different types of diagrams that you can utilize and things like user personas user stories workflow model wireframes reports non-functional requirements functional requirements these are all the techniques and diagrams that you can utilize in order to help you solidify your understanding of the requirements in order to minimize the gap between your understanding and what the business expects in the future so and so I'm not going to go into details about what these diagrams or techniques are in today's video I just don't have enough time to go over everything here but what I'm gonna do is I'm gonna hand pick some of these diagrams and then we're gonna do a deep dive in the follow up videos so it for today's video I hope you guys found it useful if any and if you guys have any specific questions please feel free to comment below and and I'll talk to you guys later bye