BOEING COMPUTING INFRASTRUCTURE The following topics are presented to identify the need of the new CSW software

to be compatible with future computing systems at The Boeing Company. (1) CU !"T C#$%UT&"' S(ST!$S

Computing systems at Boeing are currently dominated by a mi)ture of U"&* (+&*, -%.U*, Sun#S) and Windows ("T, /)) machines. + single unified U"&* file system completely separate from the Windows file system is present on many programs. Third.party products (e*ceed, Win00, WTS) are often used to lin1 the U"&* and Windows file systems. 2urthermore, some applications also reside on mainframes. (3) 2UTU ! C#$%UT&"' S(ST!$S 4egacy systems will e5ol5e to more des1top machines that ha5e &ntel C%U hardware and fewer U"&* machines. +s a result, there will be C%U off.loading from ser5ers to the des1top. The client.ser5er infrastructure used in current systems will be retained as the preferred infrastructure in future systems. This computing infrastructure will support an estimated 1677 CSW users located at many sites, world wide. The current trend for operating systems is towards Windows but this decision may be impacted by the remedy being considered in a high profile case being pursued by the 0epartment #f 8ustice (0#8) against $icrosoft. The CSW computing system infrastructure shall not e)clude the option of low cost migration to emerging operating systems. (9) U"&2(&"' T!C-"#4#'( +t this point in time, it:s difficult to pinpoint unifying technology that will deli5er an integrated U"&*;Windows en5ironment in which to build the CSW. Some of the 1ey parts in future CSW are< 0istributed file system . assume a single file system that is accessible by U"&* and Windows machines. S+$B+ is being used in current systems (%hiladelphia, Seattle) to unite the two platforms and may also be used in future systems. #b=ect technologies that are directed to client;ser5er de5elopment must be supported. Three distributed ob=ect computing paradigms are a5ailable< 0C#$, C# B+, 8a5a; $&. Currently, the preferred paradigm for the Boeing CSW is #$'>s C# B+. *$4;S?' . *$4 will be used for mar1up in stress note documents. S?' is the successor to C'$ and will be used for defining graphics in stress note documents. Based on current industry directions, 8+?+ and *$4 will be important in unifying the CSW. %ortability amongst different systems is enhanced with these technologies. Connecti5ity to database ser5ers.

(@) C+0 systems C+T&+ @, U', and %ro;! are in use on current Boeing programs. C+0 usage is appro)imately as follows. The A7B of Boeing that is commercial airplanes (BC+) uses C+T&+. The @7B of Boeing
333AC1@96.doc.1 CSW A;13;3777 7@<7C<77 %$

that is defense and space (+D$ and SDC) is roughly half C+T&+ and half U'. This means that current C+0 usage is 67B C+T&+ and 37B U' appro)imately. %ro;! usage is a relati5ely small, single.figure percentage. C+T&+ !no5ia ?.C is the announced future standard for large Boeing aerospace programs, including the 8S2 program and all new commercial airframe de5elopments. +C #"($S ........ +D$ E +ircraft and $issiles BC+ E Boeing Commercial +irplanes C+0 . Computer +ided 0esign C+! . Computer +ided !ngineering C+T&+ . Computer +ided 90 &nteracti5e +pplication C'$ . Computer 'raphics $etafile C# B+ . Common #b=ect eFuest Bro1er +rchitecture (a.1.a., the G$iddleware that>s !5erywhereG) CSW . Common Structures Wor1station 0C#$ . 0istributed Component #b=ect $odel #$' . #b=ect $anagement 'roup %ro;! . %ro;!"'&"!! $& . emote $ethod &n5ocation SDC E Space and Communications S+$B+ E programs that implement the S$B protocol S$B E Ser5er $essage Bloc1 S?' . Scaled ?ector 'raphics U' . Uni'raphics *$4 . e*tensible $ar1up 4anguage !2! !"C!S .......... C# B+, 0C#$, and 8a5a; $& http<;;www.e)ecpc.com;Hgopalan;misc;compare.html 8a5a; $& and C# B+ http<;;www.omg.org;library;wp=a5a.html *$4;S?' http<;;www.library.boeing.com;gartner;research;ras;67677;676A@;676A@.html

333AC1@96.doc.2 CSW A;13;3777 7@<7C<77 %$