Inside Architecture

Notes on Enterprise Architecture, Business Alignment, Interesting Trends, and anything else that interests me this week...

Browse by Tags

Tagged Content List
  • Blog Post: Do you perform Information Architecture or a Data Architecture?

    So, full disclosure, I care about Wikipedia.  Call me dumb, I know.  Wikipedia has been described, alternatively, as the best platform ever invented for fostering useless arguments among ignorant people /and/ the most successful encyclopedia effort of all time.  The truth, as always, lies...
  • Blog Post: Being Forgotten in the Internet of Things

    We all know that Google lost a landmark legal case recently.  As of now, a citizen of Europe has the “right to be forgotten” on the Internet.  As of now, a citizen of Europe can ask Google to “forget” them, so that a search of their identity will not return embarrassing information from the...
  • Blog Post: EA Schools of Thought

    As an Enterprise Architect, I’m first and foremost a problem solver.  I don’t like to ignore problems.  Yet, it appears that EA as a field has a problem and I’m finding it tough to ignore it.  What is the problem?  If you judge by the 1500+messages that have flooded the Enterprise...
  • Blog Post: Essential Project–Open Source EA Metamodel

    One thing that often occurs when a team sets out to create an EA tool is that they create a metamodel that will be supported within the tool. As I pointed out in my last post , I would like to openly challenge tool makers to allow multiple simultaneous metamodels to exist, so that organizations can answer...
  • Blog Post: Can EA Data be independent of the Metamodel?

    One thing that I’ve come to appreciate is both the importance, and impermanence, of the Enterprise Architecture metamodel.  If that last sentence didn’t piss you off, you weren’t listening. I’ve found two common groups of Enterprise Architects: Folks who do not understand, or care, about EA metamodels...
  • Blog Post: Should some requirements be called out as “architectural” requirements?

    Some methodologies of software architecture, including EWITA , attempt to describe architectural processes in a manner that is quite separate from the development of software.  Is that valid? To whit, the first step in the EWITA process is described as “architectural requirements.” Yet, there doesn...
  • Blog Post: On the federated ownership of a conceptual domain

    As I mentioned in my last post , we have produced an interesting conceptual model of IT as a business, from Business Motivation all the way through to Operations.  For those of you who know I’m a SOA promoter: yes, I can represent a composite application in the repository. More importantly, I can...
  • Blog Post: Feedback requested: Information driven process design

    An esteemed associate of mine asked me recently if I believe that a conceptual information model, created and delivered independently from a process model, can be considered useful when attempting to improve a business.  In other words, if you have an conceptual information model, can you use it...
  • Blog Post: Alignment - the missing Viewpoint

    The (ISO Standard) RM-ODP model is a powerful and well reasoned mechanism for creating Architectural descriptions ("architectures"). Leveraging the IEEE-1471 taxonomy , and building out a visual style and standardized approach, there is tremendous value in learning and using this the RM-ODP (Reference...
  • Blog Post: Traceability, the Solution Model, and Metamodeling

    It is nice to point out, on occasion, when two different leaders in the architecture community are saying things that, when added together, become greater than the sum of their parts.  First off, my friend and colleague Gabriel Morgan recently described the business value of creating a single underlying...
  • Blog Post: Enterprise SOA needs a Federated Evolutionary Modeling Environment

    I've been thinking a lot lately about the gap between "what we have" and "what we need" in the Enterprise SOA space. I think I have a need that is not yet filled by software. (that I'm aware of). I put up a post back in June about the difficulty in creating a common information model in a large enterprise...
  • Blog Post: Building Conceptual Models, Building Relationships

    Building teamwork, at the enterprise level, is a tricky thing. As a project team comes together to solve a problem, hopefully you find yourself in the same position that I've found myself in many times: with smart experienced people, all motivated to succeed.  Microsoft IT is chock-full of folks...
  • Blog Post: Open Question: Common vocabulary: Blessing or Curse?

    Requirements are an interesting thing.  We cannot assume that we understand the business, and their needs, so we 'elicit requirements.'  And we write them down.  But "the business" is a collection of different people, and in order to be clear, we need to make sure that everyone...
Page 1 of 1 (13 items)