eSignature Business Requirements Document Template (BRD) Made Easy

List company document

my name is Terry Reiber and I'm going to take you through a quick overview of what a typical business requirements document would look like a business requirements document is what business users and business analysts would use to document the requirements for software that they are going to build or perhaps they were going to purchase from a vendor so I'm just going to go through this document really quickly and show you typically the sections that you would find in this style document the first page is obviously the title page here we say that it's a business requirements document and this document that I have here I'm showing the requirements for a Business Association website so a Business Association I would like to document the requirements to create a website for the Business Association and again you'd usually have the author the date and some versioning the next page is typically the table of contents of what's in the document the third page would be amendment history of version 1.0 and then if later on a future date you create another version you have version 1.1 1.2 etc etc typically you would have an overview section and this is an overview for a Business Association website so it basically just says that's what we're doing and we're going to document some functional and non-functional requirements the next section is a list of stakeholders and these are individuals who would be affected or impacted by building or having this website built it's a list of stakeholders I have a separate video that goes into how to come up with a list of stakeholders so I won't spend too much time here but these are the people are essentially going to we're going to give you the requirements that are going to end up in this document we also have a scope section where we talk about the business processes effect I won't go into that too much right now probably create a video later on to address that which applications are affected in this case basically we're talking about you know members wanting to sign up for the Business Association and a few other things okay here are the functional requirements now I have a separate video which you can look up that talks about how to do functional requirements in detail but this is basically a list of it's like a wish list of what the users want in the system in this case it's a Business Association website so for instance they want a home page you see this first requirement that lists the purpose of the organization they're going to have for instance Fr 0:06 a Contact Us page so this is really their their list of what they want to see in a software solution and in a big project you know you could have obviously more than five or six stakeholders you could have 20 30 50 state quarters I've worked on projects...