Wednesday, 14 November 2012

Starting a Web Project

You're about to start a new web project. Say your skill level is nearly zero, you have never developed any web project before, so this article is definitely going to help you in getting your job done quite nicely. This piece contains basically guidelines for naïve developers, what to do and how to if you intend to develop a web project. I thought to write it down to help decrease the problems new developers face when they embark on such projects, like I had to face doing my very first web project.

The very first thing you need is to ‘plan and organize' whatever you want to develop. The better you understand your web project, the easier your life would be during development phase. The requirements (SRS) must be explicitly defined and well-understood before starting the development. Choose the programming language of your choice (i.e. PHP, Asp.Net, etc). Choose the corresponding tool i.e. Dreamweaver, Visual Studio, etc. (I shall recommend to use the latest versions of whatever tool you choose, that may bring flexibility in your programming and to have maximum help/support from their online forums as well). During planning phase, decide on the pages and its contents you need to include, make lists, understanding the process flow may help in this phase. During this phase, you'll also need to decide on the web design for your project and for that; you'll need to have a good knowledge about CSS, jQuery, etc.

After that, the database structure is the next very important phase. You need to carefully decide on the tables and their inter-relations for correct data flow during different processes initiated by the project.

Once you have decided your project, understood clearly the process flow and have a clear picture of whole system in your mind, now is the right time to start development (coding). Remember to organize your pages (files) in appropriate directories i.e. admin files and user files should not be mixed, should be saved in different, clearly-named directories. It's always a better practice to sort out common data for example header and footer section, side menus or navigation menu bars, or stuff like that, save them in separate files and include them wherever needed. This will make you feel comfortable focusing on the actual process done on each individual site page.

Once you have developed the whole project, or a module/section of it, you will need to test it. Inline-testing is another better practice to follow during development. This may help you sort-out cross-browser compatibility issues timely.

I hope the above writing may help new developers i.e. students and internees like myself. The discrepancies found are welcomed to be corrected, also all comments and editions are welcomed. Happy Coding..!!!!