Q1: What the benefits of and the challenges with cloud computing are?

Answer:
Benefits
Scalability
Still, cloud service providers can upmarket to suit your requirements, if a company needs to
expand. This lessens the need for new outfit.
Effectiveness
Multiple druggies can work together and communicate over the cloud. This makes operations
more smooth- sailing.
Dexterity
Given all the advantages of cloud computing, app
development, testing, and deployment are
accelerated.
Cost Savings
You gain access to important tools without the cost of
copping tackle, software, or licenses. Everything is on
the cloud.
Availability
You can pierce anything you stored in the cloud through all your web- enabled bias.
Mobility
Workers who are working on the demesne or at the remote locales can fluently pierce all the
could services. All they need is an Internet connectivity.
Trust ability
Given an array of available waiters, services can be fluently moved to other waiters in case of a
failure.
Security
Given that they feed to a huge number of guests, cloud service providers misbehave to high-
position security protocols. These security measures bring a fortune to apply — another area
where your business could cut down some costs.
Unlimited storehouse capacity
The cloud offers nearly measureless storehouse capacity. At any time, you can snappily expand
your storehouse capacity with veritably nominal yearly freights.
Challenges
Security
While there are high norms when it comes to security, cloud computing services are still
vulnerable to security pitfalls. Given that you ’re using these services to handle important
business data, you cannot go similar threat. This matter won’t ever really go down, providers
should just ensure that the pitfalls are under control.
Internet Connectivity
Good Internet connectivity is a must-have in cloud computing. You can’t pierce cloud without
an internet connection. also, you don’t have any other way to gather data from the cloud.
Seller Cinch- in
Presently, migration from one provider to another is rough. There are interoperability, comity,
and support issues girding migration. This might end up with your business getting stuck with
your provider when you need to make a switch.
Nebulousness
Cloud providers don't incontinently inform guests about a security breach. This is commodity
not every enterprise can tolerate.
Time-out
Handling a lot of guests may overwhelm cloud service providers. There are also power outages
and connectivity interruptions. All these number the suspense of your processes.
Lower Bandwidth
Numerous cloud storehouse service providers limit bandwidth operation of their druggies. So,
in case if your association surpasses the given allowance, the fresh charges could be
significantly expensive.
Crunches of Support
Cloud Computing companies fail to give proper support to the guests. also, they want their
stoner to depend on FAQs or online help, which can be a tedious job technical person.
Technical Issues
Cloud technology is always prone to an outage and other specialized issues. Indeed, the stylish
cloud service provider companies may face this type of trouble despite maintaining high norms
of conservation.
Q2: What are the characteristics of an elegant architecture?
Answer:
Empirical
It should be possible to corroborate that the armature will perform as designed and that there
would not be lateral goods that affect from the armature and the corridor of the enterprise that
it impacts. The ultimate test of this is whether it delivers the business value that was promised
in the Vision Statement. Enterprise Architect can be used to model the measures that are
defined to corroborate that the Business objects (and thus the pretensions) have been attained.
Traceable
An armature is a description of an enterprise at a particular position of detail and doesn't live in
insulation but is generally related to business motorists and pretensions and other
infrastructures at the same position or advanced or lower and to perpetration programs and
systems.
Enterprise Architect allows rudiments to be
traced in any direction and provides a number
of important tools to fantasize the traces
including the Relationship Matrix, the
Traceability Window and plates.
The Insert Affiliated rudiments installation can
be used to automatically construct a illustration
of traces nearly magically creating suggestive
and no way ahead seen views of the depository.
Flexible
The infrastructures must be flexible and be suitable to acclimatize to changing conditions and
also give enough guidance for perpetration brigades that have the knowledge of their discipline
to make the important and necessary opinions about specialized problems and openings.
Infrastructures that are created with too important detail will frequently affect in brittle and
inflexible designs and executions performing in systems that cannot acclimatize to changing
circumstances and surroundings.
Enterprise Architect has a wide range of features that can help with change including the
Change element a important birth installation and the Kanban plates that allow Conditions
Features, stoner Stories and further to be imaged and prioritized.
Elegant
Infrastructures must have both form and function and it's a good test of an armature to
measure its fineness.
An armature that's well designed will tend to be elegant and have a simplicity of form that will
be egregious to those that take the time study it. Mastermind has important features that allow
the fineness of an armature to be imaged including the capability to produce professional
publications that can be generated automatically from the tool using a series of erected- in or
stoner defined templates.
Utilitarian
Architecture must have mileage which, in turn, when enforced will affect in practical issues.
infrastructures that are elegant but don't give provable and measurable value to the
stakeholders or the parties that requested them will eventually not be successful.
Enterprise Architect has tools that allow an armature to be imaged and understood by a
different group of stakeholders, allowing any problems with mileage to be discovered
beforehand in the armature process.
Be creative
Architecture is each about creativity. It requires people to be extraordinarily creative and
productive. Since ultramodern engineers are needed to design state- of- the- art structures that
will take the boundaries of aesthetics to a whole new position, it goes without saying that you
will have to be both imaginative and creative.
Being creative is principally allowing outside of the box and bringing enterprising inventions and
new ideas that will basically change the most common generalities. It's your most essential
charge statement, and it separates you from the rest. Constant invention will insure that you
come well- entered and memorable.
Robust
An armature should be strong and not be vulnerable to minor changes in the business,
information, operation and technology systems.
Enterprise Architect can help in icing that the infrastructures are well integrated and related to
each other and provides a number of tools similar as the Traceability window, the Relationship
Matrix and the Insert Related rudiments feature that can be used for this purpose
Doable
An armature that cannot be enforced will mean that the pretensions and objects of the
enterprise won't be met. It's stylish to identify these conditions as snappily as possible so as not
to fail the party who requested the armature work.
Mastermind can help by allowing engineers, contrivers and inventors to bandy the armature
and determine its feasibility using the Collaborate window and by mapping the Enterprise
Architecture to Capability or Solution infrastructures.
Relationship Matrix
An armature is a living reality that describes a target state and- formerly enforced- will come
the new birth state.
The infrastructures should prove to be durable with the passage of time and be flexible to
changes in the business and specialized surroundings that might do over the continuance of the
infrastructures. This implies that they must as much as possible- expropriate the future
conditions and surroundings.
Q3: How to identify Product Owners for all discrete information management projects?
Answer:
A Product owner is an individual responsible for maximizing the product’s value created by the
development platoon. They transfigure the high- position product vision developed by the
Product directors into detailed stoner stories or conditions. The most important tasks of a
Product owner include

