The analogy between the evolution of the electric energy industry and cloud computing is oftentimes used, and for good reason. It’s likely the most applicable predictor of where this industry is heading over the next 10-20 years. Although slight regional variances exist, it’s generally the case that I, as a consumer of electric power, can plug in my appliance anywhere in the world and expect it to work efficiently, safely, and reliably. Standards for voltage regulation, plug/outlet design, and circuit protection are mature and widely embraced, and the electric appliance industry can compete, and innovate, on a level playing field for the benefit of consumers worldwide. The clock radio in my office is one of Read more
Thoughts on developing a strategic plan for implementing EA programs, how to provide your teams with the technical skills needed to implement a service-oriented architecture, understanding what’s involved in creating a business architecture, and more.
Change at an architectural level is always transformational. But too often architects have struggled to demonstrate or realize this potential for making a significant, positive difference at the enterprise level. Instead, big changes are more frequently driven by the architectural opportunities from new technologies. This is starting to change, and leading enterprises are planning architectural change that genuinely combines the organizational, business, and technology perspectives. Enterprise transformation that successfully unites all three viewpoints requires a new technique to raise the architectural debate to the level of senior decision makers. Enterprise Patterns elevate the debate by: * Providing a means for aggregating viewpoints and lower level patterns into a holistic visualization of architectural possibilities. * Focusing Read more
Last week I wrote an Advisor for our Business & Enterprise Architecture practice about the role of the solution architect. I thought I’d share my overview of how that role compares to the enterprise architect’s. Is this how the roles are delineated in your company? Topic Solution Architecture Enterprise Architecture Scope Single solution or set of related solutions All current and future solutions and COTS Primary Goals Ensure that the solution fits within the enterprise context Define the enterprise context including business, information, application, and technology Responsibility Translates nonfunctional and functional requirements into design, within enterprise context Translates strategies into target architectures and roadmaps Tradeoffs Enterprisestrategy and goals vs. solution tactical and delivery requirements Prioritization and rationalization Read more
On that long list of venerable institutions primed for a high-tech overhaul, higher education is near the top. Its shortcomings are much discussed: universities are expensive, inaccessible, inflexible, and out of touch with the needs of students and the world economy. A diploma that demands four (or more) years on campus, long lectures, fend-for-yourself homework, and massive final exams seems as much a relic of the 19th century as of the 20th. Educating the millions of people that our future depends on will require not just a productivity boost but something fundamentally different. These days “something fundamentally different” usually involves the Internet. Decades of desultory experiments with “computer-aided education” have now yielded exciting, scalable, measurably Read more
Products and processes are two of the most vital components of a successful business. Useful, relevant, or innovative products are important for attracting and keeping customers. Efficient and effective processes are crucial to making the customer experience enjoyable and worthwhile. Product and process should therefore be included as key components in any business architecture. But, too often, product and process are not given the architectural priority they deserve. While physical products such as cars or planes are highly engineered, enterprise architects tend to overlook the architecture of information-based products and view them instead as the domain of business managers. (Note that physical products, such as the engineering of cars or computers, are more likely to Read more
Governance is a fundamental (perhaps the fundamental) process within EA to connect the business aspirations with the current and future enterprise reality. Governance is probably also the most contentious EA process: a necessary evil at best or a dysfunctional rubber stamp or change-prevention mechanism at worst. The current focus on enterprise agility provides a context for refining governance. The conclusion is not to throw out governance or to diminish EA to a laissez-faire view of awareness and simplistic control of the enterprise. Rather, the conclusion is that governance can be made effective, compelling, and a value-add to agility. Part of the complexity with governance is that it varies widely and is a tradeoff of constraints Read more
Welcome to the seventh-anniversary edition of my enterprise architect’s New Year’s resolutions. I hope it will give you food for thought and some inspiration for architectural growth in 2012. Understand business analytics. The past few years have seen dramatic increases in the capabilities of business intelligence systems, accompanied by decreases in costs, to the point where most organizations can easily afford to take advantage of business analytics. The problem is that the information that these systems need to analyze is not readily available. While this is not a trivial problem to solve, it does present a major opportunity for enterprise architecture. When we provide management or decision makers with information that they don’t currently have Read more