← Course overviewFree lesson 1 of 3 · lesson 1 of 34Next lesson →

Unlock all 34 lessons of Electronics System DesignFull course ₹40,000 · paid

Price & syllabus
Free lesson · 17 min · no payment

What Is a System: Purpose, Scope and the V-Diagram

A free lesson from Skill-Lync's Electronics System Design course, on Grow by Skill-Lync · Last updated 16 Nov 2026 · Session: “Module 1 Session 1”

What will you learn in this free Electronics System Design lesson?

Explains that every system is designed to achieve a purpose, using water supply, irrigation and solar system examples and a definition of a system as interconnected elements. Introduces subsystems, integration and the V-diagram of requirements, design, verification and release, with medical device applications as context.

  • Purpose and scope of a system
  • System as interconnected elements, with subsystems
  • Breaking a system into subsystems and integrating them
  • Overview of the V-diagram for system design

What comes after lesson 1?

The next free lesson is lesson 2, “Electronic System Definition: Types, Components and PCB Design Flow” (19 min). Later in Skill-Lync's Electronics System Design course (paid): lesson 4, Module 1 Session 4; lesson 5, Module 2 Session 1; lesson 6, Module 2 Session 2. The full course has 34 lessons (10 h 43 min of video); see the course overview or its price and syllabus.

Lesson transcript

Machine transcript of the lesson audio (lightly cleaned). Technical terms may contain errors; the video is the reference.

Okay, welcome everyone to the first session of electronic system design module where we will be covering the topics on introduction to electronic systems. So broadly the topics that we are going to cover today will be the purpose and scope of a system and the definition of an electronic system in a complete application and then various applications and examples in various industries. Also we will try to focus on applications in medical devices industry wherein I will be talking about various systems that are currently in use and what is the scope or scope for a better mentor, what future applications can be designed.

So the learning objectives for today's session will be so you will be able to learn about the concepts of an electronic system. So what is the definition of a system, what is the role of electronics as a part of in completing a system and what are the system design inputs and outputs like what inputs are needed to realize a system application and at the end of a system design. So what are the outputs that needs to be generated and how a concept can be generated to realize a system actually you can come up with various concepts.

So only one of them will will turn to reality. So how to come up with concepts and how to choose which one of them is the best. So those topics will be covered and again we will be covering various applications in the medical devices industry. So let's begin with this purpose and scope part. So what is the purpose of a system. So broadly any system is designed to realize a purpose. So when I say purpose it is an application. So we have transportation system so which is to carry people from one place to another place.

We have irrigation system which is to help provide water to agriculture fields or for those purposes. And we have a water supply system and the purpose of a water supply system is basically to provide water to every household for our regular usages. Now when you look at this system. So the reason why we are calling this a system is because so there are various modules. Like when the water body there is a very large water body. So somewhere very far which is a natural water resource.

And this water had to be brought to a nearby resource from where it can be supplied to all the houses. So a mechanism has to be set up between the nearby water body and a proper channel has to be established. And all those activities have to be performed and once all those activities are done. Then the purpose of providing water to household bodies is achieved. So this complete system is achieving the purpose of providing water to household. So that is why we are calling this a system.

So it's called a water supply system. Similarly any system which is designed in such a way so that it can realize a definitive purpose. It can be called as a system. The needs and applications are very much subjective. Because if you look at the system. So this water supply is used by various people. So this water supply also goes to households where you will be using water for regular activities like taking bath, washing clothes, washing dishes and all those. But the same water connection will also go to a fire office where they will be using it for a different purpose.

So when you ask a housewife like what is the purpose of water for you. Then she will say I need water to wash my clothes and all. So her needs are different. When you ask a fireman how are you going to use water. Then he will say that he will be going to use it for some other purpose like in case there is a fire accident. Then he will use it to extinguish fire or for certain other application. So his needs are different. So the water body or the solution is same.

So you are supplying water to both to house and fire office. But the date needs or the applications that they're going to realize with that are different. So that is why it is very important to understand the needs and applications before a system design is achieved. It is also very important to understand your target audience or the end user. We can say dependency yes because a system is actually collection of subsystems various functionalities come together to realize a purpose. So there is difference. There is definitely a dependency always a system is is a flow of actions.

So one action is complete and the outcome of that action because the next action and the outcome of the next action because the with the later action. So that is how a system functions. So it's always a flow of action. So that is why interconnectivity or integration of all these actions which can be performed by respective subsystems is also an impact important aspect in a system design. So the scope of a system application. So the very important point to remember when when we're realizing an application or when we're going to design a system is to understand the needs and applications.

So like I was explaining in the previous slide. So needs and applications for the end user differs from the end user. A housewife will use water supply for different purposes. A fireman will use water supply for something else and water purification system or a company. So it uses water only it only purifies water for packaging water for a different purpose. So it is very important to understand the needs and applications or of the end user and because systems can be generic and systems can also be user specific.

If it is user specific, then this is very much important. And if it's a general system like water supply system, it goes to various kinds of end users and different applications can be met. And addressing when you're addressing a specific need. So or rather anything that is addressing a specific need is called can be called as a subsystem. For example, in this water supply system, you will see a water hose. So its purpose is actually to bring water from a nearby smaller water body like a lake or a water tank and to distribute that to the various houses that are there in the society or a residential area.

So this hose or this channeling system can be called a subsystem. So it has a definitive purpose. So to collect water from the nearby body and to distribute to the target users. So this becomes a subsystem. A collection of all such subsystems. So nearby water lake or be it a water source or be it your home appliances. All these constitute or rather all these contribute to complete a water supply system. And when we talk about the scope of a system, it is actually like I explained in a previous slide.

