[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-655645-105":59,"doc-detail-655645-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-in-a-nutshell-uml-2x-overview","UML in a Nutshell - UML 2.x - Overview","","UML in a Nutshell introduces the Unified Modeling Language as a standardized set of modeling artifacts for software engineering, built from established methods such as OMT, Booch, and OOSE. It explains the purpose of UML without forcing a single development process and highlights the role of organizations like RATIONAL and OMG. The material summarizes contributions across UML 1.x versions, key concepts such as use cases, classes, and meta-modeling, and provides guidance such as rule-of-thumb advice for applying optional UML elements effectively.",{"@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-in-a-nutshell-uml-2x-overview/655645/",{"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-in-a-nutshell-uml-2x-overview/655645.png","ImageObject",300,407,{"name":92,"@type":93},"วิน","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-25",true,{"@type":102,"interactionType":103,"userInteractionCount":24},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What is UML and what problem does it address in software engineering?","Question",{"text":112,"@type":113},"UML is a unified language that captures information about software systems using standardized artifacts such as models, notation, and diagrams. It helps represent requirements, analysis, and design information consistently, even though it does not standardize a single development process.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"How do the origins of UML influence its notation and modeling approach?",{"text":117,"@type":113},"UML is based on OMT notations for data-based system analysis and design, Booch method notations for design and implementation, and OOSE notations for requirement analysis. This synthesis shapes UML’s core concepts and modeling structure.",{"name":119,"@type":110,"acceptedAnswer":120},"Which key principle guides how to apply UML elements in practice?",{"text":121,"@type":113},"UML elements are largely optional, and not every part or symbol needs to be used in every model. The guideline is to show only what helps clarify the message being conveyed for the specific problem and view.","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},655645,1793029497,{"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":24,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":52,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":143,"read_time":144},2336475104736,"https://ap-avatar.wpscdn.com/avatar/22000c4c5e0e5b17e70?x-image-process=image/resize,m_fixed,w_180,h_180&k=1786591360781797222","Software Engineering  \nUML in a Nutshell  \nOlivier Boissier Mines Saint-Etienne [Olivier.Boissier@emse.fr](Olivier.Boissier@emse.fr)  \nFall 2020  \n1  \n\n| Revision Task Force, Nov 2003 UML 2 .x\u003Cbr>UML : Evol eioaForce, March 2003 UML 1.5\u003Cbr>\u003Cbr>|  |  |  |  |\n| --- | --- | --- | --- | --- |\n| Revision Task Force, May 2001 Revision Task Force, June 1999\u003Cbr>Approval OMG, Nov 1997\u003Cbr>1st submission à OMG, Jan 1997 UML partners |  | UML 1.4\u003Cbr>\u003Cbr>UML 1.3 |  |  |\n|  |  | \u003Cbr>UML 1.1\u003Cbr>\u003Cbr>UML 1.0\u003Cbr>| |  |\n| Web-June 1996\u003Cbr>OOPSLA 1995\u003Cbr>UML 0.9\u003Cbr>\u003Cbr>Unified Method 0.8\u003Cbr>\u003Cbr>|  |  |  |  |\n| Other methods | Booch method OMT\u003Cbr>(Rumbaugh) |  | OOSE (Jacobson) | 3 |\n\n\n| UML ( Unified Modeling Language )\u003Cbr>• Based on:\u003Cbr>• OMT notations (J. Rumbaugh) for the analysis and design of data-based information systems\u003Cbr>• G. Booch’s method notations for the design and implementation phases\u003Cbr>• OOSE notations (I. Jacobson) for requirement analysis\u003Cbr>|  |\n| --- | --- |\n| through \"use cases\" .\u003Cbr>• Proposes:\u003Cbr>• Standardized development artifacts (models, notation, diagrams) WITHOUT standardizing the development process,\u003Cbr>• Important role played by RATIONAL and OMG ( [http://www.omg.org/](http://www.omg.org/)) | 2 |\n\nContributions to UML 1.X  \nMeyer  \nBefore and after conditions  \nBooch  \nBooch method   \nHarel Statecharts  \nRumbaugh OMT  \nJacobson  OOSE  \nShlaer-Mellor  \nObject lifecycles  \nGamma, et al  \nFrameworks and patterns  \nHP Fusion  \nOperation descriptions and message numbering  \n  Embley Singleton classes and  \n high-level view  \nWirfs-Brock  \nResponsibilities Odell  \nClassification  \n4  \nUML Meta-Model  \nBased on Martin Fowler UML Distilled and Viviane Jonckers OOSD-UML course 5  \nUML Diagrams  \nPossibility of representing the same diagram at different levels of detail  \nBased on Martin Fowler UML Distilled and Viviane Jonckers OOSD-UML course 7  \nUML Vocabulary  \nBasic components  \nAnnot.  \nnote  \nStruct. Group.  \nRelations  \nDependences Associations Generalisation  \nUse cases Classes Active classes Interface Component  \nCollaboration Node  \nComp.  \nInteraction  \nPackage Model Sub-system Framework  \nState machine  \nDiagrams  \n+ extention mechanisms  \n6  \nRules of thumb  \n• Nearly everything in UML is optional  \n• UML provides a language to capture information that varies greatly depending on the domain of the problem.  \n• Parts of UML either don't apply to your particular problem or may not lend anything to the particular view you are trying to convey.  \n• You don't need to use every part of UML in every model you create.  \n• You don't need to use every allowable symbol for a diagram type in every diagram you create.  \n• Show only what helps clarify the message you are trying to  \n8  \n\n| Class Diagram\u003Cbr>ØClass\u003Cbr>ØObject\u003Cbr>ØPackage\u003Cbr>ØComposite Structure\u003Cbr>ØComponent\u003Cbr>ØDeployment\u003Cbr>ØStatechart\u003Cbr>ØActivity\u003Cbr>ØUse cases\u003Cbr>ØInteraction\u003Cbr>Ø Sequence\u003Cbr>Ø Interaction\u003Cbr>Ø Communication\u003Cbr>Ø Timing\u003Cbr>• Central point of system modeling to describe what the system should do (analysis) and how it will do (design) . Diagram with the highest importance\u003Cbr>• Representation of the information system static structure\u003Cbr>• Modeling of classes and their relations\u003Cbr>• Errors in this diagram impact the other diagrams\u003Cbr>\u003Cbr>| 9 |\n| --- | --- |\n\n\n| \u003Cbr>Object Diagram\u003Cbr>• Also called instances diagram,• Represents the static structure\u003Cbr>• Represents the instances\u003Cbr>• Used to:\u003Cbr>– Show the interactions,\u003Cbr>– Represent complex structures (recursive)\u003Cbr>\u003Cbr>ØClass\u003Cbr>ØObject\u003Cbr>ØPackage\u003Cbr>ØComposite Structure\u003Cbr>ØComponent\u003Cbr>ØDeployment\u003Cbr>ØStatechart\u003Cbr>ØActivity\u003Cbr>ØUse cases\u003Cbr>ØInteraction\u003Cbr>Ø Sequence\u003Cbr>Ø Interaction\u003Cbr>Ø Communication\u003Cbr>Ø Timing | 11 |\n| --- | --- |\n\nClass Diagram  \nStatic structure of the system: Objects, Attributes, Associations  \n10  \nObject & Class Diagrams  \nRecordingCategory  \ndescription  \n| Recording |\n| --- |\n| title artist |\n\n* hasCategory  \nsubcategory  \nIs instantiated into  \nObjects are ","cbCaijCnkII1AC6t","https://ap.wps.com/l/cbCaijCnkII1AC6t","pdf",12776251,"English","# UML in a Nutshell\n## UML origins and purpose\n## Contributions to UML 1.X\n## UML meta-model and vocabulary\n## Rules of thumb\n## UML diagrams overview\n## Class, object, package, composite structure, and component diagrams","[{\"question\":\"What is UML and what problem does it address in software engineering?\",\"answer\":\"UML is a unified language that captures information about software systems using standardized artifacts such as models, notation, and diagrams. It helps represent requirements, analysis, and design information consistently, even though it does not standardize a single development process.\"},{\"question\":\"How do the origins of UML influence its notation and modeling approach?\",\"answer\":\"UML is based on OMT notations for data-based system analysis and design, Booch method notations for design and implementation, and OOSE notations for requirement analysis. This synthesis shapes UML’s core concepts and modeling structure.\"},{\"question\":\"Which key principle guides how to apply UML elements in practice?\",\"answer\":\"UML elements are largely optional, and not every part or symbol needs to be used in every model. The guideline is to show only what helps clarify the message being conveyed for the specific problem and view.\"}]","UML in a Nutshell - UML 2.x - Overview | PDF",1792962999,25]