The crazy mind mapper... Inside Architecture. Since 2009, when I first published my open source metamodel of enterprise architecture (the Enterprise Business Motivation Model), I’ve had numerous conversations with architects, business analysts, consultants, technologists, and the occasional student about models. I frequently hear things like “I have an update to your model that makes it better,” to which I reply “cool, let’s see it.” After seeing about a dozen now, I’ve begun to realize that I need to ask better questions. Some models are simply more interesting than others. Some have relationships that are more appropriate for specific situations. (for example, one friend sent me his version of my model with specific elements related to government organizational structures and interrelationships). That is very interesting, because I can see a value in capturing distinctions related to different types of organizations. Those are the good examples.
I say “yes” in very narrow circumstances. “All models are wrong. Simplicity in practice. Richard Veryard on Architecture. Enterprise Architecture. It hit me the other day when I was speaking with a call center operator about my reservation. She was funny, smart, well informed and flew around her app. with the quickness of the chipmunk. She is the new breed of worker. Not the production worker that performs repetitive tasks, like data entry and responding to the same dumb information requests, anxious to get you off the phone to meet a call duration metric. No, our relentless offshoring, automation, and customer self-service is slowly eliminating this type of worker. We hear numbers like this consistently, and this from a Workforce Planning VP at a major Major Telecommunications company, “Today 70% of our inquiries are handled by self service (IVR, Web, or mobile) with only 30% that ever get to our call center.
But these calls that get through are really hard. What does this mean for enterprises? We will shortly publish a wave on DCM. IST: Enterprise Architecture. Institute For Enterprise Architecture Developments. Enterprise Architecture « Center for Information Systems Research - MIT Sloan School of Management. MIT CISR defines enterprise architecture as “the organizing logic for business process and IT capabilities reflecting the integration and standardization requirements of the firm’s operating model.” We view architecture as a strategic, rather than technical, exercise. A firm’s architecture describes a shared vision of how a firm will operate—thus providing a shared understanding of the role of IT. We have found enterprise architecture to be a critical tool for aligning IT and business strategy and for driving business value from IT. We emphasize three key concepts in our research: Enterprise Architecture Content on InfoQ. Enterprise Architecture.
Book:Enterprise Architecture.