It is to realize an application or a purpose. So the purpose of this system is only to provide water to houses. And similarly, when you if you have a different system, so that will have a definite purpose with which you started the design. OK, then what is the system as defined by pioneering system thinker Donnellam Meadows. So a system is actually an interconnection or an interconnected set of elements that is coherently organized in a way that achieves something. So we'll take another example. Let us take a solar system.

So it's a system which constitutes of planets, stars, meteors, constellations and all. But a solar system inside a solar system. So Sun it rotates around itself. So Earth it rotates around itself. It also revolves around the Sun around Sun. So similarly or all other planets. So they had their own speeds of rotation revolution. So they are a subsist. You can tell that there are subsystems in their own way. But all those subsystems like all those planets, all those meteors and everything they constitute to complete a solar system.

So breaking down this statement an interconnected set of elements. So elements here are our planets, meteors, stars, Sun and all those are elements. So they are all interconnected. OK, and they are currently organized. So they all rotate and they all revolve in a definite axis and at a constant speed which is not altered in a way that achieves something. So what is it achieving? It is establishing a solar system. It is bringing balance to the cosmos. So I really don't know about the application of a solar system.

But it is there to achieve something. So that is what is called a system and systems thinking. So this is a very interesting topic. So an engineer. So like has to be a different perspective when it has when he or she starts looking at a system. The main goal of a system is actually to achieve some end users application or a purpose. And unless and until the purpose is not clear or. End-User applications that you want to realize are not clear. Your system is not going to be complete. So, it is very important to understand the end-user expectations and it's not just about understanding what the end-user wants. It is also to make him understand like what are the things that are possible.

So, sometimes user insights are very limited. So, you have to actually have to educate him or give some information or share some knowledge so that he will be able to understand the application more. So, if you have to do that, so you have to have more insights than him and more understanding on the system or the application. So, systems thinking is something to do with that. So, it is actually connection of all dots. So, systems thinking will help you to realize an application by breaking down the entire application into small, small submodules or components of work and how they all can be connected together to realize a complete system.

Coming back to the same example. Coming back to the same example, if you see there are interconnections between the bigger water body and the smaller water body and there is also interconnection between a smaller water body to the nearby distribution system and from the distribution system to your end application. So, the interfaces that we see here, the first interface is between the bigger water body and the smaller water body. This is like channeling or laying down canals through which water can flow from the main source to a nearby lake or a water tank.

The second interconnection is actually to have channels or water carrying pipes through which water can be brought and stored to nearby water body or it can be channelized through a hose or some distribution network and this is a larger distribution network and from here there will be a smaller distribution network through which your water will be distributed to your household. So, connecting the dots. So, connecting the dots. So, these are the missing dots. So, these are three different functionalities or targets that need to be achieved independently first and they all need to be connected together to achieve the purpose of the end application. So, which is providing water to the households. So, connecting the dots is nothing but breaking down. So, breaking down your entire system into smaller subsystems or smaller groups of activities and then realizing them independently and then connecting them in an order through which your end application is achieved. So, systems thinking will help you understand like how to break down this system into smaller components and when these connections have to happen and where to happen.

And what way the connections have to be have to be made and all those things. So, there is a reference actually. So, system purpose dot pd which can be found at this web links website. So, this will help you understand more on what is the purpose of a system. I will also talk about the concepts of system engineering in brief. So, a systems engineering unlike your regular engineering like electrical engineering or mechanical engineering systems engineering is a holistic approach. So, a systems engineer doesn't look at a system or a sub module level like he doesn't want to understand how resistors and the capacitors are connected or he doesn't want to understand how how this particular firmware is a particular firmware is working rather he has a visibility of when that particular software or when an electronic system or when that complete mechanical structure is complete when all of them are brought together is that system realizing or able to achieve the purpose for which the system is built or the purpose the system is targeted to.

So, so that is a system engineer. So, that is a system engineer and systems engineering is a is a branch of engineering which deals with which deals with the system design at a very higher level. And so, some of the activities that perform in system engineering are defining the complexity of the application and breaking down the complexity into subsystems and their integration. And when I say complexity of the application it is actually the end user needs and subsystems are like your end user needs can be broken down into some sub components or subsystems and each subsystem is meant to achieve a definite purpose.

Okay, so when all those subsystems. Okay, so when all those subsystems achieve their own definite purposes, they can all come together to achieve the bigger purpose, which is the end user application and that is a part of integration. So, all the subsystems that are broken down will be integrated together into a subsystem. So, in this image you will see this is basically a V diagram. It's a model of engineering engineering design design which we will be covering in later topics, but to give a brief introduction about this. So, this is a holistic system engineering system design approach systems engineer will will be responsible for concept generation. Its management concept will be responsible for deriving system requirements and the system design specifications which will be broken down into into subsystem design, subsystem requirements and then into detailed design and the component level implementation and in parallel the verification and testing activities will be happening and at the end. So, operations and maintenance design release and all those activities will be performed. So, this is in brief all the activities that will be carried out in order to realize a system.

So, that's all on the purpose and scope of this on the introduction to electronic system.

Want the rest of Electronics System Design?

Get the full course syllabus and fees.

The full course is paid (₹40,000). We'll send the syllabus and call you back within one working day.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.

Full course · paid

Unlock the full Electronics System Design course

The remaining 31 lessons, mentor-reviewed projects and a certificate come with the paid course (₹40,000). Leave your details: we'll send the syllabus and fees and call you back.

Get the syllabus and fees

A counsellor calls you back within one working day.

By submitting you agree to our Terms and Privacy Policy.

Grow by Skill-Lync · free lesson

Start watching

Free, no payment. Leave your details once and every free lesson on Grow plays straight away. A Skill-Lync counsellor may call you about the full Electronics System Design course.

By submitting you agree to our Terms and Privacy Policy.

Talk to a career counsellor

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.