It's Just What I did

Concept Document
It is ideal that Concept Documentation is created with the Project Managers and Content Developers. This document should focus on the following:

• Overall guideline for the project
  
• Determine Project Goal
  
• Target Audience
  
• How to achieve Goal
  
• What type of multimedia to use to achieve goal.
  

With all of these areas defined we can move on to the next step, Technical Specification.

Technical Specification
The project managers and Developers should create the specification based on technology and the concept documentation. This step of the application design should be in complete detail, leave no void in any detail if a function is not applicable state the function and reason why it isn’t applicable for reference only. These specs will provide the developmental limitations and technological framework in which to develop the application. If there are any add-ins or adjustments, they must follow the specs already provided. It is extremely important to keep in mind your end user for the technology they posses may not be as advance as the technology that is available to you.

These specifications should encompass the following in complete detail:

• Define the technological frame work for the project.
  
• Platform - Mac, PC, Palm, Pocket PC, Blackberry, Other
  
• Operating System and version
  
• Delivery method
  
• Storage requirement
  
• Screen size
  
• Color depth
  
• Audio & video
  
• Networking
  
• Support software - browser, plug-ins
  
• font
  
• description of color pallets to use
  
• code resources
  
• hardware configuration
  

Flow Chart
The flow chart is designed by the development team, depending on the content and the perspective view of the end user. A flow chart is a visual map of the application. It should detail each screen in the application, including a list of major components, such as text, audio and video assets, interface controls, and input and output methods (data fields, text areas, etc.). The details listed in the flow chart are related to the information in the functional specification.

The flow chart is a key to determining the navigational flow of the application. Included all navigational control at this stage, including things such as help and quit buttons. Please confirm the steps of the flow chart to determine if the information you are presenting is optimal and as you desired.

Functional Specification
Functional specifications are based on the flow chart, what has to happen in order to make the end result a reality. The development team will determine in details what, how and when. Based on programming languages involved and platforms, it is preferred to begin with the platform/language that is most common to your team.

Your team should:

• Detail about what the application actually does
  
• Detail the function of each control on every screen as well as “core functionality” that is required.
  
• Database structure
  
• Ability to read or write external text files
  
• Dynamic updates
  
• Information form website
  
• Common functions like help and quit should be included into custom functions so they can be written once and called as many times as necessary.
  
• 
  

Script
Scripts are provided by the content managers, preferably before the development of the flow chart. Depending on the application a script might be necessary. The scripts are used just like movie scripts. They determine which information is displayed onscreen if any, they also determine dialog for interaction. This pertains to the role of the Content Manager. Without final script, there will in an internal debate about final product. If your application is content dependent please be sure to obtain final copy of the content before implementing prototype.

Graphic Design
The graphic design of an application defines the “look” of an application, the developers and the designers will communicate to ensure a positive usability. It is the most immediate way of conveying visual messages to the user.

Consider the following in the creation of a graphic design:

• Background and control panels
  
• Color
  
• Textures
  
• Types - Titles, Text, Images
  
• Containers for types
  
• “White” spaces
  
• Alignment & positioning.
  

Interface Design
Developers and Designers must work together to make it all work uniformly. The interface is the main means of interactions between the user and the application. Most interface functions can be broken down into one of three categories:

• getting information from the user
  
• returning information to the user
  
• initiating action
  

For user input, text fields and buttons are most frequently used. Returning information to the user occurs in a variety of ways, text fields, audio feed back and/or graphics. The button is the common form of interface component.

The most important aspect of an interface design is the ability to get the application to do what he/she wants. Interface designers must be careful of the assumptions they make regarding the user’s level of understanding. If the system is too complex, a help system must be integrated into the design. A good interface should be able to operable without additional instructions, even if a help system is needed to explain the functionality of the application.

Prototype
Developers this is a must prototypes are considered to be betas and alphas versions of the of the final product. Prototypes are versions of an application created to test various aspects of a design before final production. You can categorize prototypes into two categories:

• Interface prototypes - Allows designers to test the way users respond to the interface in terms of clarity, consistency, navigation and ease of use. This also enables designers to test various methods of performing the same activity to determine which method is best.
  
  
• Functional prototypes - Build and test certain features without the overhead of the complete program. This simplifies the process of creating and debugging new features or controls. The scripts from the prototypes contain event handlers that can then be integrated into the complete application with minor modification.
  

Test and debug prototypes as often as possible, revise and retest again.

Final Implementation
Developers and designers should use feedback from prototype testing, make any necessary modifications to the applications design and build it. Test the program depending on your level of quality control. If errors or problems are found they can be address and a new version can be built and tested again. This cycle can is often repeated until an acceptable level of quality is achieved and the final version can be deployed and/or delivered.

Hope this will clear up some gray areas for you and if you wish please let me know if I may have missed anything.

Thank you,
Albert Rosa