Platinum Sponsor

Bronze Sponsor

Best Practices Track

Session Descriptions

Putting the A in SOA
Charles Stack, CEO, Flashline Inc.
May 16, 10:30 a.m.
There is nothing hollow about the promise of unprecedented agility, flexibility, and software reuse through SOA. However, too many SOA initiatives fail because organizations try to make the leap to SOA without strong management of the underlying architecture. SOA is worth the effort, but it won't rescue an enterprise architecture in disarray. We'll explore patterns and best practices that focus on SOA as an integral part of a well-managed enterprise architecture, and we'll examine service and architectural design, deployment, governance, and management as well as discover tips for getting started and keeping things on the enterprise architecture track and measuring the results.

Database Connectivity in the Midst of Infrastructure Diversity
John Goodson, Vice President of Product Operations, DataDirect Technologies
May 16, 11:45 a.m.
You no doubt have a variety of technologies deployed in your enterprise to support your application solutions. Legacy systems, Microsoft- and Java-based technologies, and EAI or home-grown middleware all play a role in your IT infrastructure, and you’ve started deploying some applications based on the latest technologies including SOA, Web services, Microsoft’s .NET framework, and various open source technologies. You also have a myriad of databases that span a variety of technologies including Oracle, SQL Server, DB2, and MySQL. You want to rationalize these technologies to reduce your development and deployment cost, improve risk/reward posture, and position your organization to better leverage new revenue opportunities.
See how to take a best practices approach to data connectivity in a heterogeneous environment.  John will draw from his 20 years of experience working with databases and defining data connectivity standards—ODBC, JDBC, ADO.NET, and XQuery—to present how to devise a methodology for data connectivity as well as address both the business implications and technical considerations relating to this approach through data integration landscape, database connectivity, and design. 

The Rocky Road to Compliance
Shari Zedeck, Director of Product Management, Progress Software
May 16, 3:30 p.m.
Governments around the world are imposing new regulations on the way businesses report and protect information. In the United States alone, regulations like Title 21 CFR. Part 11, HIPAA and Sarbanes-Oxley have put new stresses on the processes that are part of every business. These regulations are having a huge impact on the way our IT systems are architected, developed, deployed, managed and monitored. We'll explore the new regulations including a specific focus on new requirements they impose on our IT systems and how they change the way IT systems are designed and deployed. You'll hear about reporting and archival requirements during application development and deployment, change auditing requirements, disaster recovery plans, and application integration requirements.

 Building an Agile Enterprise
Chris Hagenbuch, Program Manager, Apptis
May 16, 4:45 p.m.
Many approaches to enterprise architecture run in conflict with agile development methods. In some cases architects sit in ivory towers and dictate to the development teams, and some run the command-and-control activities of development teams. In an agile world, teams need to embrace architecture best practices and adhere to standards, but in many cases architecture is being developed in parallel with business applications and code. How in this paradigm can enterprise architects work with the business-focused teams to align with both the architecture governance and the business priorities? Using Scrum as an example of an agile development framework, we can show how the integration of enterprise architecture principles and guidance development teams can focus on providing business value. In many cases the architecture evolves and is developed alongside the applications providing a bidirectional conduit for communication between architecture organizations and development teams.

Model Driven Software Engineering
Gunther Lenz, Program Manager, Siemens Corporate Research
May 17, 10:30 a.m.
Many buzzwords related to Model-Driven Software Development (MDSD) circulate in today's software engineering world. While some tool vendors promise an entirely model-based approach to software development, others propagate a more elaborative approach and another group doesn't believe in model-driven development because of mostly bad experiences with CASE tools. Nevertheless, through the introduction of model-driven architecture (MDA) and software factories we can see the emergence of two new paradigms that are based on the idea of raising the level of abstraction to enable the industrialization of software development. This presentation will shed light on the state of model-driven development and a prediction on its future. You'll reach a thorough understanding of the problems, the promise, and the hype around MDSD to help you make better decisions about what works and what doesn't when you employ the current generation of domain-specific frameworks and transformation tools.

Managing Dependencies Across the Architecture
Neeraj Sangal, Founder and CEO, Lattix Inc.
May 17, 2:00 p.m.
An enterprise architecture's ability to respond to change degrades during its useful life. Degradation occurs because the original architecture may not be ideal and changes over time stretch that architecture. The result can be called "accidental architecture," where the architectural model evolves based on a series of tactical decisions rather than because of a strategic plan. One proven way of reducing the impact of software changes over time is to keep track of the architecture by examining the dependencies among the various parts of the architecture. We can use rules to specify the allowed and disallowed dependencies to prevent architecture from degrading accidentally, which makes architectural evolution explicit and helps manage the complexity so that the impact of new enhancements remains well understood. This presentation describes architectural dependencies and how they can influence the long-term reliability and extensibility of an enterprise architecture. We'll focus on tracking dependencies among parts of the architecture using the Design Structure Matrix (DSM). Participants will learn about the value of managing dependencies among architectural components and how dependency tracking can keep an architecture relevant and flexible over time.

Minimize Business-Disruption Risk and Cost Through Architectural Modeling
Guy Hoffman, President and CEO, Metallect
May 17, 3:15 p.m.
Enterprises have encoded their critical business processes and intellectual property into their custom applications. These applications are the business. Over the years companies have developed dozens, even hundreds, of these business-critical applications, and many are highly interdependent, where functionality or data in one application relies on the functionality or data in another application or database. Others are siloed with duplicate functionality and information contained in multiple applications. This growing web of application interdependencies constitutes increasingly complex software sprawl, spawning a new set of risks to the enterprise. Continuous business changes drive the need to continuously modify, enhance, and extend these business-critical applications.
  
Traditional approaches to working with this complexity are no longer effective. Existing solutions for architectural modeling, dependency-mapping, impact analysis, and change capture were developed for single-technology environments and green field development. They do not scale to meet the challenges of multiapplication, multitechnology, multidivisional, multilocation, application, database, and middleware enterprise environments that span new and existing resources. This multidimensional problem can be addressed only through advanced architectural modeling that is capable of generating and maintaining a current-state, metamodel based on emerging standards. These standards—semantics, RDF, and USDL—provide visibility, dependency-mapping, impact analysis, and capture as-built changes within and between applications and across technologies. It is only though this type of fully automated, architectural modeling of the logic that comprises the business-critical applications on which the business runs that enterprise architects can minimize the risk and cost of business disruptions caused by changes to business-critical applications and databases while minimizing costs and accelerating agility to meet the needs of the business.

Build an Enterprise Security Architecture
Alan D. Ross, Lead Security Architect, Intel Corporation
May 17, 4:30 p.m.
The methodology that Intel's information technology group used to develop its enterprise security architecture is significant in terms of the roles that policy, risk, emerging business drivers, and threats played as key inputs to the strategy. This presentation will focus on the methodology and these roles and then demonstrate the methods for articulating strategy as well as correlating architecture work products. The need to work with appropriate stakeholders such as engineering, product, and service management and operations to be successful will also be presented. In addition, the artifacts that are used in creating the architecture work products and the governance process that was used to approve the new security architecture will be discussed.

Register by March 22
Save $300!

	Add to your calendar  Get e-mail updates Sponsorship Opportunities Exhibit at EA Summit Interested in speaking at Enterprise Architect Summit? Click here to visit our Call for Papers site.