Cloud Computing Assignment: Architecting Solutions To The Risks

Task: As a result of your work analysing their existing systems, PowerUpOnTheRoof Inc has now engaged your company toproduce a detailed, low-level implementation design to help them transition to cloud-based services. The scopingdocument you produced was enough to convince Melon Tusk that the general idea of moving services into “thecloud” was technically possible, and, at least in general terms, also reasonable from a business perspective. Younow need to take this one step further, and produce a detailed design document that could be given to anengineering team to evaluate and implement.Your detailed design will take the form of a document containing, at a minimum, the following information: As a result of your work analysing their existing systems, PowerUpOnTheRoof Inc has now engaged your company to produce a detailed, low-level implementation design to help them transition to cloud-based services. The scoping document you produced was enough to convince Melon Tusk that the general idea of moving services into “the cloud” was technically possible, and, at least in general terms, also reasonable from a business perspective. You now need to take this one step further, and produce a detailed design document that could be given to an engineering team to evaluate and implement. Your detailed design will take the form of a document containing, at a minimum, the following information: . An introduction which makes clear reference to your findings/recommendations from Assessment Task #2. These will be expected to be refined in your detailed design. . A detailed design for each of the individual PowerUpOnTheRoof nc. services being transitioned (either fully, or partially) from on-premises to cloud-delivered. For each PowerUpOnTheRoof Inc. service under consideration, your detailed design should document: The elements considered in this part of your design The cloud provider product(s) being used to implement this service, Justification of your design choice(s), including specific reference to product fit to both technical and business aspects of PowerlipOnTheRoof Inc. services. If there are alternative implementation approaches, you should state you recommended approach, and clearly explain why you are making that recommendation over the other possibilities. In many real-world cases, you need to make design decisions based on incomplete information or seemingly equivalent design candidates. By documenting why you are making a particular recommendation, you are enabling future engineers/architects to understand your design, and even to refine/change your design based on extra information which you didn’t have at the time. A detailed configuration for any cloud-provider products needed to implement your design. It’s not enough to say “Implement this using Product X; you need to demonstrate how that product should be configured to meet the goals of delivering this particular PowerUpOnTheRoof Inc. service, and why that particular configuration is the best one for this project. Any compromises/concerns/issues/interactions to be aware of for implementation and ongoing operations. A viable transition plan for this service. This does not have to be a step-by-step plan, but should be sufficient to show that you have considered how this particular service can be practically transitioned, and what the implications of doing so will be for the business. A clear statement of costs for this component over time. . A detailed design for any service(s) to be shared or common between other elements of your design, In addition to the detailed design requirements stated above for standalone services, you should also document: Rationale for why these are common/shared The estimated contribution of each dependent service to resource utilisation. . Any implementation dependencies, sequencing and/or timing which a Project Manager in charge of implementation would need to be aware of. For example, you should note ¡fa particular service requires a 3 week lead-time after ordering. Whilst you are not acting as the project manager here, a general schedule of implementation should be produced and included to allow you to verify implementation feasibility and identify any critical areas that might prevent a smooth implementation. . The criteria to be used to measure/quantify the success (or otherwise) of your project. You do not have to actually perform any measurements, only define your success criteria sufficiently that an independent third party could objectively perform the actual measurement. Where Assessment Task #2 was specifically targeted to C-level executives, Assessment Task #4 is to be targeted to a cross-functional engineering team which has the following structure: . A Project Manager, reporting to the PowerUpOnTheRoof mc, CTO (Chief Technical Officer) . A Senior Engineer with solid knowledge and experience of the project . Up to twelve (12) experienced engineers who have some previous experience with building and operating services “in the cloud” for the particular provider being used. This includes a mix of system administrators, network engineers, and operations staff. . A technical and a management representative from each of the existing teams delivering the IT services at PowerUpOnTheRoof Inc. These representatives are on the team to provide answers about the existing services, and to assist in transition planning for their service. Management has guaranteed that existing staff for transitioned services will not lose their jobs; these staff are actually looking forward to helping and learning about running their systems ‘in the cloud’. Your detailed design needs to be understood and implemented by this team.

Subject Name: Computer Science

Level: Undergraduate

If you want the solution to this assignment or want to discuss any other assignment or course you may contact us directly at order@bestacademicexperts.org or message us on Whatsapp or Viber at +91-9303607402 (http://api.whatsapp.com/send?phone=919303607402&text=Hello%20 )