The Object Management Group (OMG) adopted the Model Driven Architecture (MDA) approach from among the various Model Driven Engineering (MDE) methods. The MDA technique, which is based on the separation of concerns principle, aims to automate the software development process by using models rather than traditional coding. Model Driven Architecture (MDA) is a new technique to application modeling and creation that has gotten a lot of attention recently. Many organizations are now considering MDA as a way to organize and manage their application solutions, tool vendors are explicitly referring to their capabilities in terms of "MDA compliance," and the MDA lexicon of platform-specific and platform-independent models is now widely referenced in the industry. The OMG produced the second iteration of the MDA guide in June 2014 in an effort to implement the essential ideas and supplement the 2003 original with more precise specifications. Researchers' interpretations of the MDA words vary due to the 11-year difference and their respective perspectives and backgrounds. What causes uncertainty about what falls under and outside the MDA's scope. In this work, we present an overview of the current MDA trends simplifying integration challenges and enhancing business Information Technology (IT) alignment. This paper establishes boundaries around what constitutes MDA, positioning MDA in relation to other model-driven methods. It will also demonstrate its advantages over conventional software development and other model-driven methodologies. This paper highlights problems and difficulties that researchers have identified that affect the MDA. The paper also provides some insight into the MDA trends in research and directions, particularly with regard to the platforms that the MDA development process is aimed at and its automation.