Specifications

Now that we have the requirements, we can lay out the specifications. The specifications give a better understanding of what is necessary for the application. With a set of detailed specs, two programmers should be able to create almost identically functioning applications (although, admittedly, their internal implementations may differ markedly).

Users

The application should support two types of users: registered users and the general public. Since we are building a simple application, distinctions between the different user types will be clear-cut:

registered users

Registered users have script upload privileges. They can add new scripts or modify their own scripts that are already in the system.

general public

The general public has full access to scripts in the system, with the ability to download any of them. They cannot add, edit, or delete any scripts. They can send an email to any email address with a link to a specific script.

Scripts

Scripts are stored in a database. The application limits the size of each script; this script repository is intended for small scripts that implement one specific piece of functionality, not entire applications. Storing scripts in a database allows for easy access, change tracking, and download tracking.

Each stored script should have the following information:

author

The author of the script, in the form of last name, first name. The author’s name is available to the application because the user uploading the script is already ...

Get Flash Remoting: The Definitive Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.