 In week 2, we introduced the function behavior structure design framework. The function corresponds to the functionalities and features of the solution design. The structures correspond to the physical and logical components of the solution. The mechanism in which the structures interact to achieve the functionality is termed as behaviors. We then created an FPS graph which was an integrated model of the solution design. We used the Think and Link Learning environment to create and evaluate FPS graphs for different software design problems. In week 2, we created FPS graphs as software design solutions. But I am just wondering how does this map to the software processes and the development models that we just discussed in week 1? That is a good question. Actually, there is a mapping of the various processes like requirement definition, design, implementation, testing, deployment to the function structure behavior framework. Okay, so how is this mapping actually done? Can you please explain? While mapping, the FPS design elements, certain software processes get initiated. For example, when the function is mapped to a behavior, requirement definition process gets initiated. When a structure is mapped to a behavior, the design analysis process gets initiated. So on and so forth, certain doors while mapping the software process gets initiated. In this table, we see the different software engineering processes getting initiated while the FPS design elements are mapped to each other.