Web Site Development

A system development development can follow a number of principles or partnership definite frameworks, methodologies, modeling tools and languages. Let us see the steps involve in any web site development. 1. Analysis: Once a client is started discussing his requirements, the team gets into it, towards the preliminary requirement analysis. As the web site is going to be a part of a system, it needs a complete analysis as, how the web site or the web based application is going to benefit the present system and how the site is going to facilitate the business. Moreover the analysis should cover all the aspects. The first substantial item is finding the targeted audience. Then, all the present hardware, software, general public and data should be considered during the lifetime of analysis. The analysis should be done in the way, that it may not be further period consuming or with very less informative. The team should be able to come up with the complete cost-benefit a
nalysis and as the plan for the project will be an output of analysis, it should be realistic. To achieve this analyst should consult the designers, developers and testers to come up with a realistic plan. 2. Specification Building: Preliminary specifications are drawn up by covering up each and every element of the requirement. For example if the product is a web site then the modules of the site including usual layout, site navigation and dynamic parts of the site should be included in the spec. Larger projects will require further levels of consultation to assess additional business and technical requirements. After reviewing and approving the preliminary document, a written proposal is prepared, outlining the scope of the project including responsibilities, timelines and costs. 3. Design and development: After building the specification, labour on the web site is scheduled upon receipt of the signed proposal, a deposit, and any written content materials and grap
hics you wish to include. Here normally the layouts and navigation will be designed as a sample. There can be a group of suggestions and changes from the client side, and all the changes should be freezed before moving into the later phase. The revisions could be redisplayed via the web for the customer to view. Throughout the design phase the team should develop research plans and procedures for quality assurance. It is necessary to obtain client approval on design and project plans. In parallel the Database team will sit and understand the requirements and develop the database with all the data structures and sample data will also be prepared. 4. Content writing: This phase is necessary mainly for the web sites. There are professional content developers who can compose industry specific and relevant content for the site. Content writers to add their contents can utilize the design templates. The grammatical and spelling check should be over in this phase. 5. Coding: Strai
ghtaway its programmers turn to add his code without disturbing the design. Unlike traditional design the developer must know the interface and the code should not disturb the gaze and feel of the site or application. So the developer should understand the design and navigation. If the site is dynamic then the code should utilize the template. The developer may call for to interact with the designer, in order to understand the design. The designer may necessitate to develop some graphic buttons when ever the developer is in need, largely while using some form buttons. If a team of developers is working they should manipulate a CVS to control their sources. Coding team should generate necessary testing plans as well as technical documentation. For example Java users can application JavaDoc to develop their documents to understand their code flow. The end-user documentation can also be prepared by the coding team, which can be used by a technical writer who can understand t
hem, writes helps and manuals later. Full text: http://computerandtechnologies.com/web-hosting/news_2008-09-25-15-30-05-519.html