Search
 
 
 
 
 
 
 
 
 
 
Tell a friend
Managing Business
                              more
                          
 
Win Prize
                              more
 
Come along with your team
                              more
 
 Keynote Speakers:

Speaker
Description

Title: Architecture Adoption for Enterprise Survival,          Business Innovation & Risk Avoidance (Quarter on          Quarter)

Abstract:

In this keynote, Sunil is going to discuss on the evolution & adoption of Architecture within Enterprises for Innovation and Risk Avoidance. How do organizations are adopting Architecture principles (formal / informal ways) to manage change & complexity.

As IT is becoming core to all the other natural science, what are the advancements needed?

What are various architecture artifacts, how do we model (represent & specify) them and the challenges of establishing linkages across multiple stakeholders?. There is also a serious need to establish parameters for measuring effectiveness of architecture. What are those parameters?

Also, he is going to elaborate on

  Architecture Frameworks & It's relevance & usefulness wrt to       different business models.

Compare the "Periodic Table of Enterprise Framework" wrt to    Current Business & IT Scenarios.

How does "Architecture" addresses the issues of Change &    Complexity Management (Case Study).

 Architecture Metrics & Measurements.

Impact of Globalization on Architecture.top

Michel Susai
Michel Susai
CEO - NeoAccel

Title: End to End Enterprise Security Architecture

Abstract:

While most of the companies stop at enforcing a strong authentication mechanism as a solution for all security problems; the complete end to end security architecture should encompass much more than just authentication. True end to end security architecture provides functionalities to help corporate network from threats without affecting business. Each enterprise, based on their business needs, size and infrastructure may use different functionalities of a NAC solution.
Primarily the solution encompasses all aspects of controlling what users can do on an internal network.

Following are some of the important points that take you to provide true End to end Security Architecture:
1. Identification of the node (multi factor authentication methods)
2. End Point Security Compliance
3. Securing Access within inside (intranet security - LAN/Wifi)
    a. 802.1x
    b. WPA (Wireless Protected Access)
4. Securing access from outside (Extranet - remote/sts security)
5. User based authorization control - The solutions vary from     network authentication solution to allow authorized access or     an Endpoint compliance system or for real time inspection of     traffic.
6. Secure tunneling using SSL/TLS security
7. Complete audit trail
8. Data leakage prevention.
9. Leave no trace - cleanup critical information after access so     that it is not left inadvertently
.top

Title: Enterprise Architecture - Quality and Standards
         (should) Drive the Serving our Customers in a SOA
         world”


Abstract:

SOA is an evolution of architectural and design approaches which has a produced a major seed change in the way we think about software engineering. Solutions are becoming more complex and with this complexity come the need to understand better what and why we are doing things. Plus as the business of IT evolves so must
our understanding of the ways in which we interact and mimic the business.

To be effective in today's high paced, high stakes software development industry we need to adopt and work with standards that
will provide a window on the quality that a customer can expect. Even in the areas of XP and Agile the need for standards is paramount. It is simply the representation that changes. How we can effective engage the customer and what we set as basis for our mutual understanding is what will drive the perception of quality.

This talk will address:

1. The History of SOA (abbreviated)
2. How we came to Standards
3. The Standards We Need
4. The Difference between SOA and Integration
5. An Example on Extensibility by Design
6. Quality Success Factorstop

Title: Grid Computing - the new paradigm in High          performance

Abstract:

The information age is producing humungous amount of data that requires a paradigm shift in thinking about how to store and process this data. Traditional architectures fade into cost overruns, scalability and ROI issues.

Distributed computing is the answer. In traditional High performance settings, one often assumes a "well-behaved" system: no faults or failures, minimal security requirements, consistency of state among application components, availability of global information and simple resource sharing policies. While those assumptions are arguably valid in tightly coupled systems, they break down as systems become more distributed.

This presentation will talk about Hadoop architecture and some case studies on how it is used to solve high performance computing problems. Hadoop is a grid-computing framework for running applications on large clusters built of commodity hardware. It lets one easily write and run applications that process vast amounts of data (terabytes to petabytes).top

Title:Enterprise 2.0 Architecture Revolution

Abstract:

Enterprise 2.0 has just arrived to bring the power of Web 2.0 and Social Networking in enterprises. While SOA 2.0 significantly impacted on transforming how we design & use composite applications, Enterprise 2.0 is revolutionizing on how we work together and realize the power of communities and social computing in an enterprise.

