Over the last decade, the trend for customers is to buy code and not only the software resulting out of it. At the same time as code becomes the product its quality is being questioned and becomes subject to quality measurement. Requirements are being applied to the source code itself. To support flexibility, readability and independency for the customer, tools verify the code quality and have been directly impacted by the contract hence the payment. Checkstyles, coding conventions, class cycling and documentation are essentials to sell a good source code, creating a value for the customer. 

Software and its code works like a clockwork. Small parts gather to a bigger entity operating one or more tasks, several of those entities gather to work together and produce the result. All those single commands and conditions form the foundation of software. Unlike a clockwork, the source code should not be in a black box nor should it be a compact and concentrated. Its essential parts and their function must be easy to identify. In order to be able to modify, exchange or extend all those parts, separation of concern is the key to success. Abstraction layer, packaging and modularity are all method to provide separation of concern.