Reacties (2)

Often the best way to express a design is by means of a visual model. There's quite some modeling languages around, to name just a few: Archimate, UML, BPMN, EPC, IDEF, Use case maps, E3value. The complexity of the average language (an important improvement area) forces the architect to look for a tool to support his modeling effort. Architects who don't like the concept of being restricted to a single language and / or tool (a good habit I believe) will not likely invest in expensive tools.

Reacties (2)

Steeds meer mensen lopen rond met een (hardware) token aan hun sleutelbos. Ik ook. Met behulp van zo’n hardware token  - waarop een dynamische pincode te lezen is - kun je, in combinatie met je persoonlijke pincode, bijvoorbeeld toegang krijgen tot het beveiligde netwerk van je organisatie. Er kleven echter de nodige nadelen aan zo’n token. Ik stel een alternatieve oplossing voor die deze problemen niet heeft. Deze oplossing is gebaseerd op twee ideeën.

Reacties (11)

Reacties (2)

Reacties (2)

Research indicates that the most effective IT governance approach is a federative approach. In this approach, IT guidelines are developed at enterprise level but the actual IT decisions are made decentral. The pure centralised model however appears to be more popular, but less successful. In an article about "Lessons from Iraq and Katrina", Bill Hall states that "From the organizational point of view, the processes of orientation and decision making must be moved closer to the periphery, where the deciders and actors can react faster and more accurately within the limits of what they are capable of observing."

Schrijf als eerste een reactie

Schrijf als eerste een reactie

To date, architects very often operate as soloists. Soloists with a knowledge of construction paradigms, patterns, technologies, methods, etc. But as the construction space keeps expanding, the required knowledge is increasing: technology stacks and tiers are added, construction techniques evolve, the line between off-the-shelve and bespoke development is fading and reusable services are becoming commodities and their number growing rapidly. As a result the architect (and engineering) population will specialise more and more.

Schrijf als eerste een reactie

The future will bring more and more surprising products based on the reuse of digital 'residue'. These residue based products are products created on the residue of other products. To illustrate let me give you some examples:
- mobile phone positioning data (a residue mobile phone users leave when then are linked to the network) to calculate car traffic; a valuable input for car navigation devices (e.g. Vodafone and TomTom);
- (tagged) bookmarks collected by individual users in their browser can be used to build resource taxonomies (e.g. del.icio.us, mypip.com). An intranet version would be a simple and probably very effective way to manage corporate knowledge (especialy when it also enables highlighting).
- gaming data (e.g. a game to find similar characteristics) to create picture indexes; a valuable input for a search engine wanting to improve the relevance of image search (e.g. the espgame.org and peekaboom.org).

Schrijf als eerste een reactie

Applications get more and more detached form the infrastructure they are running on. The same goes for the architectures of both. In the most extreme scenario, architectural design choices related to the infrastructure are made completely independent from the applications running on the infrastructure. For applications, the infrastructure in most cases is a given. One could compare the relationship between applications and the infrastructure with the way electrical appliciances relate to electricity (loosely coupled with plugs and sockets).

Schrijf als eerste een reactie