In the current era of Web 2.0, so-called "Digital Generation People" are more tech savvy than ever and how they work are changing. This has started impacting enterprises as well where they perform the role of information workers. Their expectations within an organization are increasingly shaped by their experience on public web sites that offer highly participatory personalized interfaces and tools such as Blogs, Wikis, RSS, tagging, social networking, Mashups etc. To work and run businesses effectively, they see a definitive need to integrate information from many sources, access Information & applications anytime anywhere, combine ad-hoc work with enterprise applications & processes, work with others as virtual teams in a task-oriented fashion for short durations in the context of projects. This is resulting into the convergence of 1) transactional applications, 2) SOA composite applications, 3) Enterprise Portals and 4) Web Sites and revolutionizing a new User Interaction Paradigm in the Enterprise Architecture.

The session begins with discussing the drivers, challenges and demands for Enterprise 2.0 architecture. It then highly focuses on Enterprise 2.0 building blocks and a deep insight into Enterprise 2.0 Architecture. Oracle Fusion Middleware Enterprise 2.0 architecture - a latest innovation from Oracle is referred as an example.

top

 

 

 

Title: Architecture complexity- What is its worth?

Abstract:

In today's world of constant change, creating architecture and growingit as per the business need has been the most challenging for the CIOs.Globalization, Mergers and acquisitions, security, technology rate of change, obsolescence, refresh cycles, emergence of standards, compliances and regulations - All are contributing to the complexity of enterprise architecture. Is there a way out of it? Should the CIOs and CTOs have to live with the complexity? This presentation is aimed at discussing and elaborating on these challenges and sharing strategies adopted by some organizations.top
Title: Managing Global Product Line - problem areas and solution strategies


Abstract:

Managing Global Product Line presents a common set of requirements encountered and solution strategies implemented for Global Product Line management programs. It covers problem areas and solution strategies around managing the core global product and its release cycles as well as managing variations and release cycles across all its deployments in different geographies.

The solution strategies address the following major requirements and more:
 Customizability: For accommodating variations in different    geographies across the globe for feature set variations,    regulatory variations, compliance changes, business rule    variations etc. The solution should be able to pick and    choose specific feature sets for a particular custom    deployment.
 Thin Customizations: Less maintenance cost for each    custom deployment.
 Internationalization: Should be catering to different    languages and currencies, date formats etc.
 Release Management: Parallel releases of core and    custom products as well as different releases of custom    products.
 Deployment: Different custom deployment options for    different needs based on size of the geography, political    scenarios, business rules etc.
Predictability: Predictability of impact for implementing and    managing a change. Cost of change in core and custom    version should be predictable.

The solution strategies include:
 Architecture: Architecture of the core product should allow    interfacing with different systems based on the needs of    custom deployments.
Design: Design of the core product needs to be extensible    such that it allows providing a rich set of core features with    defined extension points for custom enhancements. The    design should also allow plug in and plug out of various    functional components as required for particular deployments.
 Internationalization: Internationalization solution need to go    much beyond what J2EE provides. Internationalization    capabilities need to be built in within the core product thus    allowing regionalization per locale and geography.
Governance: Processes need to be defined for configuration    and release management as well as a governance model that    clearly defines change management, parallel release    management, product upgrades, adherence to common    development model and justifications for divergence.
Estimation Processes: Estimation and sizing model should    predict the impact of change. top

Title: 7 Habits for an Effective Enterprise Architect
(You become an Architect by virtue of your technical prowess but you succeed by putting your soft skills to use)

Abstract:

Designing an architecture blueprint for an enterprise comprising of multiple diverse businesses requires a different level of skills and habits on the part of the Enterprise Architect than devising solution architecture for a point solution.

The speaker has devised a set of 7 habits which an Enterprise Architect should follow to become effective. Many of the seven habits highlights soft skills which the enterprise architect needs to consciously develop to be effective and successful. As the speaker often says -"You become an Enterprise Architect by virtue of your technical prowess but you succeed by putting your soft skills to use."top

Title: Challenges in defining & managing Reusable Assets for the enterprise - lessons learned

Abstract:

In the knowledge era Enterprises are complex, intangible and deeply embedded as systems. The need for Architected Enterprise is felt by one and all to mange burgeoning complexity and change. Today there are talks of manufacturing enterprise to order. If collectively we call the intangibles as software and that is the only asset worth managing to have sustained competitive advantage, then we need a scientific approach to create and manage enterprise assets.
This presentation provides insight into a standardized way of conceptualizing, building and deploying reusable software components in an enterprise ecosystem to foster much needed innovation. It also brings the gaps in the current industry practices and an imperative to don a new role of Architect as software economist in defining the IT systems within the enterprise
.top

 
 
        
 
Register
 

 

 
Key Focus Area
Key Highlight
Panel Discussion
Architecture assessment

 

Copyright 2008 iCMG. All rights reserved.
Site Index | Contact Us | Legal & Privacy Policy