Ending Notes

You have reached the end of the course. We talked about many different topics, and perhaps it seems unrealistic to remember all of them at all times. However, such a consequence is normal, and that is why I am providing a wrap-up to reiterate the essential aspects of this publication.

If you asked me what this text’s single guiding principle is, it would be a top-down flow of structure and information.

Everything starts at an enterprise level by examining business problems that the organization tries to solve. Once you distill this area, you can drill down into other aspects of the software engineering organization to align technology under the domain space.

Solutions to crosscutting concerns are the supporting mechanisms to other SDLCSoftware Development Life Cycle phases, so you must look into the culture, professionalism, talent, and requirements management as your next step.

After you get all the mentioned topics right, look at the phases of the SDLC. Each area seems straightforward at first glance until you accept the fact that the typical approaches prevalent today might not be the most efficient and cost-effective. What is the underlying principle of those topics in the book? It is to refuse the status quo! Instead, be persistent, and guide decisions by the structure that the earlier steps defined. For example, architecture defines microservices under the business domains, while the code implements the architecture.

That is the crux of this course in short. If you ever need additional information about any of the specific aspects that I mentioned here, you can always go back and review the corresponding chapters/lessons of the course.

I hope you enjoyed the reading. Now go and build software systems that can withstand time and serve successful businesses that gain a competitive advantage due to increased ROI.

You can do it!