Tools Risk Analysis - Initial Merger Assessments

Tools Page 1 of 8

Content Links

History and

Purpose Audience

for thisDocument

Team Members

Legend forTechnologies for

New Development Systems

Server Development Languages

Client Development Languages

Web Development and Technologies

Database Management Systems/Data Loading

End-user Reporting and Query

Developer Reporting and Query

Modeling

DevelopmentSupport/Management/Distribution

Collaborati

on Testing

Batch Reporting

Online Help

Initial Risk-Assessment

History and Purpose

During the merger process, many new systems will be built. On a project-by-project basis, the choice of technology will drive cost estimates for meeting "synergy targets". In addition, a standard application tools portfolio will allow for competencies to be shared amongst divisions in the US IS areas of GSK. Choice of technology will also have many other technological and cost implications. The purpose of this document is to assist project- level IS decision-makers to choose technologies for these new projects that are high-performing and low-risk.

A survey was completed in June 2000 by each division in US IT for both GW and SB to capture current technology architecture and tool component usage and trends. Information was analyzed and compared jointly. SB and GW met to decide on an initial guideline list of technologies for new development, as seen below.

Audience for this Document

US IT Directors, US IT Managers, and US IT Developers in GW and SB. In GW, specifically for the COIS and CFIS divisions. In SB, specifically for the merged divisions.

BACK TO TOP

Team Members

GW: Bill Almand, Margaret Dischler, Denise Hall SB: Peter Isakson, Fred Orensky, others

BACK TO TOP

Legend for Technologies for New Development Systems

Tools Page 2 of 8Color Coding

Interpretation

Tools Page 3 of 8

Green Low risk. High likelihood that this tool will remain/become part of the GSK applications architecture portfolio. A good choice for new development.

Yellow Risky. This tool may or may not remain/become part of the GSK application architecture portfolio for one or more reasons, or may be limited to only niche areas. A risky choice, but not necessarily a wrong choice, for new development. See specific ‘comments’ section on each technology below that has been ‘yellow-lighted’. Items listed with a comment of "potential area of convergence" are technologies in a category where we feel that the new GSK organization will likely, or needs to, step back and evaluate either at the local US level or possibly the global level.

Red High risk. Avoid use of this tool. Both SB and GW agree that this tool is not strategic for NEW development. It is understood and agreed that systems already using this technology will most likely continue to use it for future maintenance/enhancements.

BACK TO TOP

Server Development Languages

Languages used to develop application logic running on servers.

Tool/Language Purpose/Comments

Cobol Limited to extensions of existing systems only

Focus Mainframe language.

Javascript Client-side

Oracle ProC Oracle-based applications wherecompiled performance is critical

PERL Utilize for scripting.

PL/SQL Oracle-based applications, NT and Unix

RPG Limited to extensions of existing systems only

SAS Analytical applications. UNIX preferred. Avoid mainframe and pcSAS if possible.

Tools Page 4 of 8

SyncSort Use as a utility for high performance sorting; do not use the language portions

Transact SQL No use of MS SQL Server whereapplication logic must run on server (use Oracle)

UNIX Shell Scripting

Any shell language allowed

Visual Basic 6 VBScript or compiled objects

Note: Also refer to Web Technologies section.

BACK TO TOP

Client Development Languages

Languages used to develop application logic running on clients.


MS Access New development using Access as a front-end GUI is strongly discouraged in favor of Visual Basic. Limited to small, low complexity small group/personal or transportable apps which also require offline use of an MSAccess db. See ‘Database Management Systems’ section for MS Access dB risk assessment.

PowerBuilder Continue to use for existing

applications. Visual Basic 6 Includes VBA for Office Products

(Excel,PowerPoint, Word, etc.)

Note: Also refer to Web Technologies section.

BACK TO TOP

Web Development and Technologies


Acrobat Reader

ActiveX For intranet use only. Be careful if using Hosting services like Citrix server. The desktop is affected by the components and

Tools Page 5 of 8

needs to be handled with care, especially due to the SB lockdown of the desktop.

ASP/IIS Potential area of

convergence. Domino 4.6.3/5 Potential area of

convergence.

DreamWeaver Utilized at SB; being heavily considered inGW COIS.

Flash

FrontPage98 Standard at GW.

Homesite Utilized at GW COIS and SB.

