Deakin University - Cloud and SOA Web Application Project Diary Part A
VerifiedAdded on 2022/09/17
|17
|3696
|26
Project
AI Summary
This project diary details the development plan for a web application utilizing Service-Oriented Architecture (SOA) and cloud computing technologies. The project aims to create a cost-effective and efficient web application, similar to those hosted on AWS. The student outlines the project's value hypothesis, emphasizing the integration of various platforms through XML messaging and code reuse. The growth hypothesis focuses on researching existing implementations and assessing various cloud service providers based on factors like price, simplicity, and security. The project plan includes a communication strategy using a Slack channel, task management with WP Project Manager, and time management using the 4D and Pomodoro methods. The diary also details iteration plans, design thinking processes, and an architectural overview of the web application, including single-page applications, microservices, and serverless components. The student employs a design thinking process to empathize, define, ideate, prototype, and test the application, providing a comprehensive overview of the project's progression, challenges, and solutions.
Assignment 1 – Project Diary part A
Student’s Name
Project goal
Cloud computing and SOA is highly gaining momentum across various companies. These
organizations are aimed at reducing the cost of operation and operational efficiency purposes. The two
technologies have left behind the status of the current emerging technologies to consolidate as proven and
mature technologies. It is evident that in this 21st-century adoption of cloud computing and SOA
architectures are taking place in all industry segments which has also incorporated small scale
organizations.
Cloud computing platform provides the abstraction layer between technical implementation details
like databases, networks, and servers and computing resources and thus enabling all computational
resources to be used on-demand. On the other hand, SOA is said to be an architectural pattern that is
used for the development of all distributed systems which transform resources into services. Some of the
benefits offered by SOA are increased cost savings and agility.
Most designers are faced with increased costs during the development of a web-based application.
The major aim of this project is to develop a plan for web-application that is based on SOA and that which
is designed for the cloud. The web-application will work just like those hosted on AWS cloud platform.
Student’s Name
Project goal
Cloud computing and SOA is highly gaining momentum across various companies. These
organizations are aimed at reducing the cost of operation and operational efficiency purposes. The two
technologies have left behind the status of the current emerging technologies to consolidate as proven and
mature technologies. It is evident that in this 21st-century adoption of cloud computing and SOA
architectures are taking place in all industry segments which has also incorporated small scale
organizations.
Cloud computing platform provides the abstraction layer between technical implementation details
like databases, networks, and servers and computing resources and thus enabling all computational
resources to be used on-demand. On the other hand, SOA is said to be an architectural pattern that is
used for the development of all distributed systems which transform resources into services. Some of the
benefits offered by SOA are increased cost savings and agility.
Most designers are faced with increased costs during the development of a web-based application.
The major aim of this project is to develop a plan for web-application that is based on SOA and that which
is designed for the cloud. The web-application will work just like those hosted on AWS cloud platform.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Project value
Value hypothesis
By implementing the two technologies, the developed web-application will be in a position to
integrate between the various platforms i.e. with the exchanging XML messages between the various
services it will be possible to integrate with the various platforms like PHP and Java. Also, the two
technologies enable code-reuse thus shortening web-application development. Also, SOA and cloud
platforms will make it easy for use the development team to maintain the web application by saving time
through the re-use of services. Lastly, SOA and cloud platform offer and ease the distribution of
functionalities
Growth hypothesis
For this project, I will start by looking into those organizations which have implemented the two
types of technologies and how they have gone about in laying down the technology. I will use some of
these organizations to publicize the two technologies. Second I will assess requirements needs for every
technology and the many decisions required. Third, I will assess, the features of the various companies
that offer these services. This assessment will be based on six factors; first is the price offered by each
platform. Second is simplicity; cloud computing facilities offered by the company needs to be very easy to
use and also to set-up all the services without requiring a third party to set-up or even worry about resource
management. Third, the company needs to have reliable access to its cloud computing resources and
reliability which backed by some kind of penalties or money back in the event of services downtime. The
other factors to consider are flexibility, collaboration, and security. In terms of security, the services offered
by the cloud company needs to allow users to add software patches on the developed application and to
Value hypothesis
By implementing the two technologies, the developed web-application will be in a position to
integrate between the various platforms i.e. with the exchanging XML messages between the various
services it will be possible to integrate with the various platforms like PHP and Java. Also, the two
technologies enable code-reuse thus shortening web-application development. Also, SOA and cloud
platforms will make it easy for use the development team to maintain the web application by saving time
through the re-use of services. Lastly, SOA and cloud platform offer and ease the distribution of
functionalities
Growth hypothesis
For this project, I will start by looking into those organizations which have implemented the two
types of technologies and how they have gone about in laying down the technology. I will use some of
these organizations to publicize the two technologies. Second I will assess requirements needs for every
technology and the many decisions required. Third, I will assess, the features of the various companies
that offer these services. This assessment will be based on six factors; first is the price offered by each
platform. Second is simplicity; cloud computing facilities offered by the company needs to be very easy to
use and also to set-up all the services without requiring a third party to set-up or even worry about resource
management. Third, the company needs to have reliable access to its cloud computing resources and
reliability which backed by some kind of penalties or money back in the event of services downtime. The
other factors to consider are flexibility, collaboration, and security. In terms of security, the services offered
by the cloud company needs to allow users to add software patches on the developed application and to
add capacities. After these considerations, I will settle on one company that offers these two technologies
where I will then make payments and start the process of designing the web application.
Metrics
I will slow kick off the project after payment to SOA and cloud platform providers. In this first few
days will get me some orientation overview of all the features offered by the cloud provider and learning the
usage of various plugins. Since one can use various plugins to develop the web application, the process
will move on quickly. I am expecting to have completed the web-application project within three weeks.
Project plan
Communication strategy
This is a one-man project but because it is my desire to see the success of this, I will make sure I
will meet SOA and cloud computing platform threshold. When I see there is a need I will involve other
experts from those organizations whose web-application are already on the two platforms on how best I
can utilize the two technologies. Also, I will create a portal of communication between myself and other
web-designers who have already implemented the two technologies. This slack channel will serve as a
communication channel instead of the normal relying of emails (Dörnyei, 2014, p. 69).
Task management strategy
I believe I will complete this project within three weeks. Since I desire to see the success of this project, I
will utilize the qualities offered by WP Project Manager Tool to manage all the project-related tasks. With
WP Project Manager Tool I will in a position to create and manage all the tasks related to this project. The
tool also allows the production of reports and has a file manager which will allow me to view all the project
where I will then make payments and start the process of designing the web application.
Metrics
I will slow kick off the project after payment to SOA and cloud platform providers. In this first few
days will get me some orientation overview of all the features offered by the cloud provider and learning the
usage of various plugins. Since one can use various plugins to develop the web application, the process
will move on quickly. I am expecting to have completed the web-application project within three weeks.
Project plan
Communication strategy
This is a one-man project but because it is my desire to see the success of this, I will make sure I
will meet SOA and cloud computing platform threshold. When I see there is a need I will involve other
experts from those organizations whose web-application are already on the two platforms on how best I
can utilize the two technologies. Also, I will create a portal of communication between myself and other
web-designers who have already implemented the two technologies. This slack channel will serve as a
communication channel instead of the normal relying of emails (Dörnyei, 2014, p. 69).
Task management strategy
I believe I will complete this project within three weeks. Since I desire to see the success of this project, I
will utilize the qualities offered by WP Project Manager Tool to manage all the project-related tasks. With
WP Project Manager Tool I will in a position to create and manage all the tasks related to this project. The
tool also allows the production of reports and has a file manager which will allow me to view all the project
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.
Trusted by 1+ million students worldwide
files at once. Also, I will make use of Pareto principle which will assists in prioritizing time that I spend on
daily tasks. With Pareto principle, I will be in a position to analyze the duration of a certain task and the
time required to accomplish the most important tasks (learning, 2014, p. 421).
Time management strategy
In terms of time management, I will utilize the 4D method and Pomodoro method. This is simple,
and an effective technique to manage time. With this method, I will be in a position to decide which tasks
needs to be dropped and those that I need to focus on at a certain time and those that require a lot of time.
Pomodoro method will help in improving that focus and to boost web development productivity (Gray, 2014,
p. 57).
daily tasks. With Pareto principle, I will be in a position to analyze the duration of a certain task and the
time required to accomplish the most important tasks (learning, 2014, p. 421).
Time management strategy
In terms of time management, I will utilize the 4D method and Pomodoro method. This is simple,
and an effective technique to manage time. With this method, I will be in a position to decide which tasks
needs to be dropped and those that I need to focus on at a certain time and those that require a lot of time.
Pomodoro method will help in improving that focus and to boost web development productivity (Gray, 2014,
p. 57).
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Iteration plans
Iteration 1 : Is it worth Designed
For:
Web-application
project
Project Goal Is this an application that organizations will use to conduct their daily activities? The assumption is that project will assist
organization cost of production will be reduced. Also, the application will be based on SOA and cloud application
technologies. The riskiest assumption is that Amazon is the option for the implementation of the two technologies. The
main priority here is an application that is featured with SOA and is on cloud platform
Hypothesis
It is more professional to develop an application on SOA and on cloud platform as it can be integrated with various platform
such as Java and PHP. It also enables code-reuse thus shortening web-application development
Metric
The first metric will be the
response from those
organizations who have
already implemented the
two technologies. The
project will slowly kick off in
the firs few days but on the
second week a lot will be
achieved.
Fail Condition Success
condition
The project fails if acceptance is below 20% and if all elements of SOA
technology are not implemented
The project will succeed if
the acceptance level is
above 30 percent and if
all cloud and SOA
features are implemented
If this happens, the project has failed! If this happens then the project is
put into use
Experiment
I will create a communication channel between those experts who have used the two technologies during the design of
their project and those organizations which have already put into use SOA and cloud computing platform
Iteration 1 : Is it worth Designed
For:
Web-application
project
Project Goal Is this an application that organizations will use to conduct their daily activities? The assumption is that project will assist
organization cost of production will be reduced. Also, the application will be based on SOA and cloud application
technologies. The riskiest assumption is that Amazon is the option for the implementation of the two technologies. The
main priority here is an application that is featured with SOA and is on cloud platform
Hypothesis
It is more professional to develop an application on SOA and on cloud platform as it can be integrated with various platform
such as Java and PHP. It also enables code-reuse thus shortening web-application development
Metric
The first metric will be the
response from those
organizations who have
already implemented the
two technologies. The
project will slowly kick off in
the firs few days but on the
second week a lot will be
achieved.
Fail Condition Success
condition
The project fails if acceptance is below 20% and if all elements of SOA
technology are not implemented
The project will succeed if
the acceptance level is
above 30 percent and if
all cloud and SOA
features are implemented
If this happens, the project has failed! If this happens then the project is
put into use
Experiment
I will create a communication channel between those experts who have used the two technologies during the design of
their project and those organizations which have already put into use SOA and cloud computing platform
Timebox Start End Retro
12-Apr-20 7-May-20
8/5/2020
The specific date and time
when you will have your retro
Result I presented the wen-application prototype to those organization which have already implemented SOA and Cloud
technologies and received an overwhelming consent and the fact that this application is worthwhile. It is worth noting that
all the organizations were from Australia and have utilized AWS technologies.
Next Step
Create screens to present to a limited number of experts to get a simple prototype out and running.
Iteration 2 : Create Mock up screens Designe
d For: Web-based application
12-Apr-20 7-May-20
8/5/2020
The specific date and time
when you will have your retro
Result I presented the wen-application prototype to those organization which have already implemented SOA and Cloud
technologies and received an overwhelming consent and the fact that this application is worthwhile. It is worth noting that
all the organizations were from Australia and have utilized AWS technologies.
Next Step
Create screens to present to a limited number of experts to get a simple prototype out and running.
Iteration 2 : Create Mock up screens Designe
d For: Web-based application
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.
Trusted by 1+ million students worldwide
Learning Goal
What SOA and Cloud computing features will people need in the prototype? The assumption here is that a model similar to
amazon can be acceptable, but it will also require careful development of the prototype. For now, it is important to find out all
the features offered by Amazon E2 console. I am taking a risk here in not including web-design experts in the design, and
using myself as the first user, but given the experience, I believe i can provide a good enough starting point to build the
application prototype.
Hypothesis A web-application application similar to that designed by Fox.
Metric A score 0.1 to 1 (1 very bad, 1.0 excellent) is
going to be part of a survey.
Fail Condition Success
The experiment fails if acceptance is below 0.3 Above 0.3
Experiment
The screens with an explanation of the flow will be presented to organizations which have implemented the two types of
technologies, and they will be given time to score the functionality from 0.1 to 1.0 (0.1 bad, 1.0 good), and given time to
discuss what they would like to see implemented during project design.
Timebox
Start End
15-Apr-20 21-Apr-20
Result The prototypes was presented to Five web-design experts and one organization and their feedback highlighted in point form
on what needs to be added.
Next Step Develop a skeleton web-project
What SOA and Cloud computing features will people need in the prototype? The assumption here is that a model similar to
amazon can be acceptable, but it will also require careful development of the prototype. For now, it is important to find out all
the features offered by Amazon E2 console. I am taking a risk here in not including web-design experts in the design, and
using myself as the first user, but given the experience, I believe i can provide a good enough starting point to build the
application prototype.
Hypothesis A web-application application similar to that designed by Fox.
Metric A score 0.1 to 1 (1 very bad, 1.0 excellent) is
going to be part of a survey.
Fail Condition Success
The experiment fails if acceptance is below 0.3 Above 0.3
Experiment
The screens with an explanation of the flow will be presented to organizations which have implemented the two types of
technologies, and they will be given time to score the functionality from 0.1 to 1.0 (0.1 bad, 1.0 good), and given time to
discuss what they would like to see implemented during project design.
Timebox
Start End
15-Apr-20 21-Apr-20
Result The prototypes was presented to Five web-design experts and one organization and their feedback highlighted in point form
on what needs to be added.
Next Step Develop a skeleton web-project
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Iteration 3 : Create Skeleton web-application Designe
d For:
Web
application
Learning Goal Use word press framework to create the interface part of the web-application and PHP framework to develop some functionalities of the
application. My priority here is capture the major project requirements
Hypothesis Amazon E2 can be used as it contains both the PHP and wordpress framework
Metric Usability performance of the web
application, and the utilization of SOA
and cloud platform
Fail Condition Success
condition
The experiment fails if acceptance is below 0.3
the sketon
falls above
0.3
Experiment Implement the web-based application and verify the basic SOA and cloud based technologies.
Timebox Start End
4/23/202 4/30/202
Result The web-based application as expected, results to be working find for the intended purpose, with the implementation of both SOA and
cloud platform basic functional tests indicate good results and is, at this tage, suitable to create the prototype.
Next Step Full design of the web application
d For:
Web
application
Learning Goal Use word press framework to create the interface part of the web-application and PHP framework to develop some functionalities of the
application. My priority here is capture the major project requirements
Hypothesis Amazon E2 can be used as it contains both the PHP and wordpress framework
Metric Usability performance of the web
application, and the utilization of SOA
and cloud platform
Fail Condition Success
condition
The experiment fails if acceptance is below 0.3
the sketon
falls above
0.3
Experiment Implement the web-based application and verify the basic SOA and cloud based technologies.
Timebox Start End
4/23/202 4/30/202
Result The web-based application as expected, results to be working find for the intended purpose, with the implementation of both SOA and
cloud platform basic functional tests indicate good results and is, at this tage, suitable to create the prototype.
Next Step Full design of the web application
Design thinking process
Even though this is a one-man project, I will adopted design thinking process such as that which
was adopted by interaction design Foundation. This is a five phased approach where am required to
emphathize, define, ideate, prototype, and test the web-application. The ultimate goal is derive a deep
understanding of the product and its users (Li, 2017, p. 110).
In the first phase I will gain an empathetic understanding of the issues with the project. This will
allow me to set aside my own project assumptions about the project. Second, I will generate ideas
gathered in the first phase and synthesize on observations I gathered on those organization which have
already implemented SOA and cloud technologies. The third phase is to generate ideas gathered from
phase two. The fourth phase is to create a prototype for each of the ideas identified in phase tree. The last
phase is to test the prototype to test ideas gathered. This prototype is to be presented to web design
Even though this is a one-man project, I will adopted design thinking process such as that which
was adopted by interaction design Foundation. This is a five phased approach where am required to
emphathize, define, ideate, prototype, and test the web-application. The ultimate goal is derive a deep
understanding of the product and its users (Li, 2017, p. 110).
In the first phase I will gain an empathetic understanding of the issues with the project. This will
allow me to set aside my own project assumptions about the project. Second, I will generate ideas
gathered in the first phase and synthesize on observations I gathered on those organization which have
already implemented SOA and cloud technologies. The third phase is to generate ideas gathered from
phase two. The fourth phase is to create a prototype for each of the ideas identified in phase tree. The last
phase is to test the prototype to test ideas gathered. This prototype is to be presented to web design
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.
Trusted by 1+ million students worldwide
experts and to those organizations which have implemented SOA and cloud technologies (Anderson &
Kerr, 2013, p. 89)
Architecture
Overview of Web-application architecture
This is the framework ties up the interaction and relation together in a web application. The flow of
processes in a web-application architecture includes user browsing for the exact URL, browser then
triggers the search, the network then sends data to the computer browser from servers, and the browser
continue to display the web page as requested. The web-application architecture consists of single page.
Micro services, and server-less components. The single page applications offers greater interactive user
experience thus permitting the single-page to have a more dynamic interaction (Calvo, 2013, p. 109).
The micro-service component permits developers to have one and specific functionality via micro-
services architecture framework. The server-less component permits the web-application to execute
without correlation to infrastructure related tasks (Bansod, 2011, p. 67).
Overview of Service-oriented architecture
SOA (Service-oriented architecture) is a computer software design in which applications
components provides services to other components through communications protocol, typically over a
network. The major principle of SOA is the independent of any product, technology or vendor. SOA
architecture makes it easier for web application components over different networks to work with each
other (Liu, 2010, p. 309). Those web services which are built as per SOA architecture tend to make web-
application more independent. The web-application itself can exchange information or data within itself
and with other web-applications. SOA architecture is based on four design principles which are
standardized service contract where all services are supposed to adhere to service description. Each and
Kerr, 2013, p. 89)
Architecture
Overview of Web-application architecture
This is the framework ties up the interaction and relation together in a web application. The flow of
processes in a web-application architecture includes user browsing for the exact URL, browser then
triggers the search, the network then sends data to the computer browser from servers, and the browser
continue to display the web page as requested. The web-application architecture consists of single page.
Micro services, and server-less components. The single page applications offers greater interactive user
experience thus permitting the single-page to have a more dynamic interaction (Calvo, 2013, p. 109).
The micro-service component permits developers to have one and specific functionality via micro-
services architecture framework. The server-less component permits the web-application to execute
without correlation to infrastructure related tasks (Bansod, 2011, p. 67).
Overview of Service-oriented architecture
SOA (Service-oriented architecture) is a computer software design in which applications
components provides services to other components through communications protocol, typically over a
network. The major principle of SOA is the independent of any product, technology or vendor. SOA
architecture makes it easier for web application components over different networks to work with each
other (Liu, 2010, p. 309). Those web services which are built as per SOA architecture tend to make web-
application more independent. The web-application itself can exchange information or data within itself
and with other web-applications. SOA architecture is based on four design principles which are
standardized service contract where all services are supposed to adhere to service description. Each and
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
every service ought to have some sort of description that describes what SOA services are about. This
makes it easier for client applications to understand what the web application service does. Loose coupling
is another principle which is less dependency on each other. This is the major feature of web-application
service that states that there ought to be less dependency as possible between web-application services
and client invoking web-application web-service. Then there was service abstraction where services tends
to hide the web application logic. The web application encapsulate from the outside world. Here SOA
makes the web-application not to expose how its functionality. Lastly is service re-usability which is divided
with the intention of maximizing re-usability and building the same code again and again across the web-
application (Lin, 2018, p. 186). Other principles are service autonomy, service composability, service
interoperability, service discoverability and service stateless. With SOA, web application services should
not withhold data or information from state to another. On service interoperability, services ought ot use
standards which allow diverse subscribers to use the web-application service and a web-application
service which uses HTTP and XML standards to ensure it conforms with service interoperability (Tsai,
2010, p. 657).
makes it easier for client applications to understand what the web application service does. Loose coupling
is another principle which is less dependency on each other. This is the major feature of web-application
service that states that there ought to be less dependency as possible between web-application services
and client invoking web-application web-service. Then there was service abstraction where services tends
to hide the web application logic. The web application encapsulate from the outside world. Here SOA
makes the web-application not to expose how its functionality. Lastly is service re-usability which is divided
with the intention of maximizing re-usability and building the same code again and again across the web-
application (Lin, 2018, p. 186). Other principles are service autonomy, service composability, service
interoperability, service discoverability and service stateless. With SOA, web application services should
not withhold data or information from state to another. On service interoperability, services ought ot use
standards which allow diverse subscribers to use the web-application service and a web-application
service which uses HTTP and XML standards to ensure it conforms with service interoperability (Tsai,
2010, p. 657).
Cloud architecture
Cloud computing refers to those components required for cloud computing. These components
consists of network platform, back-end platforms, cloud delivery platform, and front-end platform. The cloud
delivery is composed of software as a service commonly known as SaaS model which involves the service
provide maintaining and installing software in the cloud and users running the software from cloud over the
internet (Kung, 2013, p. 39). It also consists of development as a service commonly known as DaaS, Data
as a Service, and Platform as a service. The cloud networking platform offers low latency and high
bandwidth thus allowing users to have uninterrupted access to the applications and data, agile network that
allows on-demand access to cloud computing resources; it requires ability to move efficiently and quickly
between servers (Tianfield, 2011, p. 1398).
Cloud computing refers to those components required for cloud computing. These components
consists of network platform, back-end platforms, cloud delivery platform, and front-end platform. The cloud
delivery is composed of software as a service commonly known as SaaS model which involves the service
provide maintaining and installing software in the cloud and users running the software from cloud over the
internet (Kung, 2013, p. 39). It also consists of development as a service commonly known as DaaS, Data
as a Service, and Platform as a service. The cloud networking platform offers low latency and high
bandwidth thus allowing users to have uninterrupted access to the applications and data, agile network that
allows on-demand access to cloud computing resources; it requires ability to move efficiently and quickly
between servers (Tianfield, 2011, p. 1398).
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.
Trusted by 1+ million students worldwide
1 out of 17
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
![[object Object]](/_next/static/media/star-bottom.7253800d.svg)
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.