[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-517783-105":3,"detail-sidebar-cat-0-en-105":81,"doc-detail-517783-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","software-architecture-metrics-at-sig-lessons-learned-getting-software-right","Software Architecture Metrics at SIG - Lessons Learned - Getting Software Right","","Software architecture metrics at SIG summarizes lessons learned from large-scale software analysis involving 1,500+ systems, 40,000+ versions, and 100+ programming languages. The material covers principles for choosing metrics (“metric is a good servant but a bad master”), avoiding “silver bullets,” and recognizing when metric-driven changes become cosmetic. It emphasizes context and structure, using human-in-the-loop exploration, and tooling for rapid zoom from visualizations to source code, including mapping technologies to basic metrics and visual metric representations.",{"@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/research-report/","Research & Report",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/document/software-architecture-metrics-at-sig-lessons-learned-getting-software-right/517783/",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/software-architecture-metrics-at-sig-lessons-learned-getting-software-right/517783.png","ImageObject",300,407,{"name":42,"@type":43},"Ivy","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-11-17","2026-10-07",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",8,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the core warning about using software metrics?","Question",{"text":63,"@type":64},"Metrics are useful as feedback, but using them as goals leads to distorted behavior. The document explicitly states: “Metric is a good servant but a bad master.”","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How should metric changes be evaluated to avoid cosmetic improvements?",{"text":68,"@type":64},"Recognize when alterations affect only the software’s surface appearance rather than its underlying quality. The document gives examples such as reordering getters/setters or mechanically splitting methods.",{"name":70,"@type":61,"acceptedAnswer":71},"Why is context and structure important when interpreting data?",{"text":72,"@type":64},"The document stresses that data alone cannot tell the story; the surrounding context and structure determine meaning. It highlights the need for the narrative behind the metrics.","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},517783,1791461772,{"code":4,"msg":82,"data":83},"success",[84,88,92,96,101,106,111,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":102,"doc_module":4,"doc_module_name":25,"category_name":103,"show_sort_weight":104,"slug":105},6,"Technology",50,"technology",{"id":107,"doc_module":4,"doc_module_name":25,"category_name":108,"show_sort_weight":109,"slug":110},7,"Healthcare",40,"healthcare",{"id":55,"doc_module":4,"doc_module_name":25,"category_name":29,"show_sort_weight":112,"slug":113},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,"preview_page_count":33,"preview_urls":146},549758252649,"https://ap-avatar.wpscdn.com/avatar/8000253669c5317157?_k=1778319167496531819","System Architecture Metrics at SIG: Lessons Learned  \nZeljko Obrenovic, [http://obren.info](http://obren.info)  \nFebruary 2, 2016  \nGETTING SOFTWARE RIGHT  \n1500+  \nsystems  \n40,000+ versions  \n100+  \nlanguages  \n7 bln + lines of code  \n25 mln + LOC analyzed each  \nweek  \nSoftware Improvement Group Page 2  \nContents  \n1 No silver bullets  \n2 Getting what you measure  \n3 The importance of context and structure: “story tells that data, data do not tell the story”  \n4 Human in the loop: exploration, creativity and (simple) metrics + implication for tools  \n5 Visualizing the metrics: from paper and glue to 3D  \nSoftware Improvement Group Page 3  \n100+ languages (200 dialects)  \nabap, abapsmartforms, abl, accell, acl, actionscript, actionscript3, ada, adabasnatural, adfxml, ads, angularjstemplate, applicationmaster, aps, aquima, asp, aspx, batch, bea, bixml, biztalk, bpel, brail, bsp, c, cache, cacheobjectscript, ccl, cgdc, cl, clearbasic, clojure, cobol, coffeescript, coldfusion, common, configuration, coolgen, coolgenc, coolgencobol, cordysbpm, cpp, csharp, csharppreprocessed, csp, css, cucumber, datastage, datastageetl, datastageworkflow, db2, dcl, delphi, delphiforms, docker, drools, easytrieve, egl, ejs, embeddedsql, erb, esql, filetab, finacle, flow, fortran, freemarker, gensym, groovy, gsp, gupta, hql, html, ibmbpm, ibmbpmbpd, ibmbpmprocess, ideal, idms, importexpander, informix, informix4gl, informixsql, ingres, intershoppipeline, jade, jasperreports, java, javafx, javascript, jbc, jcl, jcs, jsf, json, jsp, less, lodestar, logicnets, lotusscript, lua, magic, magik, magnum, matlab, mendix, messagebuilder, models, mustache, mysql, naviscript, nodejs, nonstopsql, normalizedsystemsjava, objectivec, odi, opa, opc, openroad, oracle, pascal, pascalprecompiled, performance, perl, php, pli, plsql, plsqlforms, plsqlreports, postgresql, powerbuilder, powershell, progress, progressstrict, pronto, prt, puppet, python, razor, rexx, rpg, ruby, sas, sass, scala, scl, scr, script, shared, shellscript, siebeldeclarative, siebeljs, siebelscripted, siebelworkflow, smalltalk, sourcegraph, sql, sqlite, sqlj, sqr, ssis, starlimssql, streamserve, swift, synon, t4, tacl, tal, tandem, tapestry, tibco, tibcobe, tibcobejava, tibcobestatemachine, tripleforms, tsql, turtle, typescript, uil, uniface, unknown, until, vag, vagrecord, vb, vbnet, velocity, visualobjects, visualrpg, webfocus, webmethods, wsdl, wtx, xaml, xml, xpdl, xpp, xquery, xsd, xslt, yaml  \nSoftware Improvement Group Page 4 of 5  \nDependencies among modules  \n31 modules, 347 connections, 79 places with cyclic dependencies  \nSoftware Improvement Group  \nMapping technologies to basic metrics  \n4. System  \nCodebase maintained by a team of developers  \n1. Unit  \ne.g.: Method Procedure,  \nsubroutine  \n3. Component  \ne.g.: Top-level directory, package, namespace, Maven sub-module, Visual Studio solution  \n2. Module  \ne.g.: File, Class, Script  \n,  \nFunction,  \nSoftware Improvement Group Page 7  \nContents  \n1 No silver bullets  \n2 Getting what you measure  \n3 The importance of context and structure: “story tells that data, data do not tell the story”  \n4 Human in the loop: exploration, creativity and (simple) metrics + implication for tools  \n5 Visualizing the metrics: from paper and glue to 3D  \nSoftware Improvement Group Page 8  \nGetting what you measure  \n“Metric is a good servant but a bad master”  \n> Making alterations just to improve the value of a metric  \n• Difficult to avoid using metrics as a goal rather than as a feedback mechanism> Recognized when changes made to the software are purely cosmetic.  \n> Examples: order of getters and setter, mechanical splitting of methods (e.g. step 1, step 2…)> In the end you need to be able to zoom in the code  \n• Need for tools that enable rapid metrics zoom in / zoom out to the source code  \nSoftware Improvement Group Page 9  \nGetting what you measure  \nOne-track metric or a metric galore  \n> Focusing on only a single metric:  \n• E.g. duplication ","cbCaiuuiTMZT3VQF","https://ap.wps.com/l/cbCaiuuiTMZT3VQF","pdf",8524614,28,"English","# Contents\n## No silver bullets\n## Getting what you measure\n## The importance of context and structure\n## Human in the loop\n## Visualizing the metrics","[{\"question\":\"What is the core warning about using software metrics?\",\"answer\":\"Metrics are useful as feedback, but using them as goals leads to distorted behavior. The document explicitly states: “Metric is a good servant but a bad master.”\"},{\"question\":\"How should metric changes be evaluated to avoid cosmetic improvements?\",\"answer\":\"Recognize when alterations affect only the software’s surface appearance rather than its underlying quality. The document gives examples such as reordering getters/setters or mechanically splitting methods.\"},{\"question\":\"Why is context and structure important when interpreting data?\",\"answer\":\"The document stresses that data alone cannot tell the story; the surrounding context and structure determine meaning. It highlights the need for the narrative behind the metrics.\"}]","Software Architecture Metrics at SIG - Lessons Learned - Getting Software Right | PDF",1791344980,71,[147,151,154,158],{"page_no":22,"url":148,"width":149,"height":150},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/25076a6429842935b63e306ed1a7c7ac.webp",983,552,{"page_no":26,"url":152,"width":153,"height":150},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/9e77ec4f87b169770abc72d28e501844.webp",982,{"page_no":30,"url":155,"width":156,"height":157},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/72986cf353f83108dcecaf910bce0a36.webp",981,551,{"page_no":33,"url":159,"width":160,"height":157},"https://res-academy.cache.wpscdn.com/upload/kdocshare/2026-11-17/62c31201b9c3366db168dc0780435f21.webp",980]