UML (Unified Modeling Language) is a general-purpose description language, especially in software development, which indicates the details of the development process of anything that happening in the industry. It is intended to provide a standard way of visualizing the design of a system. In software engineering, UML modeling is particularly used to generate codes or reverse engineering models. Say no to plagiarism. Get a tailor-made essay on “Why Violent Video Games Should Not Be Banned”? Get an original essay The first step in developing a project is to model what is going to be done. Modeling is the most important process for specifying the architecture of a project. UML greatly facilitates this modeling process, it is also used in several different software systems disciplines such as - largely 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 on a project. These developers can follow different methods depending on the conditions of the project in which they are involved. For example, UML has defined syntax, notation, and semantics, but today's developers can customize these notions to suit their 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 an impeccable task, but when the schedule or deadline becomes important, practitioners believe that the deadline is the stopping criterion. This idea will lead to a visible drop in the quality of the planned work. However, this may differ between developers working on projects of different sizes. Particularly regarding the relationship between completeness and deadline, completeness gains more importance in defining termination criteria in large projects. The reason for this may be the need for more systematic methods due to increased complexity. This situation provides a mechanism for developing a more definitive project. When looking at UML modeling, it becomes clear that most developers may encounter several issues during the modeling process. These issues can be addressed 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; Disproportion: Architects can find more details on parts of the system that they think are more complex; Inconsistency: Completely different model design situation due to different analysis of the problem by the developers who are supposed to develop the project. Furthermore, it is possible to mention other causes such as the quality of the diagrams, informal use, lack of modeling conventions, etc. All of these types of problems can be caused by architects and their intellects and habits. This situation will result in inconsistent UML modeling and make projects completely inconsistent due to poor communication. Knowing how to design UML models is just as important as designing UML. For example, research into modeling interactive public methods that are not described and must be invoked 48.