 So last time we spoke about function behavior and structure. We discussed that functionalities are realized by various structures that interact with each other. These interactions are known as behaviors. Yes, we also looked at the function behavior and structure elements of a mood-based music player. But you also mentioned that we need to integrate the function behavior and structure. Why do we need to do that? Yes, that's an important question. So learners, what will happen if you do not integrate function behavior and structure? Pause the video, write your answers in the notebook and then continue. If you do not integrate function behavior and structure, the design would be many solutions and incoherent. For example, mood-based music player, if you had only focused on the functionality of mood detection, we would have created many solutions for achieving this functionality. This is not decidable. Okay, so we will have an incoherent solution if we do not integrate the function structure and behavior. But what are the benefits of integrating them? Creating a conceptual design, it is useful to integrate function structure and behavior for the following reasons. It helps us create an integrated view of the design solution. We also can ensure that the solution fulfills all the requirements. This unified view can be used to communicate within the team and the various stakeholders. It's also a useful technique to avoid getting stuck while creating a design. Okay, so now I have these individual fb and s. Now, how do I go about integrating the function structure and behavior? Is to start from known solution. For example, we know that there are cameras that can deduct mood automatically. These could be the structures in the design solution. But we also need to evaluate if these structures are applicable in the current problem and adaptive. In the next step, we can start thinking in terms of end user as well as a system to generate behaviors. For example, a user would place the camera to automatically start playing songs. The system could fetch song list based on a particular mood. And so on and so forth. In the next step, we map all the structures that work together when a behavior happens. In this way, we identify structures, behaviors and map them. The next step would be to identify how the structures and behaviors satisfy a particular requirement. So now we have identified structures, behaviors and functions and also mapped them. Okay, so this looks something like a graph, right? Yes, it is called the function behavior structure FPS graph. The nodes are the FPS. Links connect the FPS. Just like a graph, you could start from any of the nodes F, B or S and move on to the next as you identify and connect them. So learners, here is a question for you. Can you think of combinations of FPS graph and the kinds of graph that can be created? Pause the video, write your answers in the notebook and continue. On the screen, there are combinations of the FPS graph. In this graph, the behaviors are mapped to the structures and then the function B, S, F. In another graph, functions are broken down and mapped to structures which are combined to different end user behaviors. F, S, B. So there can be many types and kinds of FPS graph. Oh, okay. So there are many possible FPS graphs for a given problem. But how will I know if the graph that I have created is good enough? That is a good question. There is a checklist of things to keep in mind to self-evaluate a FPS graph. Okay, that sounds interesting. You know, there is a learning environment where you could do all this. Create a FPS graph and self-evaluate it for different software design problems. Really? Well, that sounds like a very cool solution. Yes, Tink and Link is a learning environment where the learners are taken through the steps of creating the FPS graph as well as evaluating it. In this video, we saw the importance of integrating F, B and S while creating a design. We also saw that one of the ways to integrate them is to create a FPS graph. Yes, in an FPS graph, the nodes, they form the function structure and behavior and these nodes are connected via links. We also saw that there are many combinations and kinds of FPS graph possible for a software design problem. A checklist is available to self-evaluate the FPS graph. In the next LED, we will explore how to use Tink and Link to create and self-evaluate a FPS graph for various software design problems.