Dear Students, Welcome to Gate Smashers. I am going to explain in this video. Software requirement.
And as you know software requirement is the first step of the software development life cycle. and in which we talk mainly about the different requirements. Such as What are Functional Requirements?
What are Non-Functional Requirements? What are the user's requirements? What are the System Requirements?
Even software requirement specifications, What is an SRS document? What is the feasibility study? Apart from this, information gathering, Analysis, all these things, all these topics comes under software requirements.
So I will, See, all these topics are theoretical, but I will explain them to you by relating them to a real-life example. So guys, immediately like this video & subscribe to the channel, if you have not done it yet. And if you have done it, then you can subscribe to it from other devices and also share it.
So see here, It is a description of the features and functionality of the target system, means what system do I have to create? The client has come. The client is approaching a company.
Let's say, I have a company, a client came to the company that I have to make this system. Now the target system is, What features should it have? What characteristics should it have?
What should be the functionalities? On that, we talk here in the description. That means all of its descriptions are written here, okay.
This means here in the first step everything is documented, This means bringing the things into documentation, which means in writing. As we say, things in writing. The implementation will be done later.
Designing, implementing, testing, etc. are later things. Elaborate the things first.
it is the description of what the system should do. This means what will the system do? We'll talk about that here.
And all these steps here called Requirement Engineering. This means the requirement, We say, okay, we have this requirement, we need this thing. We need that things, But this is the whole engineering in itself It is an art to do the thing Properly.
This means we don't do things casually. We have to do it formally. See, Why not do it casually?
Because it is a building process, later on, they will design the system, then they will implement, test & launch. Brother, if any problem will come at that time So we can finish that thing on the first step. This means, If a building is to be built, then the foundation is first laid in the building, and the base is made.
so that thing is this. If there is a problem in the base, there is a problem in the foundation. So the problem will definitely come in the future on the top.
So that's why it is a complete engineering in itself, it is an art. If we're talking about this, the requirement engineering, It refers to the process of defining, documenting & maintaining requirements in the, It is the same thing, making things properly, defining them, and maintaining them. so that my target system becomes what I designed today, all the things I wrote today.
It is a four-step process. means it has four processes in it. First, feasibility study.
What does a feasibility study mean, Is your system feasible? Is it worth making or not? These things are our first step.
See, The man who is coming to me. Anyone who is approaching the company. So he has a raw idea.
Something pops into the head that I want to make this thing or do it like this. So based on this idea, analysts are Like business analysts Or strategy analysts or IT analysts. First, They will listen to him.
There are the stakeholders or clients or users, they will listen to him first. And then in a way, they will think That yes man, are these things feasible? Technically this thing is feasible or not.
Or cost wise Or time-wise. It is not that the technology will change by the time it comes onto the market. Many things have to be taken into consideration & its feasibility has to be checked.
Like, I give you a simple example. Elon Musk He must have thought of the idea of Self-driving cars. Now when the idea came to his mind, to build a car that drives itself So it must have crossed the mind of many people, has he gone mad, can such a thing be made?
But if you look at today's time, then such things are already running outside. It is not running in India. Coming to India is also a bit of a challenge in itself.
because there are so many samples here, who will drive at a speed of 20 on the highway & in the streets, they will drive at aspeed of 80. So somewhere, it will be very challenging in India. But In the feasibility Study, Let's assume that the mindset has to be kept that nothing is impossible only then you can think in a little broadway.
Let's think it is feasible, that yes This system is feasible, cost-wise, and everything-wise means it can be made. Then, requirement gathering. This is a very important phase.
Requirement gathering and elicitation. What does it mean? Now, gather the things.
Now you gather the information, gather it from the client. What does the client want? Gather from the stakeholder.
What does the user want? And then sit in the company and do proper brainstorming. Can these things make?
This is the gathering phase, This is all a phase of gathering the information in a way. This is a very important phase because this is where your story mainly starts. Then Software requirement specification.
I mean, I've gathered the things. I gathered the information. I conducted different interviews.
I conducted the services. I also did brainstorming. I have done the meetings.
I have done a lot of conferences. I did a lot of things. With the stakeholders, with the clients, and with the users.
And after bringing everything to mind, I thought, yes man. some of my things can be done like this And then I wrote it in an elaboratic well defined way and it is called Software Requirement Specification (SRS). I have made a separate video on this, its link you will find in the above suggestive video or in the description.
So definitely check it, because it is a main topic in itself. The rest is the theory It will end here only. But this is a main topic in itself, it is a separate topic, which is often asked, okay.
You will do that separately. Then Software Requirement Validation. I defined everything properly, wrote it properly, and made a document.
Now we have to validate means to check its accuracy & all those things. So that it can be finally signed. And then start working in the designing phase.
So it's a way to validate things, Properly Check the things. One thing more goes along with it. That's software management.
Software Management. We call it Software management or also call it, software management requirements or specifications. What does software management mean?
You're managing things. You're changing, & updating things on your end. So proper communication is necessary.
Communication is most commonly used in this phase. Communication means interacting with each other. Whether it is the people within the company who will work on that project, Or communication with clients communicates with stakeholders.
Regular communication is very important. And based on that communication, You will come to a proper document, then the final work will start. This is a very important point.
Tool support for the requirement. Now all the requirements that you are doing, how will you do that, for that you need some tools or some other methods. So we have those methods, such as observation report, user observation means what the user wants like we do the surveys, different kinds of surveys are done.
Questionnaires are filled. There are a lot of people who fills out the questionnaire at the start. Conduct Surveys, interviews, and polls.
I will take a simple example. Like in today's time, if I also want to start a course. So it's not that I'll start it straightway.
I can put a poll on the community. That brother, on which topic or on which particular competitive exam, you want a course. So that we get a little idea in that way.
So it comes to know what is the interest. So the same thing is here. Creating a database means in a way you have to create a lot of data.
And for that, you have to do the interviews surveys, polls, and all this. Use cases mean using the case you already have. User stories are things that are already made It doesn't mean that you have to make it all new Like, Indian Railways has a system, & they want that my whole system becomes online online ticketing, all this should be done.
It has been already done but They already had an offline system. People used to go offline and buy tickets. This mean, they had an idea that things go like this.
Just they convert the entire offline system into online. This is just converting an already existing into online. But as I gave the example of Elon Musk, cars already running.
But making a self-drive car, that itself is a big challenging task. So these are the things that are different, the things that are already going on have to be used, Its base has to be maintained. Requirement different workshops, mind mapping.
Like, there is a software Mindtree, and what happens in it, we make very good 3D diagrams, very good elaborating diagrams. so that we can communicate well. It is not that you only write theory means you pasted 15 pages of theory It is like, maximum like I have done MTech, I know when we create a report, etc.
, So what do we do in it? We make a report of 50 pages. you also know no one reads that reports.
No one even sees. Check out two to three pages of starting, have seen superficially what is done in it, and see its summary. That's it.
But when crores of, billions of rupees will invest in a project at the company level. so it is very important to examine it closely. So, instead of theory, you bring the best diagram 3D diagrams, so that you can tell your things better.
Like I give the best example. When you will go to buy a house or flat in any society. So they have made full videos in 3D.
They show you the entire project in 3D view. So you will know that How will it look after it's built? That is a very important thing.
Similarly, role-play, prototype, a dummy model. The design will come later. Make a kind of raw diagram or a raw-like thing.
So that everyone, whatever the people who are in the loop, there are clients, the stakeholders, and users too, the company itself who is making. So they can all be in a loop and consistently prepare things. So the entire story comes under the software requirement or we also call it requirement engineering.
Thank you.
