Why do I need to learn about advanced software design?
I think that I already learned about software design in the Topic 12 – Introduction to Software Design.
Now your task is not just to build a house. Your task is to build a city. The situation is similar to when you create complex software. Now, you are responsible for creating a software system containing about 10,000 classes for 5,000 people to use in 15 years. The maximum system downtime must be less than 5 minutes per year.
Image that you have to create a system that serves millions of people simultaneously like Facebook or YouTube or Amazon or Office 365 or GMail. Are you able to create it?
Image that you are tasked to create a web framework for developers to extend such as ASP.NET CORE or Yii or React.js. Are you confident in creating one?
If you are not sure how to fulfill these tasks then probably, you should learn how other people crafted similar systems and adapt their experiences to your case. Advanced software design knowledge will then be useful for you.
What can I do after finishing learning advanced software design?
You will know how to design a very complex software system that satisfies not only functional requirements but also security, modifiability, scalability, reusability, extensibility and reliability requirements.
That sounds interesting! What should I do now?
Advanced software design requires a lot of reading. Please do review your software design knowledge introduced in the Topic 12 - Introduction to Software Design first. Because nowadays software can be applied to many fields, each of them requires specific advanced software design knowledge, in this topic, we only focus on enterprise software because of its popularity.
Before you design a complicated system you must thoroughly understand its sophisticated requirements. This is a critical step when building a large system. Please read this "David C. Hay (2002). Requirements Analysis: From Business Views to Architecture" book to learn how to capture requirements for an enterprise system.
After that please read - this "Deepak Alur et al. (2003). Core J2EE Patterns: Best Practices and Design Strategies" book, and - this "Martin Fowler (2002). Patterns of Enterprise Application Architecture" book, and - this "Philip A. Bernstein and Eric Newcomer (2009). Principles of Transaction Processing. Second Edition" book.
After that please read - this "Eric Evans (2003). Domain-Driven Design: Tackling Complexity in the Heart of Software" book and - this "Jimmy Nilsson (2006). Applying Domain-Driven Design and Patterns: With Examples in C# and .NET" book and - this "Philip A. Bernstein and Eric Newcomer (2009). Principles of Transaction Processing. Second Edition" book.
After that please read this "David Budgen (2011). Software Design" book.
After that please read this "Len Bass et al. (2012). Software Architecture in Practice" book, especially chapter 5, 8 and 11.
After that please read - this "Cloves Carneiro Jr. and Tim Schmelmer (2016. Microservices from Day One: Build robust and scalable software from the start" book, and - this "Sam Newman (2016). Building Microservices: Designing Fine-Grained Systems" book.
After finishing the books please click Topic 16 – Calculus to continue.