23. Separation of Concerns Applied to Methods
The SEMAT approach to methods is fundamentally different to that used in the past. This can all be summed up with the phrase “separation of concerns.” Separation of concerns is a principle that you can apply when designing software systems to create systems that are made of nonoverlapping modules, each handling a distinct concern. Separation of concerns helps software systems become extensible and maintainable. Here, we apply the principle of separation of concerns (SoC) to methods, which means
• We specify a kernel
• We make extensions without changing or complicating the kernel
Not changing or complicating the kernel as you add extensions ensures that you, after learning the kernel, can count on ...