3.4 – Conceptual Integrity

3.4 – Conceptual Integrity

 

Conceptual integrity is about creating consistent software. It is making decisions about how your system will be designed and implemented so that even if multiple people worked on the software, it would seem as if there was only one mind guiding all the work. 

 

Adopting certain agile development practices like daily stand-up meetings and sprint retrospectives, where team members can agree to use certain libraries or methods when addressing certain issues, can help to maintain the consistency of the code. 

 

For example, team members can all follow a particular naming convention.

 

Much like using certain design principles, having a strong software design or architecture to guide how your software is organized creates consistency. 

Unifying concepts is also another approach to maintaining conceptual integrity.

 

How can code reviews help ensure conceptual integrity?

- Code reviews help find bugs in code.

- Code reivews allows programmers to review each other's code and let them revise code to make it more consistent with each other.