[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-655849-105":59,"doc-detail-655849-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","uml-an-introduction","UML - An Introduction","","UML: An Introduction explains why systems should be modeled by analyzing problem domains, simplifying reality, capturing requirements, and visualizing both structure and behavior for solution design and documentation. It presents core principles such as choosing an appropriate modeling level of precision, connecting models to reality without hiding important details, and recognizing that nontrivial systems have multiple dimensions. It then defines UML as a unified modeling language created by Grady Booch, James Rumbaugh, and Ivar Jacobson, standardized by OMG in 1997, and describes modeling for visualization, specification, construction, and documentation using building blocks and common mechanisms.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/uml-an-introduction/655849/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/uml-an-introduction/655849.png","ImageObject",300,407,{"name":92,"@type":93},"Kurz","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-25",true,{"@type":102,"interactionType":103,"userInteractionCount":29},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"Why is modeling necessary before designing a solution?","Question",{"text":112,"@type":113},"Modeling helps analyze the problem domain, simplify reality, capture requirements, visualize the system overall, and specify its structure and/or behavior. It supports designing and documenting the solution.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"What principles guide effective modeling?",{"text":117,"@type":113},"Models must be chosen well, expressed at appropriate precision levels (scalable granularity), connected to reality while keeping important details, and recognized as multi-dimensional because no single model suffices for nontrivial systems.",{"name":119,"@type":110,"acceptedAnswer":120},"What is UML and what is it used for?",{"text":121,"@type":113},"UML is a unified modeling language for visualizing, specifying, constructing, and documenting software system artifacts. It provides unambiguous notations for modeling precisely and supports design independent of programming language.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},655849,1793029500,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":29,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":139,"language":140,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":67,"update_tm":144,"read_time":145},2336478945635,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","UML: An Introduction  \nContents  \n• Why model ?  \n• Principles of modeling  \n• What is UML ?  \n• Conceptual Model of the UML  \n• Building Blocks  \n• Rules  \n• Common Mechanisms  \nWhy Model ?  \n• Analyse the problem-domain  \n• simplify reality  \n• capture requirements  \n• visualize the system in its entirety  \n• specify the structure and/or behaviour of the system  \n• Design the solution  \n• document the solution- in terms of its structure, behaviour, etc.  \nPrinciples of Modeling  \n• Choose your model well-the choice of model profoundly impacts the analysis of the problem and the design of the solution.  \n• Every model may be expressed at different levels of precision-the same model can be scaled up (or down) to different granularities.  \n• The best models are connected to reality-simplify the model, but don’t hide important details.  \n• No single model suffices-every nontrivial system has different dimensions to the problem and its solution.  \nWhat is UML ?  \n• UML-Unified Modeling language  \n• Blue print of source code.  \n• UML is a modeling language, not a methodology or process  \n• Developed by Grady Booch, James Rumbaugh and Ivar Jacobson at Rational Software.  \n• Accepted as a standard by the Object Management Group (OMG), in 1997.  \nMore on UML. . .  \nUML is a modeling language for visualising, specifying, constructing and documenting the artifacts of software systems.  \nVisualizing-a picture is worth a thousand words; a graphical notation articulates and unambiguously communicates the overall view of the system (problem-domain).  \nMore on UML. . .  \nSpecifying-UML provides the means to model precisely, unambiguously and completely, the system in question.  \nConstructing-models built with UML have a “design” dimension to it; these are language independent and can be implemented in any programming language.  \nMore on UML. . .  \nDocumentation is  \n(among others) for:    \n• Requirements  \n• Design  \n• Tests  \nDocumenting-every software project involves a lot of documentation-from the inception phase to the deliverables.  \nUML provides the notations for documenting some of these artifacts  \nConceptual Model of UML  \n• Building Blocks  \n􀀎 Things  \n􀀎 Relationships  \n• Rules 􀀎 Diagrams  \n• Common Mechanisms  \n􀀎 Specifications  \n􀀎 Adornments  \n􀀎 Common Divisions  \n􀀎 Extensibility Mechanisms  \nUML Building Blocks  \n• Things  \n􀀎 Structural  \n􀀎 Behavioral  \n􀀎 Grouping  \n􀀎 Annotational  \n• Relationships  \n􀀎 Dependency  \n􀀎 Association  \n􀀎 Generalisation  \n􀀎 Realization  \n􀂋 Diagrams  \n􀂋 Class Diagram  \n􀂋 Object Diagram  \n􀂋 Use Case Diagram  \n􀂋 Sequence Diagram  \n􀂋 Collaboration Diagram  \n􀂋 Statechart Diagram  \n􀂋 Activity Diagram  \n􀂋 Component Diagram  \n􀂋 Deployment Diagram","cbCaivkV7dBHweXx","https://ap.wps.com/l/cbCaivkV7dBHweXx","pdf",1222943,43,"English","# Contents\n## Why model ?\n## Principles of Modeling\n## What is UML ?\n## Conceptual Model of UML\n## Building Blocks\n## UML Building Blocks","[{\"question\":\"Why is modeling necessary before designing a solution?\",\"answer\":\"Modeling helps analyze the problem domain, simplify reality, capture requirements, visualize the system overall, and specify its structure and/or behavior. It supports designing and documenting the solution.\"},{\"question\":\"What principles guide effective modeling?\",\"answer\":\"Models must be chosen well, expressed at appropriate precision levels (scalable granularity), connected to reality while keeping important details, and recognized as multi-dimensional because no single model suffices for nontrivial systems.\"},{\"question\":\"What is UML and what is it used for?\",\"answer\":\"UML is a unified modeling language for visualizing, specifying, constructing, and documenting software system artifacts. It provides unambiguous notations for modeling precisely and supports design independent of programming language.\"}]","UML - An Introduction | PDF",1792964305,108]