Overview: Service-Oriented Architecture (SOA) and Cloud Computing projects are no different from other IT projects in that larger projects tend to fail and issues regarding people and change can scuttle projects. Oftentimes, such change issues are not identified early enough in the project. This session introduces Incremental SOA Analysis. It aims to improve the project selection process in a way that also improves the chance of success for the selected project. This analysis takes into account both project size and human change issues.
Incremental SOA Analysis uses three tools that address change issues:
Force Field Analysis provides a perspective on the various forces involved in an organization when trying to make a change. In Force Field Analysis, change is seen as a goal or vision. There are driving and restraining forces that affect the likelihood of achieving this goal or vision. Driving forces help achieve the goal or vision. Restraining forces hinder achieving the goal or vision. The visual nature of Force Field Analysis gets people involved in finding solutions to change issues. Force Field Analysis is simple to learn and can be used in a group setting.
The Worksheet for Resistance Issues and Suggestions allows a group to engage in problem solving. The purpose is to find ways to weaken the restraining forces for a given Force Field Analysis in order to allow the driving forces to shift the status quo - thus making it easier for change to occur.
The Decomposition Matrix deals with a common problem that occurs when attempting to change an existing system. With an existing system, it is often difficult to think about that system in a new way. Many of us tend to replicate what we have done before. Instead of starting out with a diagram (and drawing something we likely have seen before), the Decomposition Matrix provides us with a way to think differently about the system we are about to design. This free tool can be used in a group setting much like the other two tools.
These tools are used in Incremental SOA Analysis to engage people in such a way that they can come to their own resolution on the concepts that are causing human change issues. There are five principles explained in this session that provide the basis for Incremental SOA Analysis:
Make projects as small as possible.
Involve stakeholders appropriately and as much as possible.
Make decisions as late as possible.
Weaken the restraining forces within the project as much as possible.
Realize that your Service-Oriented/Cloud Computing Architecture will never be done.
For most organizations, a Service-Oriented/Cloud Computing Architecture will be ever changing because it will need to respond to the changing nature of business and technology. The primary goal of Incremental SOA Analysis is to eventually position your organization so that it can respond quickly to those changes. It will provide you with a loosely coupled architecture that should improve your organization’s ability to change. A secondary goal is to leave you with functioning architecture whenever you stop. Budgets and other demands often derail the best-laid development plans. With this type of analysis, you should be able to restart your development at some later time if work is suspended for some reason. Even though this session addresses a technical topic, it is presented in such a way that this session is also suitable for nontechnical members of your team.
Why should you attend: You may have noticed statements of problems with service-oriented architecture (SOA) projects. For example, one published statement was that 50% of SOA projects are a complete failure. Another statement characterized what is described as rage over the changes being instituted as part of the SOA projects. This is pretty dismal stuff. Is it reality? We need to put these statements in perspective. This session describes how SOA and Cloud Computing projects are really no different than other IT projects in that larger projects tend to fail and that many change issues are not identified early in the project can scuttle those projects.
This session focuses on the people involved in the change, including leadership, users, and those working on the project. People are understandably concerned about the future of their jobs and about learning new tools and technologies. An organization must deal with managing the human aspect of the change that occurs with the adoption of a Service-Oriented Architecture with Cloud Computing. Nevertheless, there is always the chance that a given SOA/Cloud Computing project could fail. To understand one way to minimize this chance, Incremental SOA Analysis is introduced. The purpose of this analysis is to improve the project selection process in a way that it also improves the chance of success for that project. This analysis takes into account both project size and human change issues. Even though this session addresses a technical topic, it is presented in such a way that this session is also suitable for nontechnical members of your team.
Areas Covered in the Session:
Change Issues Related to Service-Oriented Architecture (SOA) and Cloud Computing
Three Tools to Address Change Issues
Force Field Analysis
Worksheet for Resistance Issues and Suggestions
Incremental SOA Analysis: Facing Reality, Coping with Change, and Improving Your Chance of Success
Five Principles for Incremental SOA Analysis
Incremental SOA Analysis Explained
Business Process Analysis
Candidate Process Analysis
An Example Incremental SOA Analysis Using the Three Tools
Who Will Benefit:
Application Development Managers
Project Team Leaders
Application/Software Developers and Engineers
Business Analysts ·
Overview: This course will cover basic green data center design in light of new findings from Hurricane Sandy and the expectation of increased severe weather as a result of climate change in the coming years. The electrical grid in particular is extremely susceptible to major climate disruptions and many states as well as data center operators are deploying micro grids in response. This is resulting in the design of new "distributed" data centers, as opposed to the traditional mega facility.
As well the course will discuss the impact of California’s new cap and trade program and the proposed carbon tax systems to be implemented in several states. Business case analysis will be provided on the aspects and cost savings of various green data center architectures.
Why should you attend: Data centers and corporate clouds can represent up to 50% of the electrical energy costs for an organization. As CFOs start to realize that the IT department is responsible for the one of the largest cost centers in many organizations there is increased pressure for CIOs to find ways to reduce the energy consumption of their data center and/or clouds. In addition several states such as California, Oregon, Washington etc are planning to introduce cap and trade or carbon taxes which will further significantly increase the cost of operating data centers and clouds in those states. As well new SEC rules require that corporations disclose their liability in terms of exposure to climate change and the increased likelihood of storms and droughts. Hurricane Sandy was a wakeup call to the data center industry. Several data centers were knocked up in the New York area, which in turn caused major economic damage to the companies whose servers were hosted in their data centers.
Areas Covered In the Session:
Lessons learned from Hurricane Sandy about data center design and location
Impact of climate change on future data center design and architecture
How green data centers can be deployed significantly cheaper than today’s mega facilities
How PUE, WUE and CUE are largely irrelevant in data center design
Micro grid power design for data centers
Examples of Green data centers powered by bio-fuels, solar & wind power etc
Business case studies of Green data centers
Who will benefit:
Data Center Facilities Managers
Data Center Architects
Cloud Architects ·
Overview: Many organizations today are feeling pressure to reduce IT costs and optimize IT operations. Cloud computing is rapidly emerging as a viable means to create dynamic, rapidly provisioned resources for operating platforms, applications, development environments, storage and backup capabilities, and many more IT functions.
A staggering number of security considerations exist that information security professionals need to consider when evaluating the risks of cloud computing. Serious discussion of cloud security starts with a detailed introduction to the various delivery models of cloud computing ranging from Software as a Service (SaaS) to Infrastructure as a Service (IaaS) and everything in between.
Each of these delivery models represents an entirely separate set of security conditions to consider, especially when coupled with various cloud types including: public, private, and hybrid. Managers, auditors, and systems and network administrators will benefit from a discussion into the technologies available for securing cloud-based assets while covering all the policies, processes, and compliance considerations that go along with this major technology shift.
Why Should You Attend: The cloud is everywhere! Well, that's what the marketing folks would have us believe, anyway. For security professionals, migrating systems, applications, and data to the cloud presents a new set of challenges to tackle. What kind of policies do we need, and how can we work with legal teams to incorporate language into contracts? How can we protect sensitive data with encryption, intrusion detection and prevention, and host and network access controls? Can we extend identity and access management tools and processes into the cloud? Senior Fellow and Chief Strategist, Melvin Greer provides clarity around cloud security and details the issues associated with data privacy.
Areas Covered in the Session:
Cloud Computing Overview
Cloud security issues and opportunities
Security vs. Privacy
Risk Mitigation Strategies
Data Privacy: A Legal Framework
Strategic Recommendations: What Should I do Now?
Who Will Benefit:
Chief Security Officers
Web Content Developers
Cloud Computing Staff
Social Media Staff
Auditors, and Systems and Network administrators ·
Cloud Computing verändert die IT-Landschaft. Denn in Zukunft beziehen Unternehmen verstärkt Rechenkapazität, Speicherplatz und Software über das Internet. Dieses Video zeigt, wie relevant die Cloud mittlerweile ist. ·
Web Privacy, Compliance, Cloud Computing und mehr.Die Uniscon GmbH wurde 2009 mit dem Ziel gegründet, technische Lösungen zu entwickeln, die es Usern erlaubt, sich im Internet sicher und frei zu bewegen. ·
Die PIRONET NDH AG agiert als Unternehmensgruppe im IT-Markt in drei Geschäftssegmenten: ITK Outsourcing, Content Management sowie Beratung und Kreation. PIRONET NDH gehört zu den marktführenden deutschen Anbietern von Cloud Computing. Im Fokus steht die Bereitstellung von Unternehmenssoftware über das Internet bis hin zu kompletten Desktop-Arbeitsplätzen und geschäftskritischen Applikationen von SAP und Microsoft. ·
Bundesministerium für Wirtschaft und Technologie. Das Technologieprogramm Trusted Cloud unterstützt die Entwicklung innovativer, sicherer und rechtskonformer Cloud-Lösungen, die sich insbesondere für den Einsatz im Mittelstand eignen. Alle Informationen über das Programm, seine Inhalte und seine Ziele auf einen Blick. ·