IE 5 Migrating from IE4 by 4th Qtr 2000.XML, HTML, DHTML

Interwoven Content management and version control.Workflow and distribution into production.

Javascript Client-side only

Report2Web See ‘End User Reporting and Query’below.

Shockwave

Visual InterDev

BACK TO TOP

Database Management Systems/Data Loading


DB2/400 UDB Only for extensions of existingapplications

Informatica Information extraction loading tool (ETL). PowerMart portion used primarily at SB.

MS Access Use of database limited to small, low complexity small group/personal or transportable apps. See ‘Client Development Languages’ for risk assessment of front-end GUI of MS Access.

MS SQL Server 7 Where required by application purchased

Tools Page 6 of 8

Oracle 8.05 NT or UNIX – preferred DBMS platform

BACK TO TOP

End-user Reporting and Query

Tools given to end users to build/execute their own queries and reports


Brio Only for applications limited to GW located users near term. Potential area of convergence for GSK. We feel that GSK will or needs to re-evaluate a US, US/UK, or global end-user and reporting tool to capitalize on licensing and integration across tools.

Business Objects For use at GW; currently in use in R&Dareas. Potential area of convergence for GSK. We feel that GSK will or needs to reevaluate a US, US/UK, or global end- user and reporting tool to capitalize on licensing and integration across tools.

Cognos Impromptu Only for applications limited to SBlocated users near term. Potential area of convergence for GSK. We feel that GSK will or needs to reevaluate a US, US/UK, or global end-user and reporting tool to capitalize on licensing and integration across tools.

Cognos PowerPlay Only for applications limited to SBlocated users near term. Potential area of convergence for GSK. We feel that GSK will or needs to reevaluate a US, US/UK, or global end-user and reporting tool to capitalize on licensing and integration across tools.

DSS Agent For use for high-end analysts.

MS Access Limited to accessing local small databasesonly.

Report2Web Niche product. Major use is to burst largemainframe GW sales reports into smaller reports and display through the web.

Oracle Discoverer OK at SB for high-performance against

Tools Page 7 of 8

large sets of granular data. Use BRIO at GW instead for same need.

BACK TO TOP

Developer Reporting and Query

Tools used by developers to create "canned" queries or reports that end users execute but do not modify (except for parameter substitution)


Cognos Impromptu Only for applications limited to SB locatedusers near term

Cognos PowerPlay Only for applications limited to SB locatedusers near term

Crystal Reports Limit due to compatibility issues acrossversions which can cause incompatibilities for the desktop DLL’s. Avoided at SB due to SB desktop lockdown.

DSS Agent Only as embedded reporting

engine. MS Access 97 Only as embedded reporting

engine.Against small databases or running storedprocedures.

Oracle Discoverer Do not use at GW for new development.Niche use at SB currently.

SQR Only for applications limited to GW located users near term.

BACK TO TOP

Modeling


Oracle Designer Use at GW. Potential area of convergence.Preference is to have one GSK corporate modeling tool for databases.

ERWin Use at SB. Potential area of convergence. Preference is to have one GSK corporate modeling tool for databases.

Tools Page 8 of 8BACK TO TOP

Tools Page 9 of 8

Development Support/Management/Distribution


PVCS Limited to use for existing applications.

SMS Use for distributing software (e.g.GWARP at GW)

Visual SourceSafe Ideal for client/server applications thatutilize Microsoft front-end development. Less ideal for UNIX based systems, but possible to use.

WinInstall

BACK TO TOP

Collaboration


NewsGroups GW currently uses for online collaboration.

Domino 4.3.6/5 Limited to SB-based users, unless via pureWeb access

BACK TO TOP

Testing


SQARobot Utilized only for CARS/IS application at GW at this time.

Test Director This is GW’s primary tool for the SFAsystem.

WinRunner

BACK TO TOP

Batch Reporting


SQR Use in circumstances for high-volume batch reports where writing them in ‘C’ is

Tools Page 10 of 8

the only other alternative. SQR is much easier, faster to write in than C and performs almost as well as C (execution speed).

Business Objects Under review; may belong in a different category.

BACK TO TOP

Online Help


RoboHelp

Doc-To-Help Pro

ForeHelp

RoboHTML

ForeHTML

FrontPage

Other:

Computer telephony interfaces in the Customer Response Center. Other "Web Publishing Tools" Miscellaneous

BACK TO TOP