Reference no: EM13950583 , Length: word count:4000
Design Report:
In this assignment you are asked to provide a solution to a hypothetical scenario. The assignment implies that you have a good understanding of the Cloud Reference Model and its segmentation into the three key market offerings (IaaS, PaaS, and SaaS), and the key patterns utilized in designing Cloud Computing applications.
Assessment Rules and Submission Policy (please read):
This is an individual task. While collaborative work is encouraged collusion/copying is not permitted and constitutes plagiarism.
All references should be correctly cited and included using a standard form of referencing.
Case Study: Improve Service Performance
Introduction
The assignment does not require any "implementation" work (i.e. you will not be expected to deliver a working application but simply its design). Despite this, the practice sessions have exposed you to some of the technologies and methodologies that are involved in building applications for the Cloud. Use the learning developed in those sessions to inform your design.
The Italian Government has just hired you to lead an important project. The scope of the project is to review in real time the performance of some its key services, provided to the general public.
Context
In the past years, the performance of the Taxation Office was only evaluated upon collected data from marketing research companies, which involved sampling data from phone interviews.
The Government now wants to gather more information about how to improve the service. Part of this is based on collecting feedback, but the Government recognizes that by mining the social media they could gather much more valuable information provided by the public.
Project Goal and Scope
You have been engaged to devise an endtoend solution for gathering and presenting information.
Key Features
1. Develop a service, which people can use to provide feedback - such as a feedback form.
2. Mine data from social media, in particular Twitter.
3. Provide an interface for government staff to visualize the collected information and do additional analytics.
Some Aspects to Consider
1. Because the feedback feature will be integrated into the current web application that the Government utilizes to provide lodgment and Q&A online, it will have access to the users confidential data to provide a better context for the feedback. This information needs to be "managed with care" as there are additional constraints related to where it can be stored and in which form. In particular, there are "Data Sovereignty" constraints and the information cannot leave the country, while at rest.
2. The Government cannot estimate with confidence what the longevity of this application will be. In particular, they do not know whether such project will be needed after an initial trial of 6 months. Therefore, it is not willing to make huge upfront investments (e.g. extend their data centers now running at full capacity, or buy a software solution). Because of that, it is particularly keen to exploit Cloud Computing technologies, but it has given you freedom to devise what the best approach will be.
3. During the development of the solution, you will be given access to the public Twitter feed, which only gives you access to a small portion (i.e. 10%) of the total number of tweets. Once in production, or when eventually the application will be deemed valuable, the Government plans to access the entire Twitter feed, thus creating a considerable increase in the data volumes that will need to be handled. For your reference, monitoring a single twitter keyword could generate at least 100 MB/day on a public feed.
4. The user experience of the public citizen is particularly important to the Government, as the organization tries to improve its services and image. Therefore, a key requirement is the performance of the feedback function, which needs to run without delays and provide useful information to the user. Less pressure is perceived in the administrative user interface for the Government staff, as it will be subject to less user demand, but potentially deal with much larger datasets.
What You Are Expected to Deliver
Produce a report that incorporates the following aspects:
1. Devise a comprehensive architecture of the system that includes the three capabilities and how they relate and interact with each other.
2. Design of each the three capabilities in more detail by highlighting the components needed to address the business concerns discussed above.
3. Discussion about the different design choices made. This implies that you motivate the reason of the choices you have made.
4. A discussion on how you decide to use Cloud Computing technologies (and which ones from the Cloud Reference Model) and their implication on the price and the charges that you will eventually apply to the Government. In particular, which specific pricing scheme you will propose and how will you make profit?
A Little Help
1. The "project brief" in this document has highlighted some key aspects to point you in the right direction. For instance data sovereignty and scalability of the application are particularly important, but they are not the only ones. Please keep in mind these aspects as you develop your solution.
2. Even though, not expressed explicitly, the solution needs to live on "Cloud Computing technologies" and the discussions and case studies that have been presented during lectures 3, 4, 5, 6, 7 and 8 are of particular importance to complete the assignment.
3. The practice sessions have highlighted some technologies that could be of help in devising the architecture of some of the components. In particular, NodeRed, NoSQL databases. You might want to consider them to design some of the components of the solution as an option.
Necessary Inclusions in the Report:
Report Structure
The report is well structured in sections with headings and includes:
1. Introduction to the problem and the overall solution design
2. Diagrams that explain visually all the components of the solution design
3. A section for each of the criterion organized in sub-headings were necessary.
4. Comparison tables where appropriate.
5. Referencing is comprehensive.
Length
The total length of the report is within the limits prescribed in the limits (~4000 words, 15 pages max)
Solution Architecture (end-to-end)
Breadth and Completeness
The presentation of the solution architecture is complete and well structured. It not only gives the understanding at a high level but provides additional insights with the appropriate level of details.
Decisions and Motivations
The key architectural choices are described and a motivation for each of them is provided and comparison with other choices are added.
Requirements
All the requirements are covered and additional aspects discussed in the lectures relevant to the scenario but not directly mentioned are touched and discussed.
Feedback Service
Discussion
The architecture and the design of the components are discussed comprehensively. Not only the appropriated level of detail is provided but also the interaction with the other components is highlighted. Architectural Aspects
Scalability, availability, and security concerns are properly discussed with a motivation of the choices made and a comparison with other possible alternatives is presented.
In addition to the motivation a trade-off analysis is provided. In particular, by discussing the implications on price and deployment challenges.
Social Media Integration
Discussion
The architecture and the design of the components are discussed comprehensively. Not only the appropriated level of detail is provided but also the interaction with the other components is highlighted.
Architectural Aspects
Scalability, availability, and security concerns are properly discussed with a motivation of the choices made and a comparison with other possible alternatives is presented.
In addition to the motivation a trade-off analysis is provided. In particular, by discussing the implications on price and deployment challenges.
Government User Interface
Discussion
The architecture and the design of the components are discussed comprehensively. Not only the appropriated level of detail is provided but also the interaction with the other components is highlighted.
Architectural Aspects
Scalability, availability, and security concerns are properly discussed with a motivation of the choices made and a comparison with other possible alternatives is presented.
In addition to the motivation a trade-off analysis is provided. In particular, by discussing the implications on price and deployment challenges.
Critical Analysis
Problem Analysis
The analysis of the business scenario is well thought and detailed. A clear explanation of the key requirement driving the solution is presented.
The business scenario is properly decomposed in its aspects and clear path to the elements in the solution design addressing them is provided.
Solution Analysis
All the architectural and design decisions discussed in the report are compared with alternative options and an appropriate discussion of the impact on solution is presented (e.g. pros/cons).
Particular attention is given to the trade-off of the choice made and convincing motivation is provided.