Gain insights into implementing practical software architectures, mastering key development methodologies, and distinguishing core principles, ensuring your skills remain relevant in the ever-evolving industry.

Effective Software Development for Enterprise Applications.png

Non-readable code? Non-practical architectures? Unclear requirements? Are you pulling your hair at this point?

These are exactly the sort of pitfalls this course serves to provide in-depth remediation for. Over your years of working in the software industry, numerous day-to-day challenges like these come and go. While the industry has been constantly transforming, some core principles and values remain amidst the advancing technologies. 

Through tried and tested approaches, you will learn how to practically implement 'Effective Software'. With a comprehensive compilation of key concepts in software development methodology, you will be left with essential techniques for becoming a better software craftsman. It is time to distinguish between the core and the noise, making your skills timeless!

Effective Software Development for Enterprise Applications

I want to dedicate this section to [object-oriented programming](https://en.wikipedia.org/wiki/Object-oriented_programming) since I believe that it is the primary direction in enterprise software architecture and development. While functional programming is advantageous in certain situations, it is not so convenient or as naturally useful as OOP. 


The primary reason behind such a preference is the way people tend to think of or express domain knowledge, which is via nouns and verbs, which directly translate into objects and their behavior. This factor makes me believe that OOP will continue being a preferred choice for business or enterprise software development for the foreseeable future.

# Confusion about OOP

There is frequent confusion about OOP; people believe that they write object-oriented code as long as they use an object-oriented programming language. Unfortunately, this statement is not necessarily true. It is quite possible and very common too that people write procedural code while using an object-oriented programming language (e.g., C#).

A typical example of procedural code that developers often consider object-oriented is a sequence of steps to fulfill a particular operation. For instance, when placing an order, an application needs to charge a credit card, decrease inventory levels, and send a confirmation email. One way to implement this functionality is to write three classes that each fulfill a step of the overall process. Afterward, we can compose (i.e., inject) those three classes into one master class to invoke them in a sequence. Here is what it looks like on a UML diagram:

Learn why object-oriented programming is a fitting approach.

Fundamentals

Part I: Introduction

Part II: Crosscutting Concerns

Part III: From Customer Insights to Internal Requirements

Part IV: Design and Architecture

Part V: Implementation and Coding

Part VI: Testing and Quality Assurance

Part VII: Deployment

Part VIII: Maintenance and Support

Wrap-Up

Essence of Object-Oriented Programming