|
|
|
|
| |
| |
Maximizing the Business Value of Software
Nick Jackson
Two-thirds of all software projects are considered failures today. Software errors cost the U.S. economy $59.5 billion dollars annually. It's obviously time for change. This presentation will examine why aligning people, process and technology is essential in shifting software development from a chaotic art form to a managed business process. It will also provide unique insight into how development tools and processes are evolving to change the way software teams work together - at all levels, from all locations.
Nick Jackson, Borland's managing director for the ASEAN region, will lead an animated discussion on the importance of aligning people, process and technology in a development environment that is becoming more complex every day. Nick will provide historical context on why a holistic approach is necessary for making software development more repeatable, predictable and successful and what advancements will enable this transformation. He will also explain how the integration of products and processes are happening today, and why people - from developers to CIOs - are driving this evolution. Through customer examples and technology demonstrations, he will show you how this will change the way software teams work together today and in the future.
Back to the top
|
Microsoft Enterprise Software Application Platform
K. Daniel Ingitaraj
Director, DPE, Microsoft Singapore
An enterprise software application platform suitable for building connected systems is much more complex than a traditional application server. It includes elements such as client and server operating systems, development tools, applications services, and so on. Most organisations utilise products from multiple vendors for these elements in their enterprise software development platform, and hence require that all elements be able to interoperate and integrate with elements supplied by different vendors.
This keynote will describe the comprehensive Microsoft enterprise application development platform for building connected systems. It will cover the core components of this platform, including the support for core standards and service orientation that enable each element to interoperate with elements provided by different software vendors.
This session will also highlight SOA Blueprint best practices in a functional and behavioural specification to demonstrate how SOA can solve real-world issues.
Back to the top
|
Optimising Distributed Application Scalability, Performance and Availability
Ingo Rammer
Microsoft Regional Director
Austria
Creating and operating distributed and service-oriented applications presents new challenges for scalability, performance and availability. In this session, you will learn the performance and scalability implications of technologies like ASP.NET Web Services, .NET Remoting, Enterprise Services, MSMQ, and the Web Services Enhancements (WSE). This session helps you to gauge the differences in performance and scalability between certain technologies and to establish a strong technical foundation for your own applications. Furthermore, you will also learn how to take advantage of availability and throughput increasing features that are built into the Windows Server operating system. Do you know that creating a failover and load-balancing cluster with Windows Server System takes only about 15 mouse clicks and no special hardware is required?
Back to the top
|
Learning from the 1920s
Clemens Vasters
Co-founder, CTO, newtelligence AG
New York, Union Square, Circa 1920. The Metropolitan Life Insurance Building. Computers were missing from the scene. How did it all work?
Today, it is confounding that large organisations did indeed function, and function effectually, before the arrival of Information Technology. They had well-defined processes, forms, paper-based communication paths, roles and products that all somehow neatly pieced together into a functioning business. It is interesting that we are seeing the equivalent of many of those “old” concepts again today, save that we call them, in contemporary computer jargon, as orchestration, schemas and messages.
In this session, Clemens Vasters shares his thoughts about what we, and service-oriented system design, can learn and benefit from the 1920s.
Back to the top
|
|
|
|
|
