Too often these days, organizations plow ahead with cloud computing projects, without considering how it fits into the rest of the enterprise. An enterprise architecture approach will help align cloud plans with the short-term and long-term needs of the organization -- just as it has helped with on-premises systems.
In his latest book, titled Architecting the Cloud: Design Decisions for Cloud Computing Service Models, Mike Kavis, a seasoned chief technology officer and IT architect, shows how cloud proponents can map out their cloud plans.
Mike identifies the five key questions that are essential to cloud architectural planning:
1) Identify the problem statement (why): "The single most important question to answer," Kavis observes. While cloud is a no-brainer for startups, more established enterprises need to evaluate how cloud will benefit the business. Ultimately, a cloud-based solution may focus on one specific business problem where existing systems aren't delivering satisfactory results. An enterprise may end up with numerous cloud models to address varying requirements.
2) Evaluate user characteristics (who): "Users may be people or systems," says Kavis. "Identifying the actors helps discover what organizations interact with the overall system."
3) Identify business and technical requirements (what): Such requirements "describe how the system, application, and service should function," and include points such as what data the system must process, how the screens should operate, how the workflow operates, system outputs, who has access, and pertinent regulations.
4) Visualize the service consumer experience (where): Just as building architects need to understand the laws and conditions of where they are building a house, cloud architects "need to become familiar with the laws and regulations that pertain to their business and their data." Local and national data laws may affect how the cloud is built and managed. Another consideration: "what devices and touch points are these cloud services being accessed by?"
5) Identify the project constraints (when and with what): Project deadlines are one of the most critical aspects of a cloud project, Kavis relates. "Sometimes what's best for the architecture is not best for the business."
6) Understand current state constraints (how): This is all about organizational readiness, Kavis relates. "Does the company have the skills in-house?" Are accounting and finance willing and able to shift from a capital expenditure to an operational (pay-as-you-go) model?" One mistake Kavis says he has seen a lot of cloud proponents make is leaving the HR department out of the process.