hello everybody and welcome today we will be talking about uh SRS what is SRS how to create SRS and why we use SRS please watch this video till end so that you can have a better understanding of SRS clear requirements help development teams create the right product and a software requirement specification helps you lay the ground work for product development we will Define what this is when you would use one and five steps to write an SRS document what is a software requirement specification document a software requirement specification is a document that describes what the software will do and how it will be expected to perform it also describes the functionality the product needs to fulfill all stakeholders needs for example business or users a typical SRS in includes a purpose and overall description specific requirements the best SRS document defines how the software will interact when embedded in Hardware or when connected to other softwares good SRS document also account for real life user so now let's review the reasons for using SRS SRS describes how a software system should be developed it provides everyone involved with a road map for that project SRS in software engineering creates the basis for all documentations it sets your communication on the right track it helps you understand the product SRS documentation helps to grow your development standards it helps to cover risk on each development stage so there are five steps to create SRS a good SRS the number one is start with outline then clarify project overview then understand users and project risks detail the project requirements and get the SRS approval at the final stage so let's discuss about the SRS outlines as always it is important to make your document structured and focused this will help your Outsourcing development team avoid unnecessary effort in Reading project requirements back and forth as a result it will reduce the risk of missing information across the teams you should also ensure the three main parts of the SRS including introduction overall description and detailed features at requirements to create a good Outsourcing software document now let's take a look at an outline example here the first thing is Introduction within introduction you can write project purpose project scope glossery and reference the second is overall description where we can write user needs assumptions and dependencies and the third is detailed features and requirements where we can write actually the functional requirements non-functional requirements external interface requirements we'll go into detail of all these one by one so let's start with introduction in introduction we clarify the project overview starting the SRS with a clear introduction to describe the project purpose and give readers an overview of the project big picture the introduction should cover the following content the number one is Project purpose what is the project built for answer this question to help the readers understand the aims and objectives of the project the second is Project scope what is the business goal what values does the project deliver find the answer to these questions to make clear the project sophistic ation glossery and reference explain the terms used in the document show your references to readers to consolidate the transmitted information so the next is overall description here we understand users and project risks all developing effort is to ensure that the project is completed and meet the user expectation to achieve this success you need to pay enough attention to analyze user needs Define your software's end user and how they use it correctly understanding the users's needs will give you a clear Direction on how your software should be built assumptions and dependencies think of assumptions and dependencies that might impact fulfilling the requirements outlined in your SRS and take not note of external factors for example software components reused from another project this is to prepare for any upcoming challenges in the project implementation and reduce the risk of project failure so now about features and requirements where we can actually write the project requirements in detail clear requirements can be considered as keys to the project deliverables in general and the project success in particular the more specific requirements the easier it will be for the developers to plan and implement the project requirements are various but mainly divided into functional requirements non-functional requirements and external interface requirements each type of requirement needs to be specified direct and differently so let's talk about functional requirements functional requirements describe what the software will do and Define how it will function to meet user expectations you should also mention the acceptance criteria for these functional requirements to determine if a function is completed and performs as expected non-functional requirements non-functional requirements include usability performance software Quality Security and so on they can be seen as extensions help describe how the software will perform external interface requirements external interface requirements are types of functional requirements and these interfaces include user software Hardware system communication interfaces Etc so the last thing is get the SRS approval to ensure the SRS accuracy and objectivity and the mutual agreements in how the software should run the key stakeholders should be involved to approve the SRS by doing this you can reduce the risk of wasting time effort and money in the future unnecessary changes so as a final thought the SRS is important because it gives you a source of information where you can easily manage requirements throughout the Outsourcing software development process in this video I aimed to help you get the basic ideas of the SRS structure and Hope hopefully I did it thank you for watching