Construction principles for the information professional

In its simplest form, this gives rise to a matrix with four elements. One element represents the architect of the organization as an information-processing entity, or the information professional architect. Additionally, there is the architect responsible for the means of information processing, known as the computer science architect. Regarding the constructor, the same distinction applies: an information professional constructor and a computer science constructor.

This classification remains relevant today when considering all the designations of IT specialists. It helps to better identify the quadrant in which someone operates based on their role and discipline. Moreover, individuals may be active in multiple quadrants as long as they remain aware of their position.

For the execution of their profession, they all apply principles.

The information professional architect determines which information principles are applicable to the design of the information-processing organization, while the constructor applies them as norms during construction and implementation. Construction principles are more universal because each design materializes in the tangible reality through construction. Something either works or it doesn’t—there’s no in-between. This makes it clear that a construction principle cannot defy the laws of nature. An inadequate structure collapses.

The interaction between architecture and construction lies in the advancement of technology. Different technologies enable different constructions. Consequently, the architect gains the ability and limitation of making alternative choices.

In a series of short columns, I aim to address the still-valid information construction principles that guarantee better information structures. Over the past decades, the emphasis has often been placed on the possibilities offered by advancing technology for these structures. The information science aspect has been somewhat overlooked, resulting in occasionally unstable or poorly maintainable “information structures.”

The following information principles will be covered:

1. Meaningless identity designation, read here.
2. Decoupling points for complexity reduction and flexibility, maximizing independence of components, read here.
3. Language consistency, read here.
4. Clear distribution of responsibilities and functional separation for administration, read here.
5. Delegating decision-making authority as low as possible, read here.
6. Detaching authorization from identification/authentication, read here.
7. Single registration of master data, read here.
8. Separating data and metadata in storage and processing, read here.
9. Applying standard patterns without deviations, read here.
10. Separating application function from data storage, read here.
11. Device-independent development, read here.
12. Choose a Storage Structure, read here.
13. No hidden interfaces, read here.

References:

[1] EAN 9789026721557 (*this book is only available in Dutch). He still makes the valid distinction between the study of information technology (computer science) and the study of information processing.