This Readiness Checklist is used to help Science Program assess where a person/group is in their cloud journey.
We don't expect everyone to be experts in all things, but the way we approach a Pathfinder greatly depends on the level of knowledge, skill, and interest in the various methodologies and technologies we're promoting.
Review the SSC-SP Cloud Terms of Reference (ToR) first and ensure all are feasible
When assessing yourself against our Cloud offerings, there's certain expectations that need to be defined so that you can get the most out of your time.
What technical resources do you have for the build and assessment?
When working in the cloud, these are the common Cloud Roles
Cloud Practitioners are entrusted with managing the cloud computing architecture. Their role is based around cloud migration initiatives whilst reviewing workload architectures. Cloud Practitioners ideally serve as a connecting junction between the business side and the technical side of the cloud operations. Hence, it is also under their authority to oversee that the technical findings of cloud operations are closely aligned with the business objectives of the plan.
In short, Cloud Developers create applications that are served from the cloud. The work they do is very similar to software engineers or web engineers, except that the programs Cloud Developers make run on cloud platforms. This adds an extra layer of complication (especially in architecting the systems) for matters like security and efficiency.
The day-to-day work of a Cloud Developer is similar to that of any software engineer; they will spend time analyzing customer needs, designing systems and solutions, coding, and debugging.
Cloud computing architecture refers to the components and subcomponents required for cloud computing. These components typically consist of a front end platform, back end platforms, a cloud-based delivery, and a network. Combined, these components make up cloud computing architecture. Cloud solutions design is based on architectural procedures and methods that have been developed over the last 20 or so years.
A Solution Architect is responsible for converting the technical requirements of a project into the architecture and design that will guide the final product. Often, Solution Architect are also responsible for bridging the gaps between complex business problems and solutions in the cloud. Other members of a technology team, including SysOps Administrators and Cloud Developers, work with the Solution Architect to ensure that the right technology or technologies are being built.
A SysOps Administrator is responsible for managing and maintaining the cloud infrastructure services and servers in mixed software environments. They lead and oversee the computing environment to meet the needs of the pathfinder. The administrator must have strong technical knowledge of various cloud offerings, including IaaS, PaaS, and SaaS.
Their duties include deploying and configuring systems, setting up core cloud infrastructure, balancing workloads, and monitoring and altering systems according to established methodology. They also select and implement cost-effective cloud-based systems that meet the technical requirements of the pathfinder.
Here are some things to think about before completing the ‘Technical intake’ form:
Do you have an exit strategy?
What is the sensitivity of the data and access required?
This checklist is to assess client readiness; you need to know this information, but it is not a document we will be using for the project documents. We will not be tracking the details, nor do we expect it to be filled out. We will gather this information in other forms throughout the intake submission.