[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_122":123,"_124":125},"routes/public/layout",{"_61":62},"routes/public/primary/notes",{"_11":12,"_13":14},"note",{"_16":41,"_18":41,"_19":51,"_21":52,"_23":53,"_25":26,"_27":54,"_29":55,"_31":55,"_32":56,"_34":57,"_36":58,"_13":59},"backlinks",[15],{"_16":17,"_18":17,"_19":20,"_21":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":30,"_32":33,"_34":35,"_36":37,"_13":38},"id","computer-science/software-architecture/practical-knowledges/modularity/cohesion","slug","title","Cohesion","path","Computer Science/Software Architecture/Practical Knowledges/Modularity/Cohesion","canonicalPath","/notes/computer-science/software-architecture/practical-knowledges/modularity/cohesion","folder","Computer Science","tags",[],"createdAt","2026-07-26T03:12:21.712Z","modifiedAt","excerpt","Cohesion adalah istilah yang digunakan untuk menunjukkan seberapa terkait bagian-bagian yang ada di dalam suatu modul. Idealnya, suatu modul perlu mencakup segala hal yang terkait kuat dengannya, itu terjadi ketika satu ","html","

Cohesion adalah istilah yang digunakan untuk menunjukkan seberapa terkait bagian-bagian yang ada di dalam suatu modul.

Idealnya, suatu modul perlu mencakup segala hal yang terkait kuat dengannya, itu terjadi ketika satu bagian sangat bergantung ke bagian lain untuk dapat bekerja. Memecah modul yang punya cohesion cukup kuat berarti meningkatkan coupling dan mengurangi keterbacaan codebase.

Cohesion punya beberapa jenis, sebagai berikut:

Walaupun jenisnya banyak, Cohesion adalah metrik penilaian yang kurang presisi dibanding dengan Coupling. Untuk melatih Architectural Thinking terkait Cohesion, bisa dengan Study Cases yang ada.

Para ilmuan komputer sudah mengembangkan metrik pengukuran yang bagus untuk menilai cohesion, khususnya fenomena Lack of Cohesion. Sistem pengukuran yang cukup terkenal adalah Chidamber and Kemerer Object-Oriented Metrics Suite yang dapat digunakan untuk mengukur aspek-aspek tertentu dalam sistem Object-Oriented.

","outgoing",[42,43,44,45,46,47,48,39,49,41,50],[39,40,41],"computer-science/software-architecture/practical-knowledges/modularity/coupling","computer-science/software-architecture/practical-knowledges/modularity/measuring-modularity","computer-science/software-architecture/practical-knowledges/modularity/study-cases","computer-science/software-architecture/practical-knowledges/modularity/functional-cohesion","computer-science/software-architecture/practical-knowledges/modularity/sequential-cohesion","computer-science/software-architecture/practical-knowledges/modularity/communicational-cohesion","computer-science/software-architecture/practical-knowledges/modularity/procedural-cohesion","computer-science/software-architecture/practical-knowledges/modularity/temporal-cohesion","computer-science/software-architecture/practical-knowledges/modularity/logical-cohesion","computer-science/software-architecture/theoretical-knowledges/experts-quotes/coincidental-cohesion","computer-science/software-architecture/theoretical-knowledges/architectural-thinking/architectural-thinking","computer-science/software-architecture/practical-knowledges/modularity/chidamber-and-kemerer-object-oriented-metrics-suite","Study Cases","Computer Science/Software Architecture/Practical Knowledges/Modularity/Study Cases","/notes/computer-science/software-architecture/practical-knowledges/modularity/study-cases",[],"2026-07-26T03:12:21.716Z","Berikut adalah studi kasus terkait [[Cohesion]]: [[Customer & Order]]","

Berikut adalah studi kasus terkait Cohesion:

Customer & Order

",[17,60],[17],"computer-science/software-architecture/practical-knowledges/modularity/customer-and-order","profile",{"_16":63,"_64":61,"_65":66,"_67":68,"_69":70,"_71":72,"_29":73,"_74":75},"6954a19b11e7fe6da253c845","type","identity",{"_112":113,"_114":115,"_116":117,"_118":119},"contact",{"_104":105,"_106":107},"seo",{"_19":88,"_89":90,"_91":92,"_93":94,"_95":96,"_97":98},"bio",{"_76":77,"_78":79,"_80":81,"_82":83,"_84":85,"_86":87},"2025-12-31T04:07:55.862Z","updatedAt","2026-07-28T08:55:52.260Z","p1","Maulana Hafidz Ismail is an engineer who believes technology isn't just about efficiency. It's about resistance.","p2","While the world optimizes for profit, he builds to question the system itself: in education, work, and how we define value.","p3","His background blends engineering precision with entrepreneurial instinct. He has worked across software development, database systems, and AI, always driven by one goal: to make tools that actually serve people, not the hierarchy itself.","closing","This site is his lab. He writes journals to document a process, articles to share thought, and papers to formalize the things he learns.","tagline","Some ideas fail, some evolve, all of them teach.","callToAction","If you're building, rebelling, or just thinking about how to make things better, you're already part of the conversation.","Maulana Hafidz","description","Technical articles, engineering notes, system design explorations, and project documentation by Maulana Hafidz Ismail, an Engineer documenting real software systems.","shortDescription","Maulana Hafidz Ismail is an Engineer and Entrepreneur in training. Redefining fairness in education, work, and governance.","url","https://maulanahafidz.com","image","https://maulanahafidz.com/og-image.jpg","keywords",[99,100,101,102,103],"Meta Engineer","Entrepreneur","Software Engineer","AI Developer","System Designer","email","contact@maulanahafidz.com","socials",{"_108":109,"_110":111},"github","https://github.com/imhefizh/","linkedin","https://www.linkedin.com/in/maulana-hafidz-ismail/","fullName","Maulana Hafidz Ismail","shortName","ImHefizh","titles",[120,121],"subtitle","Building systems that question the system.","Software Engineering","Entrepreneurship","nonce","14bbfdd89adc4478b6f29a881a6b00b4","language","EN"]

Linked mentions