 Since we are at the last week of the course, it is important to reflect on the learnings and concepts we learnt in the previous weeks, so that we can make connections between them. Yes, I agree. Also making connections between the newly learnt concepts and the earlier known concepts is an important exercise. So in week one, we looked at how a relatively large software like Amazon is built. It is made up of several interworking modules. And this concept is known as modularization. Modularization is used to divide a software system into multiple independent and co-working modules. These modules are capable of carrying out the desired functionalities and they form the basic building blocks for the entire software. Also in week one, we learnt about the different phases and the software development models. So learners, here is a question for you. Why didn't we learn about the various phases in software design and the development models? Pause the video, write your answer in the notebook and resume. Software development does not start immediately with programming and creating a software. It begins with understanding the needs of the end user, creating a plan, verifying it and then implementing it using a programming language. After creating the software, we test it and then deploy it at the customer's end. So software development is a systematic process of problem solving. Yes, you are right. The software development phases are broad and could be done iteratively and in many different ways. So that is why it is important for software developers to know and understand these phases and processes. We also compared and contrasted software design with design in other domains, specifically architecture. Yes, the abstract and intangible nature of software adds to the complexity in software design and development. However, there are similarities in the design processes across the domains, much like the steps to problem solving. In V2 and V3, we created software design models using the FBS design framework and the UVMA diagrams. How do these models map to the software development phases and the processes? Yes, that is an important question. We will discuss this in detail in the next video.