This blog is a new view to my earlier presented Data Value Chain-model. Data is an enterprise asset which represents value. The Data Value Chain visualizes and puts all data assets in sequence of increasing value. It is intended as a communication-tool to position our services and explain the opportunities and challenges of a data-related landscape.
Some time ago I wrote about the considerations to make when defining an Enterprise Architecture Repository (EAR). One of these considerations is the meta-model. I generally stick to the principle: “adhere to standards unless …”. This means that by default I would base an EAR on the industry standard ArchiMate.
Digital disruption requires for new priorities in ICT-strategy. From killer app to killer data – how to start:
My previous blog looked at datafication, a recent trend that suggests treating data as an enterprise asset. The blog proposed some extensions to the DAMA functional model. This blog presents a new Data Value Chain-model. As stated before, data is to be treated as an enterprise asset. And as assets represent a value, we would like to relate the value of assets to each other in a visual way. The model displays common data sets / stores and data related functions in sequence of increasing value.
Datafication is an unstoppable trend for the coming years. Its bottom line: data is as an asset instead of a by-product of processes and applications.
Companies like Facebook have caused an emphasis on the value of data – both commercially and strategically. New technologies allow to build applications instantly to support new business models and customer needs, what nowadays causes data to outlive applications.
The demand for software engineers exceeds supply. And this gap only will keep on growing for the next decade. Trends predict that the coming years the software development capacity decrease to less than 25% of the need. The call for more productive engineering methods is inevitable.
In de twee eerdere blogs uit deze serie over blockchain, ben ik ingegaan op wat het nu eigenlijk is, wat het bijzonder maakt en wanneer het gebruikt kan worden en wanneer juist niet. Dit laatste blog richt zich meer in detail op de toepassingen, transacties en platformen in relatie tot blockchain.
Eerder schreef ik over het fenomeen blockchain, wat het nu eigenlijk is, wat het zo bijzonder maakt en waarom er nog altijd een zweem van mystiek omheen lijkt te hangen. In dit blog ga ik verder in op de toepassing van blockchain: wat zijn de voor- en nadelen en – rekening houdend met deze nadelen – wanneer pas je blockchain toe?
Blockchain staat hoog op de hype-cycle van Gartner. En niet onterecht: alles wijst erop dat het de manier van transacties doen drastisch op zijn kop gaat zetten.
Iedereen kent inmiddels Bitcoin: de eerste en meest populaire BlockChain. Dit virtuele betaalmiddel heeft zich inmiddels een belangrijke positie verworven. Elke dag wordt er ruim $300 miljoen aan transacties in omgezet. Desondanks is deze crypto-currency nog altijd omgeven met een zweem van mystiek. Niet alleen omdat de bedenker ervan onbekend is. Of dat het veelvuldig gebruikt wordt op het ‘darkweb’, daar waar zakendoen zich aan het oog van de regelgeving onttrekt.
Enterprise Architecture may be hard to grasp. Especially for people who have little feeling with this topic. An analogy usually helps explaining it. One that works pretty fine to me, is a city. This city-analogy allows me to project map enterprise architecture on common life concepts. Both enterprise and city are comparable as they have goals, an organization structure, functions and processes. Buildings in the city resemble applications; roads the infrastructure; people and goods the data.This article dives a bit deeper into this comparison. It discusses and compares architectural aspects and roles (see also my blog on architecture roles)
