Coding Methodology - Discussion

We need four documents that are interrelated.

1. The Variable dictionary - Lists out the main variables we use.

2. Program flow diagram - This lists out the complete lists of all of the programs/Modules and how they interconnect on a macro level.

3. Procedure dictionary - We keep here the lists of all procedures and their inputs and outputs.

4. Testing Q/A Methodology Process -

5. Standards Definitions: Naming conventions - Commenting standards,

6. Visualization Flow - screen layout of display results/instances.

1. This starts us off with a fundamental design question: Is Starium XCV to be written in a procedural or object-oriented language. Php supports both approaches.

2. This may go without saying, but the visualization flow needs to incorporate reports and internal emails generated by the code.

In practical use, we will use a hybrid approach. This is the difference between theory and application.

We will employ both the DRY and KISS theories, "Don't Repeat Yourself" and "Keep it Simple Stupid".

However, I doubt that we will need to get into inheritance and class structures.

We have already bypassed much of the need for that with how the data is set up.

For standards in terms of PHP, it will be procedural. However, I expect that we will use approaches that eliminate redundancy.

My take is that our coding does not have to be the most elegant, but rather focus on functionality and speed and getting it done.