Web application development: Difference between revisions

Revision as of 14:24, 27 May 2007

Revision as of 15:57, 2 June 2007

Line 4:

'''Web application development''' is the process and practice of developing [[web application]]s {{Fact|date=February 2007}}.

==FormalityRisk==

Just as with a traditional desktop application, web applications have varying levels of risk. A personal home page mightis requiremuch less formalityrisky than, for example, a stock trading web site. AtFor thesome formal end of the spectrumprojects [[Computer security|security]], [[software bug]]s, etc. are major issues. DependingIf ontime formalityto market, lifecycleor activitiestechnical cancomplexity rangeis anywherea from no planning at allconcern, to formal [[Software documentation|documentation]], [[test plan]]ning, [[change control]], [[requirements analysis]], [[software architecture|architectural description]], and formal design and construction practices. can mitigate risk.

How formal the project is affects virtually every activity throughout the life of the project. More formality means more overhead. But larger projects require more planning and attention to detail. (McConnell 2004:657)

A personal home page might require less formality than, for example, a stock trading web site. At the formal end of the spectrum [[Computer security|security]], [[software bug]]s, etc. are major issues. Depending on formality, lifecycle activities can range anywhere from no planning at all, to formal [[Software documentation|documentation]], [[test plan]]ning, [[change control]], [[requirements analysis]], [[software architecture|architectural description]], design and construction practices.

==Technologies==