• Formulating design pretensions and effectively plan work conditioning

• Developing and managing the product backlog
• Overseeing the product development at colorful stages
• Amusement as liaison between the customer and the product development platoon
• Balancing the compass, time, and budget constraints
• insure translucency into the forthcoming work of the product development platoon
• Communicating with stakeholders
You ’ll be most likely to find Product possessors at companies that apply the nimble approach
to develop digital products.
Primary Purpose
Product owner is responsible for helping the development platoon by creating detailed stoner
stories (or get them created by the development platoon) and working nearly with them to
execute the pretensions that the product director helps to define. A Product owner also serves
as an internal client expert by answering the questions of the development platoon.
Connection to the Product
Product Owner is considered a lifeline of the product and is directly involved with its
development. It's because they dissect the product from a client’s perspective. They share in
colorful meetings similar as diurnal Scrum, to get the feedback on the status of the product. In
case they find any problems with the product, they suggest implicit results and prioritize them
grounded on their significance.
Collaboration
Product owner works veritably nearly with the development platoon. He makes sure that the
Development Team understands particulars in the Product Backlog to the position demanded.
piecemeal from the dev platoon, the Product owner also frequently communicates with the QA
staff, UI, UX, contrivers, and the operations platoon to define the detailed conditions and
ensure that the product’s specialized perpetration will be flexible for unborn changes.
Involvement with Product Roadmap
The Product owner generally doesn't produce another product roadmap that's separate from
the one set by the Product director. still, they nearly work with the Product owner when
needed to review the product roadmap and make sure the precedence’s are aligned duly.
There Qualities to Identify Great Product owner
1. Secerning what's demanded from what's wanted
A significant part of the product owner part is relating what's demanded to break druggies’
problems, fulfill their requirements, enable them to be better at their job, or maximize their fun
or relaxation. The part is about understanding the problem and creating a vision of how that
problem could be answered — not the specialized result, but the true need.
The reason this skill is so tough is that druggies infrequently know what they need. generally, a
stoner’s vision is constrained by what they presently do. As a result, numerous products come
reworks of a paper system or an old frame.
A poor product owner gives a client what they want or what they asked for, but a good product
owner listens and watches so they can blend wants and needs in order to break the client’s
problem and give them what they truly need.
This point leads us to an intriguing quotation by Henry Ford “ If I had asked people what they
wanted, they would have said briskly nags. ”
2. Understanding what's needed to produce a successful operation
Generally speaking, business product possessors frequently warrant this knowledge and
experience, and they will inaptly perceive a desire for a completely working product rather than
appreciate the value of early feedback. numerous try to include every imaginable point rather
than working toward a minimal point set to get feedback and decide value beforehand.
What would you rather have an educated product owner with zero business knowledge, or an
expert in the business with zero software delivery experience? Before you answer, consider this
Business knowledge can be picked from effective discussion, observation, and feedback. still,
the understanding of a good nimble software development lifecycle is far harder to learn, and
there's no cover for experience. Generally, the stylish products affect from trials, reviews, and
feedback, along with a amenability to be flexible in responses. The product owner sets
precedence’s and interprets the vision, so they've further influence on the product creation
than anyone.
3. Communicating effectively with both specialized and business stakeholders
A great product owner learns to say no hypercritically and in a way that conveys understanding
of what’s being asked. With that, a great product owner shouldn't be seen as a handicap or a
chain, but a slavey of good opinions. The word “no” should be delivered in a way that leaves
the client feeling confident that this decision is right, indeed if it isn't what was originally
wanted, and that the product owner will deliver the stylish product within the parameters.
Again, if the product owner chooses to say yes, they should be suitable to convey the
counteraccusations of that. Product possessors should have a number of tools that can help
people understand their opinions.
The product owner must also communicate with the development platoon, and they must
understand specialized development terms so that they can have a full grasp of the specialized
perpetration, indeed if they don't have authority over how effects get done. In other words,
they should have a vested interest in understanding the process.
Product possessors also need the creativity to communicate design ideas, or, if the ideas come
from others, the compass to understand that creativity and express it to the business and
specialized brigades. The same can be said about major stakeholders (banning druggies). This
group generally funds the product, and they want to see progress and good stewardship of
their investment, so they may ask for vaticinations and indeed press for commitments.

The End.
 Questions about topics ask to other students
Cloud Computing:
Explain System integrators in cloud computing?
What is the difference between cloud and traditional datacenters?
Why API's is used in cloud services?
Elegant architecture:
Things that effect the elegant architecture?
If architecture is not elegant than what problems we can face in that scenario?
Identify Product Owners:
How would you characterize your role as Product Owner?
Difference between Product Owner and Product Manager?
How would Product Owner collaborate with the other Scrum Team members?