Please note: This material is no longer current and appears online for archival purposes only. Use the search and navigation tools above to locate more up-to-date materials, if they exist.

Software Distribution Needs Statement

Introduction

As client/server computing continues to mature, more and more software needs to be made available to end users. In some cases this software is distributed to desktop workstations. In other cases file servers are used as locations from which end users launch applications. ISC currently provides and supports a number of methods for distributing software to end users. The goal of this document is to describe the full set of requirements for these products.

---

Reasons for Common Software Distribution Techniques

Minimize end-user and local provider of support configuration time: Desktop software installation is a heavy support burden. LAN server can alleviate some of this, but in many cases installation to individual desktops is required. Good, common techniques and products can reduce this burden significantly. Standard techniques reduce support costs through consistency. Technology needs to help people do their work, not be a hindrance.

Promote campus-wide standards: Centrally-coordinated, common strategies have the best chance of promoting campus-wide standards in the area of desktop computing.

Reduce redundant work creating installers and strategies: Campus-wide efforts allow the maximum leverage across schools, departments, and centers. A set of agreed-upon solutions jointly supported by ISC and distributed units will reduce overall effort.

Ensure quality of products distributed and media integrity: Preparing high-quality software for end user installation can be tricky business. Special care needs to be taken to ensure a virus-free environment, to install proper versions with appropriate default preferences, and to update software versions consistent with server requirements. Special equipment (like special diskette duplication equipment) is most efficiently maintained in a single facility and operated by trained personnel.

Minimize license costs: License costs for software may be able to be reduced through campus-wide distribution techniques that achieve price concessions from vendors who value central coordination.

---

Requirements, Principles, and Assumptions

(...all mushed together for now...)

Types of objects: Software distribution needs to be able to accommodate both application software as well as data files.

Platforms: Both Macintosh and MS-Windows desktop computers are target platforms. Any solution supporting MS-Windows should be able to accommodate both MS-Windows 3.1 and Windows 95. Desktops should conform to the minimum standards for desktop computers. Support for distribution to LAN servers (AppleShare and NetWare) should also be included.

Users: Any Penn affiliate (faculty, staff, students, alumni) should all be able to use the supported solutions within the limits of the licensing of the software being distributed. Licensing is frequently different for some kinds of users.

Authentication and Authorization: Some software vendors require proof that Penn will only allow authorized individuals to use distributed software. A system is required to authenticate a user's identity, and check the user's authorization based at minimum on status, for access to some software.

Location Independence: User desktops need to be supported whether ethernet-attached to PennNet or remote (e.g. via PPP). Solutions may not be the same for each type of connection type.

Communications Protocol: Solutions must support TCP/IP, the only enterprise-wide protocol. Workgroup protocols such as AppleTalk and IPX/SPX may be supported additionally. Solutions may not be the same for each protocol.

New Installations: The supported solutions must be able to easily configure and install software on a new desktop computer.

Update Installations: The supported solutions must be able to easily re-configure a desktop for a new version of an already-installed piece of software. Existing user preferences must be retained if the new version allows.

Bootstrap: The supported solutions should maximize the use of PennNet for software distribution. A minimum set of bootstrap software may be necessary for distribution by diskette to make a desktop computer minimally functional on the network.

Products for distribution: The supported solutions should be able to accommodate distribution of a flexible set of products as determined by the users. Alternatively, a local support provider should be able to select a set of software and pre-configure the distribution process for a set of local users.

Prevention of needless re-installation: The supported solutions should be able to detect whether the software being requested for installation is already installed on the user's desktop, and verify the user's intentions to install.

Version Control: The supported solutions should allow for a list of approved software versions, and detect whether a user's desktop is configured for the correct versions of the products. If not, a user should have the option of installing an updated version or not. In some cases, an updated version should be required (e.g. patch to secure Netscape browser). In all cases, version numbers should be clearly identified in file names (where possible) and documentation.

Reliability and Robustness: Supported solutions must be reliable and robust, especially for use by end users. Products must indicate wherever possible the reasons for failures when they do occur, and be able to withstand a variety of users at a variety of experience levels.

Common Interface: The look and feel of supported solutions should be consistent with and agreed-upon user interface (e.g. Netscape, or native file browser/chooser as two different examples). Custom interfaces unique to the software distribution should be avoided where possible.

Standard Names: If multiple strategies are used, the same files should be named with the same names and stored in identical directory structures (if applicable).

Default Preferences: A variety of default preferences, specific to local schools, departments, and centers, must be permitted by supported solutions.

Supportability: The best solutions technically are not always the easiest to support, especially for products aimed at a wide community. Proper documentation, both for end users and providers of support, is required.

Please note: This material is no longer current and appears online for archival purposes only. Use the search and navigation tools above to locate more up-to-date materials, if they exist.