The profession of Enterprise Architecture struggles, in part, because we have done a poor job of outlining our value proposition to senior leaders of our respective companies. I have posted occasionally about the value proposition of EA. I was a lead author on the FEAPO perspectives paper that discusses the value of EA. However, I want to highlight one value proposition that is often missed: the human side of envisioning.
While we know that software can expose data, we sometimes forget that writing software can expose data.
When a system gets deployed, we typically build a development environment, one or more test environments, and a production environment. No surprises there. However, developing software with sample data, instead of “real” data, can allow defects that are difficult to catch. On the other hand, using “real” data (typically a subset of production data) runs considerable data security risks. In this post, I’ll discuss the notion of building a general purpose deidentification tool specifically for software development and DevOps purposes. (more…)
There are surprisingly few researchers publishing articles about Enterprise Architecture from universities. Even well considered programs like Penn State and MIT may only publish four or five papers a year. Therefore, when a single researcher (a doctoral candidate at a well regarded university) publishes no fewer than fourteen separate papers on Enterprise Architecture over the course of three years, a few directly through the British Computer Society website, folks like me notice.
Unfortunately, as this article will show, this researcher appears to be building a body of sloppy work that he promotes widely, potentially harming both the profession of Enterprise Architecture and the reputation of the British Computer Society for promoting him.