Introduction; Boeing scope by the numbers

Web is particularly valuable for huge, highly dispersed, = computer-dependent corporation
Early corporate adopter ('94); pre-existing big network, free software made it easy
Currently one of largest intranets in world

~5,000 internal web servers
~180,0000?? clients
~2,000,000 pages indexed (that's the license limit; takes 12 days of = 7x24 processing)
~6,500,000 requests/hour to web forward proxy servers
~35,000 external partners, customers, suppliers logging on through = reverse proxy

Corporate culture

Most enterprise-wide functions have moved to web applications (e.g., = payroll, personnel information, company news; benefits)
Also used for most local information sharing functions

The web has become an expected part of the work place
People are surprised when they can't find information on the web
Senior executives look to web technologies to e-enable the company

Corporate philosophy

Early development -- grass roots development; little management = oversight
Now -- identified as a strategic tool for enterprise system = development
The single defining quality of the web is the ability to put a document or application in one location and enable virtually anyone to access = it
Strict client standardization:

Interoperability stated as a foundational principle; guidelines are = published

Problems

Browser upgrade compatibility problems

Short release cycles, numerous releases or patches
High risk and high cost of introducing new versions into the = enterprise

Cost and complexity of deployment
Because of the number of web applications exhaustive testing is not = possible
Benefits must outweigh the risk

Third-party, partner- and supplier-developed applications
Contract development
Developer desire to leverage advanced features in latest software = versions
Lack of developer training, especially in Boeing-specific goals and = techniques (for both employees and contractors)

Problem examples

Browser Compatibility

Even minor version upgrades have the potential to break existing web = applications

Web application A requires browser version x.xx
Web application B requires browser version x.yy

Netscape 4.05 - 4.06 subtle changes in DOM caused existing web = applications to fail
Netscape 4.5 - 4.73 minor changes to Netscape JVM causes applet to fail under certain conditions
Works with IE not Netscape

Mainly integration features
ActiveX controls

Works with Netscape not IE

Mainly DOM and CSS features

Problem examples (continued)

Third-Party or Partner Web Applications

Third-Party web applications often have very specific browser version = requirements
These requirements are often difficult to coordinate with the requiremen= t of other applications
In most cases, the application is not modified and a technique must be found to work around the issue

Contract development

Applications are often developed with little coordinated testing inside the corporation
Problems are often found at the "last minute"

Javascript performance problem

Problem examples (continued)

Corporate bleeding edge

Streaming media
Flash
XML
CSS
...

Summary

Boeing views W3C specifications as key to establishing solid = interoperable web content and applications.

Feedback to the W3C:

Define specifications that include definitive examples
Use these examples as the basis for test/validation = suite(s)

Feedback to client and tool vendors:

Document what is supported
Where the specification is not completely clear,

document what you believe is supported