Footer Navigation

Header Navigation

Separating application function from data storage

Construction principles (10)

Construction principles for the IT architect: (10) Separating application function from data storage

In this series of blogs, I dwell on the still valid information science construction principles that guarantee better ‘information building’. This 10th blog in the series continues with the first informatics principle (for the distinction, see my <a href="https://highberg.com/insights/construction-principles-for-the-information-professional" target="_blank" rel="noreferrer noopener">starting blog</a>). This one is about the construction of data processing. 
We don't dwell on it but every screen we process information on hides an underlying construct that extracts data from a storage and allows us to access or modify this data or add new data. If the processing function and the data storage are separated, this has great advantages. In fact, this is the information science principle of decoupling but applied in computing.

Rutger Gooszen

Battling invisible cyber threats in our digital realm

That other pandemic...

Pexels tyler lastovich 396947

The Corona crisis has once again made us aware of the vulnerability of our (open) society. Yet we have known for much longer that vulnerability to viruses also lurks in an entirely different world; our digital society.

Towards quality with recognized standards

Professionalizing IT: Quality from within

Professionalizing IT: quality from within

What do a building architect, lawyer, general practitioner and chartered accountant have in common? On the face of it, not much. But if you look more closely, they have all undergone mandatory and recognized training and have had to qualify to use their title. That title is protected and enshrined in law. They submit to a professional code and disciplinary law. In other words, their clients know what to expect and can complain about professional performance if they are not satisfied.

Orchestrating architecture in Agile with SAFe framework

The architect role within SAFe in a nutshell

the-architect-role-within-safe-in-a-nutshell

When a system is developed according to SCRUM by a single team, quality is in the hands of the team. 'Quality arises from practice' is the thinking, because team members want to build quality software. The role of architect, as a designer who provides direction for development, is a team role that is performed collaboratively through communication and interaction on a sprint-by-sprint basis.

What do clients expect from the "lead architect" in complex programs?

On uncertain destinations

on-uncertain-destinations

Construction principles for information systems that ensure better information structures

Construction principles 4

construction-principles-for-information-professionals-4-responsibility-allocation-and-segregation-of-duties

In this series of blogs, I will focus on the enduring construction principles for information systems that ensure better "information structures." These principles have sometimes been forgotten in the rush of advancing technology, resulting in unstable or poorly maintainable and expandable "information structures." This time, I'll discuss the importance of clear responsibility allocation and segregation of duties within an organization. A recent incident at the municipality of The Hague, where an employee was able to forge passports for criminals due to inadequate segregation of duties in the work processes, serves as a reminder of the consequences that can arise when things go wrong.

Construction principles for information professionals: (4) Responsibility allocation and segregation of duties

Principles of information management that ensure better "information structures"

Construction principles 5

construction-principles-of-information-professionals-5-decentralizing-decision-making-within-the-organization

In this series of blogs, I delve into the enduring principles of information management that ensure better "information structures." Sometimes, these principles have been forgotten amidst the rapid advancement of technology, resulting in unstable or poorly maintainable "information structures." This time, I'll discuss the advantages of delegating decision-making authority as low as possible within the organization. The ongoing conflict between Russia and Ukraine serves as a daily reminder of the consequences of blindly following top-down decisions by Russian soldiers, while Ukraine's approach is more innovative and locally driven.

Construction principles of information professionals: (5) Decentralizing decision-making within the organization

Van Rees distinguished between the roles of architect and constructor.

Construction principles

construction-principles-for-the-information-professional

As early as the 1990s, Jaap van Rees argued that there was a need for information science as a discipline alongside computer science[1]. According to him, information science emerged from computer science in a similar way that traffic engineering arose from automotive technology. With only a few cars, there's not much coordination required. However, as the number of cars increases, the skill of their integrated application becomes indispensable. Van Rees distinguished between the roles of architect and constructor. The architect focuses on "beauty," quality, and fitting the design into its environment. The constructor ensures feasibility and functionality within technological constraints.

Construction principles for the information professional

Principles of information architecture that ensure better "information structures"

Construction principles 3

principles-of-construction-for-information-science-1-meaningless-identity-designation

In this series of blogs, I will delve into the enduring principles of information architecture that ensure better "information structures." Sometimes, these principles have been overlooked in the rapid advancement of technology. In this blog, I will focus on the necessity of clarity and consistency in language within a "system" or "domain" as aspects such as privacy protection, information security, and information management heavily depend on it.

Construction principles for information professionals: (3) Unambiguous and consistent language

Construction principles of information science that ensure better "information structures"

Construction principles 2

construction-principles-for-information-professionals-2-decoupling-for-complexity-reduction-and-flexibility

In this series of blogs, I will focus on the enduring construction principles of information science that ensure better "information structures." These principles have sometimes been forgotten in the rapid progress of technology, resulting in unstable or poorly maintainable and extensible "information structures." In this second blog, I will delve into the art of decoupling.

A well-designed system has so-called decoupling points, imaginary divisions in the complexity of the whole, which allow the parts to be developed, implemented, and (eventually) replaced as independently as possible. This promotes interoperability without central control. In its ultimate form, this is known as "service-oriented architecture (SOA)," which has been developed in various forms.

Construction principles for information professionals (2): Decoupling for complexity reduction and flexibility

Architecture

IT Governance

Rutger transparant 1 290x582

Principal Architect

Rutger has over 15 years of experience as a Lead Architect/Business Architect in complex chains and in coaching a team of architects to develop and promote a chain or program architecture. He has experience with both traditional and agile transformation projects. Rutger is a certified CISA, TOGAF, and SAFe architect and can methodically design and validate a system. Out of social involvement, he is a board member and co-initiator of "The Independent Architect" through the PMDDA foundation and he is also active in KNVI and DANW. Rutger's motto: getting the job done! Want to know more? Connect with Rutger on <a href="https://www.linkedin.com/in/rutgergooszen/" target="_blank" rel="noreferrer noopener">LinkedIn</a>.

Rutger Gooszen

Principal Architect

Capabilities

Related insights