SDAM a ddnd mmdmsmfkvskkejj sehfjvksxkmwnejjfjbjsnenfPRESENTATION.pptx
- 1. Modeling with UML Department of Artificial Intelligence and Data Science Presented By : Vishal Bolke 18 Amit Dolas 42 Swapnil Gawali 51 Deepak Jadhavar 67 Vishwakarma Institute of Technology, Pune Guide: Dr Sunil M. Sangve
- 2. Agenda Introduction History of UML UML Diagram Types Tools for creating UML Diagrams Steps to create UML Diagrams Common Challenges in UML Modeling Advantages And Disadvantages Conclusion 1 2 3 4 5 6 7 8 9 10
- 3. Unified Modelling Language (UML) Unified Modeling Language (UML) is a general-purpose modeling language. The main aim of UML is to define a standard way to visualize the way a system has been designed. It is quite similar to blueprints used in other fields of engineering. UML is not a programming language, it is rather a visual language.
- 4. History of UML • UML originated in the 1990s through collaboration between software methodologists and industry leaders. • Evolution of UML through various versions, each expanding and refining the language. • Widely adopted across industries, contributing to its evolution and standardization. This Photo by Unknown Author is licensed under CC BY-SA
- 5. UML Diagram Types • UML offers a variety of diagram types, each representing different aspects of a software system. • Common types include Class Diagrams, Use Case Diagrams, Sequence Diagrams, Activity Diagrams, State Diagrams, Component Diagrams, and Deployment Diagrams. This Photo by Unknown Author is licensed under CC BY-SA
- 6. Tools for creating UML Diagrams There are several tools available for creating Unified Modeling Language (UML) diagrams, which are commonly used in software development to visually represent system architecture, design, and implementation. Here are some popular UML diagram creating tools:
- 7. Steps to create UML Diagrams
- 8. Common Challenges in UML Modeling • Time-Intensive: • UML modeling can be perceived as time-consuming, especially in fast-paced Agile environments where rapid development is emphasized. Teams may struggle to keep up with the need for frequent updates to UML diagrams. • Over-Documentation: • Agile principles value working software over comprehensive documentation. There’s a risk of over- documentation when using UML, as teams may spend too much time on detailed diagrams that do not directly contribute to delivering value. • Changing Requirements: • Agile projects often face changing requirements, and UML diagrams may become quickly outdated. Keeping up with these changes and ensuring that UML models reflect the current system state can be challenging. • Collaboration Issues: • Agile emphasizes collaboration among team members, and sometimes UML diagrams are seen as artifacts that only certain team members understand. Ensuring that everyone can contribute to and benefit from UML models can be a challenge.
- 9. Advantages • Standardization: • UML provides a standardized way of representing system models, ensuring that developers and stakeholders can communicate using a common visual language. • Communication: • UML diagrams serve as a powerful communication tool between stakeholders, including developers, designers, testers, and business users. They help in conveying complex ideas in a more understandable manner. • Visualization: • UML diagrams facilitate the visualization of system components, relationships, and processes. This visual representation aids in understanding and designing complex systems. • Documentation: • UML diagrams can be used as effective documentation tools. They provide a structured and organized way to document various aspects of a system, such as architecture, design, and behavior.
- 10. Disadvantages • Complexity • UML can be complex, especially for beginners. Learning all the aspects of UML and becoming proficient in using it may require a significant investment of time and effort. • Overhead: • In some cases, creating and maintaining detailed UML diagrams can be time- consuming. For small and simple projects, the overhead of creating extensive UML documentation may not be justified. • Ambiguity: • Interpretation of UML diagrams can be subjective, leading to potential ambiguity. Different individuals may interpret the same diagram in slightly different ways, causing confusion.