Practical software engineering foundations · Lesson 58 of 60 · Concept lesson · Optional

Software architecture

Software architecture is how a system is split into parts and how those parts depend on each other.

A common design uses layers, such as presentation, logic and data, where each layer only talks to the one below it.

Good architecture has low coupling, so parts depend on each other as little as possible, and high cohesion, so each part's contents belong together.

Picture it

presentation   screens, buttons
      |
logic          rules, decisions
      |
data           database, files

A layered design. Each layer only talks to the layer below it, so a change in one layer rarely spreads to the others.

Pick an answer for each question. You can retry as many times as you like.

Loading the questions…