1 / 8

Infrastructure for Software Service Provider

Infrastructure for Software Service Provider. Aditya Mathur. Last Update: August 6, 2003. Current paradigm for software distribution. Commercial software is distributed as:. Shrink wrap . We buy this from a physical or an online shop. Updates are sent on media or directly on-line.

teague
Download Presentation

Infrastructure for Software Service Provider

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Infrastructure for Software Service Provider Aditya Mathur Last Update: August 6, 2003 BITS C461/IS C341 Software Engineering

  2. Current paradigm for software distribution • Commercial software is distributed as: • Shrink wrap. We buy this from a physical or an online shop. • Updates are sent on media or directly on-line. • Embedded software comes with the device purchased. Updates are via the network or manually installed by specialists. BITS C461/IS C341 Software Engineering

  3. Implications of the current paradigm [1] • Usually, a customer buys the entire application that may have thousands of features. • A user generally uses a small fraction of the entire application feature set, but pays for all! • A new release is usually purchased at an additional cost. • Sharing of data produced by an application becomes difficult or impossible if new release is not purchased. BITS C461/IS C341 Software Engineering

  4. Implications of the current paradigm [2] • All features of an application are usually constructed and maintained by one company. • If an application binary requires X amount of memory and Y number of users buy it then the total disk space used is XY. • User’s are forced to buy more memory, primary and disk space, to load an entire application even when they do not use most of it. • Switching from an application from one manufacturer to another application with the same feature set but by a different manufacturer, incurs additional cost. BITS C461/IS C341 Software Engineering

  5. App 2 Capsule Capsule Capsule Capsule Capsule App 1 App 3 Set of dynamically composable applications An alternate paradigm: Capsules and SSP BITS C461/IS C341 Software Engineering

  6. User Subscribes to SSP (LFAM) App 2 Selects an app (LMI) Capsule Capsule Capsule Capsule Capsule Begins using the application (CS) App 1 App 3 LFAM: Library and Financial Accounts Manager LMI: Library Management Interface Set of dynamically composable applications CS: Capsule Server User’s view Pays for use. Never needs to buy an application (LFAM). BITS C461/IS C341 Software Engineering

  7. Developer Browses capsule specifications (CSV) App 2 Capsule Capsule Capsule Capsule Capsule App 1 App 3 CSV: Capsule Specification and Validation Set of dynamically composable applications Developer’s view Selects capsule(s) for development Submits capsule (CSV) Gets paid depending on Capsule use (LFAM). BITS C461/IS C341 Software Engineering

  8. Your tasks • Understand the problem well. • Perform requirement analysis. Make good use of information and components already available to you. • Design SSP infrastructure components. Give careful thought to various component interfaces and features. • Prototype the SSP infrastructure components and show that this is a feasible concept. Be a pioneer! Do something different! Something useful! BITS C461/IS C341 Software Engineering

More Related