File Manager Application Requirements

by Ron Henderson and Joshua Finkler

I. Introduction

The following is a requirements document for the ACS File Manager application.

II. Vision Statement

Content managers often need to be able to work on a site without having access to or the knowledge to interface with such file-transfer programs as FTP, SCP, and the like. The File Manager application will provide a Web-based user interface for uploading and editing text files and for uploading binary image and program files. It will integrate with our current permissioning system and shall be fully CVS compliant so as to allow proper version control tracking for all file system changes.

III. System/Application Overview

The File Manager system will emulate a file browser by using icons to indicate file status and type for each file handled by the system. The file types to be covered are: editable (text) file, editable (image) file, folder, locked file, and forbidden file.

IV. Use-cases and User-scenarios

File Manager users will typically be HTML designers, graphic artists, and content editors who oversee text and graphics displayed on the site. All users of the system must have site-wide administration privileges.

V. Related Links

VI.A Requirements: Data Model

The File Manager application has no associated data model.

VI.B Requirements: User-Level Requirements

VI.C Requirements: Version Control

VI.D Requirements: Permissions

VI.E Requirements: Configurable Behavior

VII. Implementation Notes

The behavior of the File Manager application should be configurable via a set of parameters indicating: whether or not version control is to be enabled, any salient version control parameters if so, and those directories accessible via File Manager.

VII. Revision History

$Log: requirements.html,v $
Revision 1.1.1.1  2001/04/20 20:51:14  donb

Forgot to define binary files before importing, so .gifs were messed up.

Revision 1.1.1.1  2000/11/21 08:15:18  ron
initial version


Joshua Finkler