UML (Unified Modeling Language) is a general-purpose description language, especially in software development, that indicates the details of the development process of anything in industry. It is intended to provide a standard way to view the design of a system. In software engineering, UML modeling is particularly used to generate reverse engineering codes or models. Say no to plagiarism. Get a tailor-made essay on "Why Violent Video Games Shouldn't Be Banned"? Get an Original Essay The first step in developing a project is modeling what will be done. Modeling is the most significant process for specifying the architecture of a project. UML greatly helps the modeling process, it is also used in different software system disciplines such as, especially in information systems, embedded systems, operating system design, etc. UML is a high-level language designed to allow developers from various parts of the world to communicate about a project. These developers may follow different methods depending on the conditions of the project they are involved in. For example, UML has a defined syntax, notation, and semantics, but today developers can customize these notions to its development methods. Developers have different evaluation methods depending on the project, which is included in many other concepts such as UML. According to our research, most software developers believe that the ideal stopping criterion for modeling a project is to complete a task flawlessly, but when the schedule or deadline gains importance, professionals think that the deadline is a stopping criterion. This idea will lead to a visible decline in the quality of the designed work. However, this may differ between developers working on different sized projects. Especially considering the relationship between completeness and deadline, completeness becomes more important for defining stopping criteria in large projects. The reason for this can be conceived as the demand for more systematic methods due to increased complexity. This situation introduces a mechanism for developing more definitive designs. Looking at UML modeling, it is clearly seen that most developers might encounter several problems during the modeling process. These issues can be considered in 4 main sections: Scattered information: Various concepts related to modeling choice can be scattered by developers. Incompleteness: developers develop a very specific part of the project, rather than thinking about the project as a whole; Disproportionality: Architects can find more detail for the parts of the system they find more complex; Inconsistency: Completely different model design situation due to the developers who were supposed to develop the project analyzing the problem differently. Furthermore, other causes such as quality of diagrams, informal usage, lack of modeling conventions, etc. can be mentioned. All these types of problems could be caused by architects and their understandings and habits. This situation will cause inconsistent UML modeling and make designs completely inconsistent due to communication issues. How you design UML models is just as important as how you design UML. For example, research involving modeling interactive public methods that are not described and must be called on sequence diagrams finds that between 40 and 78% of models are not designed with any sequence diagrams. Also, another one 48.