Open Source vs. Open Systems

A Profile and Comparison

Sasan SalariVP, New Technology Services

Head, Vista Developers NetworkJuly 14th, 2004

Open Source/Open Systems• Why all the buzz on this?

• What is Open Source? An Open System?

• What are the pros and cons of each?

• Can you leverage both?

What does Open Source

really mean?

Open Source

“Source-inspectable software, with varying degrees of

freedom”

Donald K. Rosenberg

Open Source

Many different Open Source Licenses:– GNU GPL– Lesser GPL– BSD License– Mozilla Public License– IBM Public License– Sun Community Source

License

Define rights for:

– Modification– Distribution– Derivative Works– Commercialization

Open Source: Pros

• Complete ownership and control of software assets for modification, extensions and deployment

• Reduced development effort / time by re-using existing code

• Source is collective input of variety of constituents, therefore addresses broader set of functional use cases

• Perceived lower cost due to free or minimal license fee

Open Source: Cons

• Often non-production designed/coded, reference implementation

• Typically little inline commenting or associated technical documentation

• No guarantee of open standards

• Potential for high production costs as the system complexity increases

Open Systems Profile….• What is an Open System?

– a software application comprised of a well defined collection of integrated components, with a standards-based interface

– typically “productized” and developed by a single software development vendor, by a managed software development team and process, offered for purchase at market cost

– terms often do not allow modification or redistribution per the original source license, but encourage open development and deployment of functionality extensions and customization

Open System: Pros

• Stable core application framework and functionality

• Architected, implemented, tested, and optimized for high quality production

• Framework based on well-defined open standards facilitates interoperability via programming interfaces.

• Vendor/central source development process, expertise, support, services

Open System: Cons

• Vendor controlled product landscape, release cycle, and feature-function set based on collective customer input

• Customization and extensions bounded by available open programming framework and interfaces

• Service/support may be required

• License term constraints, fees/cost

NOT an Either / Or….

• Open Source within an Open System

• Open System leverage of a sound baseline application, standards-based framework of functionality and interfaces

• Open source components or “libraries” to fuel application development of customizations and extensions

Vista…a Leading Open System

Vista…a Leading Open System• Highly scalable, enterprise class baseline

application

• Standards based implementation

• Powerlinks SDK– Web Services, Java– “Safe” interface layer– Deployable component framework, adapters

PowerLinks Components

Vista Developers Network• Online resource center for Vista PowerLinks

Developers

• Open to designated developers at Vista customer institutions and PowerLinks partner companies

• Launch: Q1 2004

Vista Developers Network

DevNet Features

• Links to WebCT Documentation and Resources

• Contribution Area to Share PowerLinks and Code

• How-To area where users can add their own tips and tricks

DevNet Features

• Frequently Asked Questions

• Discussion Forums

• List of known issues and their workarounds and resolution targets

• + much more…

http://devnet.webct.com

PowerLinks Partners

Vista…Critical Role of Standards

• Enables heterogeneous applications and systems to interconnect through a common protocol

• Fosters well-defined, managed, consistent, broadly applicable interfaces

• Facilitates modular, “plug-in” framework and components

• Embodies requirements specific to variety of functional areas and associated constituencies

Vista…Standards Leadership

Standards Body Impact

IMS Enterprise, Content Packaging, Profiles, Digital Repositories, Accessibility, Simple Sequencing, Learning Design, Question & Test Interoperability, Web Services

Productized integration with SISs Reusable, granular, content packages and LOs and LMs Personalized learning paths Heterogeneous application/platform tool/service integration

Open Knowledge Initiative (OKI) Additive/alternate standard Java interface framework for e-learning interop./extensibility

ADL: SCORM Standard reusable LO aggregate modules with content, behavior, sequencing

JA-SIG: J2EE, uPortal Proven, open standard, enterprise framework for system independent interop.

Internet2 - Shibboleth Emerging, HED optimized interop. framework, underlying standards

Vista…Open System Interoperability• Integration Framework

– Enables modular, “productized” adapters for non-custom, standards based, integration with campus systems

• SIS– SCT, Datatel, Peoplesoft, custom adapter components

• Directory Services/SSO– LDAP, MS-AD, Kerberos, WebISO, custom

• Portal– CP, uPortal, PS, Oracle, Epicentric, CampusCruiser, custom

• Web Services– Enable campus applications, 3rd party partner apps, .NET

• Digital Repositories: ECM, Library

Vista Interoperability Framework

In Conclusion…

• Carefully assess the balance of your open system vs. an open source solution in terms of tolerance for level of effort, time, risks, skills, scale etc.

• Strongly consider the open system leverage AND optional open source based extensions where applicable

Thank You

salari@webct.com