SC StoryMaker

StoryMaker began as an 80-line Perl script George Frink wrote for his own use. Several programming languages are used now and the code has grown complex. Yet simplicity of use, reliability, flexibility and speed remain the fundamental design principles of this eight-year project.

StoryMaker is and was from the outset intended to be an enterprise application.

By design, StoryMaker is extensible, readily maintained and highly scalable. StoryMaker can meet the needs of a small business, or scale up to support a large enterprise large numbers of users who are geographically distributed and who are assigned role-appropriate levels of administrative authority.

To achieve those goals, StoryMaker is divided, structurally, into three funcational layers:

• Presentation: Client components reside in the presentation layer. They handle user interaction, accepting input from users and displaying data which has been either retrieved or created by the business logic layer.
• Business Logic: Processing applications reside in the business logic layer. They accept, retrieve and restructure data, perform computations and otherwise do the primary computational work.
• Data: Work here is done by a relational database and/or like applications. They store and facilitate retrieval of structured data.
  

StoryMaker does not require expensive computational resources.
Small organizations may deploy StoryMaker on a single desktop machine which is also used for other purposes.

Publication intensive organizations are better served by devoting a machine to StoryMaker's business logic and database layers.

Geographically distributed organizations, with large numbers of users, will find it is best to dedicate one machine to business logic and another to database functions.

Client functions always reside on individual user's desktops.

Back to Method.