CSE Roadmap

Common tier · about 3 hours · 7 parts

Part 1 of 7 · 1 min read

Why this page comes second

In this module you will

  • Define a module and explain why architects care how code is grouped.
  • Describe cohesion, rank its seven kinds, and judge whether two features belong together.
  • Count afferent and efferent coupling and compute instability, abstractness and distance from the main sequence.
  • Name the kinds of connascence, and say which are weak, which are strong and why.
  • Use strength, locality and degree to decide what to fix first.

Every architecture style in the rest of this level is a way of grouping code and deciding how the groups talk to each other. To compare styles fairly, there must be a way to say how tightly two groups are tied. This page gives the measures. The book used is "Fundamentals of Software Architecture" (FSA), chapter 3. The numbers are made up to show the idea, unless the text names a book.