Abstract:
Software exists to change the behaviour of machines. In the world of business, software either helps to generate income or to save costs for current operations. As programmers, we often misinterpret our main responsibilities to always focus on behaviour, but there is a more important concern.
In this paper, we will explore the importance of structure and maintainability of the software, over adding behaviour. Although behaviour is the reason why the job of software developer exists, structure must be the main priority, but also unbeknownst to the customer that it is the focus.
We will also investigate the importance of expressing organisational interactions and the boundaries around them through ‘bounded contexts’ borrowed from the Domain Driven Design philosophy.
