[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-655923-105":3,"detail-sidebar-cat-0-en-105":81,"doc-detail-655923-en":130},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","course-softwaretechnik-book-chapter-2-modeling-with-uml-overview","Course \"Softwaretechnik\" Book Chapter 2 - Modeling with UML - Overview","","Chapter 2 introduces modeling with UML in the context of software engineering. It explains how modeling builds abstractions of reality by selecting relevant details and preserving valid relationships between the real system and the model. The chapter contrasts static and dynamic UML views and presents common diagram types, including class, sequence, state machine, and activity diagrams. It also outlines UML’s notation concepts such as models, views, notations, and core elements like classes, associations, interfaces, states, and supporting profile and metamodel ideas.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/document/","Document",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/document/technology/","Technology",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/course-softwaretechnik-book-chapter-2-modeling-with-uml-overview/655923/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/course-softwaretechnik-book-chapter-2-modeling-with-uml-overview/655923.png","ImageObject",300,407,{"name":42,"@type":43},"Malam Tenang","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-30","2026-10-25",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",6,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the core idea of modeling with UML in this chapter?","Question",{"text":63,"@type":64},"Modeling builds abstractions of reality by representing relevant details and relationships while ignoring irrelevant ones. UML is presented as a way to structure and communicate these abstractions.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does the chapter distinguish between static and dynamic UML views?",{"text":68,"@type":64},"Static views focus on structure, such as class diagrams and object diagrams. Dynamic views capture behavioral aspects, such as sequence diagrams, state machine diagrams, and activity diagrams.",{"name":70,"@type":61,"acceptedAnswer":71},"Which UML diagram types are covered and what does each emphasize?",{"text":72,"@type":64},"Class diagrams emphasize static structure (classes, attributes, associations). Sequence diagrams describe dynamic interactions between objects. State machine diagrams model finite-state behavior, and activity diagrams model workflows with possible concurrency.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},655923,1793052228,{"code":4,"msg":82,"data":83},"success",[84,88,92,96,101,104,109,114,119,122,126],{"id":22,"doc_module":4,"doc_module_name":25,"category_name":85,"show_sort_weight":86,"slug":87},"Story & Novel",90,"story-novel",{"id":26,"doc_module":4,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},"Literature",80,"literature",{"id":33,"doc_module":4,"doc_module_name":25,"category_name":93,"show_sort_weight":94,"slug":95},"Exam",70,"exam",{"id":97,"doc_module":4,"doc_module_name":25,"category_name":98,"show_sort_weight":99,"slug":100},5,"Comic",60,"comic",{"id":55,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":102,"slug":103},50,"technology",{"id":105,"doc_module":4,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},7,"Healthcare",40,"healthcare",{"id":110,"doc_module":4,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},8,"Research & Report",30,"research-report",{"id":115,"doc_module":4,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},9,"Religion & Spirituality",20,"religion-spirituality",{"id":117,"doc_module":4,"doc_module_name":25,"category_name":120,"show_sort_weight":117,"slug":121},"World Cup","world-cup",{"id":123,"doc_module":4,"doc_module_name":25,"category_name":124,"show_sort_weight":123,"slug":125},10,"Lifestyle","lifestyle",{"id":127,"doc_module":4,"doc_module_name":25,"category_name":128,"show_sort_weight":97,"slug":129},19,"General","general",{"code":4,"msg":82,"data":131},{"doc_id":79,"user_id":132,"nickname":42,"user_avatar":133,"doc_module":4,"category_id":55,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":139,"language":140,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":12,"update_tm":144,"read_time":145},962093532863,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","# Course \"Softwaretechnik\"Book Chapter 2\n\nModeling with UML  \nLutz Prechelt, Bernd Bruegge, Allen H. DutoitFreie Universität Berlin, Institut für Informatik  \n• Modeling, models and UML  \n• Static view:  \n• Class diagrams  \n• Dynamic view:  \n• Sequence diagrams  \n• State machine diagrams  \n• Activity diagrams  \n• Other UML diagram types  \n• component d. , collaborationuse d. , deployment d. ,communication d. , interactionoverview d.  \n• UML Metamodel , Profiles  \n• Some notation details  \n• Classes, associations,interfaces, states  \n• Modeling consists of building an abstraction of reality  \n• Models ignore irrelevant details (i. e. , they simplify)  \n• and only represent the relevant details  \n• What is relevant or irrelevant depends on thepurpose of the model. We typically want to  \n• draw complicated conclusions about reality  \nwith simple steps in the model in order to  \n• get insights into the past or presence or make predictions  \n• Reality R:  \n• Real things, people, etc.  \n• Processes happening during some time  \n• Relationships between things etc.  \n• Model M:  \n• Abstractions of any or all of the above  \n• In a good model, relationships which are valid in reality R  \nare also valid in model M (if they exist in M at all) .  \n• I : Mapping of reality R to the model M (abstraction)  \n• fM: relationship between abstractions in M  \n• fR: equivalent relationship between real things in R  \n• In a good model, the following diagram is commutative:  \nfM  \nma  mb  \n  \nI   I  \nra  rb  \nfR  \n• We can think of a model as reality and can build another  \nmodel from it (with additional abstractions)  \n• The development of software systems is a transformation of models:Requirements elicitation (􀃆 req's document M1),  \nRequirements analysis (􀃆 analysis model M2) ,  \nDesign (􀃆 design model M3) ,  \nImplementation (􀃆 source code M4)  \n….  \n\"Model-DrivenDevelopment\"  \nuses this idea for itsengineering approach.  \nM2  \n  \nAnalysis   \nM 1  \n\n| RequirementsElicitation   |   \u003Cbr>  \u003Cbr>R   |\n| --- | --- |\n\nfM 2  \nfM 1  \nfR  \nM2  \n  \n I  \nM 1  \n  \n I  \nR  \n2  \n1  \nLutz Prechelt, prechelt@inf.fu-berlin.de [4] 4 / 54  \n• A model is an abstraction describing relevant aspects of a  \nsystem  \n• A view (\"Sicht\") depicts selected aspects of a model  \n• Any view is a model itself  \n• Calling a model a view makes clear it is part of a larger model  \n• Complex models are often shown as many views only  \n• never as a whole  \n• A notation is a set of rules for depicting models  \n• graphically or textually  \n• Example:  \n• System: Aircraft  \n• Models: Flight simulator, scale model, construction plan, …  \n• Views: All blueprints (e.g. electrical wiring, fuel system)  \n## UML ( Unified Modeling Language):\n\n• The most-used standard for software modeling  \n• For both requirements modeling (application domain)  \n• and software modeling (solution domain)  \n• A set of related notations  \n• Quite complex, we will use a subset only  \n• Resulted from the convergence of notations fromthree leading object-oriented methods:  \n• OMT (James Rumbaugh)  \n• OOSE (Ivar Jacobson)  \n• Booch method (Grady Booch)  \n• The authors are known as \"The Three Amigos\"  \n• Supported by CASE tools  \n•  http://de.wikipedia.org/wiki/UML-Werkzeug  \nLutz Prechelt, prechelt@inf.fu-berlin.de [4] 6 / 54  \n• Use Case diagrams (functional view)  \n• Catalog scenarios that describe the functional behavior of thesystem as seen by the user [see lecture \"use cases\"]  \n• Class diagrams / Object diagr. (static view and examples)  \n• Describe the static structure of the system: Classes, attributes,object associations (class diagram) or  \nsnapshots of possible resulting configurations (object diagram)  \n• Sequence diagrams (dynamic view examples)  \n• Describe examples of the dynamic behavior between objects ofthe system (and possibly actors)  \n• State machine diagrams (dynamic view)  \n• Describe some aspects of the dynamic behavior of the individualobject of a class by a finite state automaton  \n• Activity d","cbCaicSnvNEeQBAK","https://ap.wps.com/l/cbCaicSnvNEeQBAK","pdf",2918959,59,"English","# Modeling with UML\n## Modeling concepts: reality, models, and mapping\n## UML as a modeling standard\n## UML diagram types: static and dynamic views\n## Notation concepts and diagram elements","[{\"question\":\"What is the core idea of modeling with UML in this chapter?\",\"answer\":\"Modeling builds abstractions of reality by representing relevant details and relationships while ignoring irrelevant ones. UML is presented as a way to structure and communicate these abstractions.\"},{\"question\":\"How does the chapter distinguish between static and dynamic UML views?\",\"answer\":\"Static views focus on structure, such as class diagrams and object diagrams. Dynamic views capture behavioral aspects, such as sequence diagrams, state machine diagrams, and activity diagrams.\"},{\"question\":\"Which UML diagram types are covered and what does each emphasize?\",\"answer\":\"Class diagrams emphasize static structure (classes, attributes, associations). Sequence diagrams describe dynamic interactions between objects. State machine diagrams model finite-state behavior, and activity diagrams model workflows with possible concurrency.\"}]","Course \"Softwaretechnik\" Book Chapter 2 - Modeling with UML - Overview | PDF",1792964948,149]