Why standard patterns?
Theory and practice show the benefits of setting things up the same way. For example, it improves manageability in an organization if you keep organizational parts uniform. People are more easily interchangeable due to shorter learning time. To govern, a model must be available of the governed system, and this is quicker to develop if it uses standard patterns that are recognizable.
In information science, standard patterns help in the unambiguous documentation of information and recognition of information (partly through an agreed syntax). In this way, for example, reading the user manual and also operating devices automatically becomes logical, just think of color use and position of certain controls. If the stop button is suddenly green and the start button red then we get accidents
Standard patterns often grow into officially recognized standards. Deviation is not allowed and if something changes it applies to all applications.
Standard patterns are typically a “design” aspect
Examples of good and bad default patterns
[1] Source Wikipedia
Application of standard patterns in construction
Jaap van Rees [2] mentions two target groups here:
Maar als de voordelen zo evident zijn waarom wordt er dan toch steeds afgeweken van de standaard?[2] De informatiearchitect, van Rees en Wisse, Kluwer, 1995.
Standard patterns and creative freedom
Standards conflict with the creative design process. Standard patterns must be converted into standard ways of thinking, and that takes time. Design decisions are framed by prescribed standard patterns. In a standard, an architecture or end-user requirements.
Read the other information science principles here:
1 Meaningless identity designation
2 Decoupling points for complexity reduction and flexibility, maximizing independence of components
3 Language consistency
4 Clear distribution of responsibilities and functional separation for administration
5 Delegating decision-making authority as low as possible
6 Detaching authorization from identification/authentication
7 Single registration of master data
8 Separating data and metadata in storage and processing
9 Applying standard patterns without deviations
10 Separating application function from data storage
11 Device-independent development
12 Choose a Storage Structure
13 No hidden interfaces
