3.30 am in the morning..

it's 3 am, after doing some fixes on the project. the updates..
- Started Main page UI
- Done the expanded Chat room

Spent almost 8hours researching on
- Flash VOIP using Adobe Flash 10, Adobe Air and Flex
(plans are aborted, as there are few setbacks in cost, and time)
- RTMFP (Real Time Media Flow Protocol)
- Voice conversion Codec, RED5, etc..
- Researched on DBML system in VSWD for SQL schema markup
- Fixed Reserved words issue in SQL using identifier delimiter (\")
- Fixed Default enter button on asp.net (declare default on html sided)
- Tested some Web.config

My researches on Code Walkthrough

• Waived: Code walkthrough is waived due to a very simple algorithm change (or configuration file), and not in a critical point in the code.
• Informal: Code is presented to the reviewer who simply reviews it "on-the-spot". This is reserved for simple, confined, and non-critical changes.
• Formal: Code is presented to the reviewer and the reviewer examines the code and algorithms for proper style, format, and technique. This is reserved for complex code changes of a critical nature and those changes that may impact multiple subsystems.

Code walkthrough is to ensure that the requirements are met, coding is sound, and all associated documents complete. The 5 major sector of code walkthrough which includes.. Design, Coding, Documentation, Test Plan and Released Notes to ensure program completeness and readibility.

Code is reviewed for the following:

• Clarity and Readability
  
• Requirements Met
  
• Performance
  
• Algorithms and Error Situations

User documentation, if appropriate, is examined for:

• Existance, for the functionality implemented.
• Clarity and Readability
• Completness

Researches done on:
http://www-md.fsl.noaa.gov/eft/developer/CodeWalkthroughGuidelines.html


I have decided to use a program called debutsetup from NCH Software. It is free and highly suitable to record our presentation of our project.