Web application development: Difference between revisions

Revision as of 01:55, 29 January 2021

Revision as of 20:06, 1 February 2021

Line 1:

{{Howto|date=September 2009}}

{{Cleanup rewrite|unnecessary details|date=February 2016}}

'''Web application development''' is the process and practice of developing web applications. There is a consensus that the processes involved are extensions of standard software engineering processes.<ref name=":0">{{Cite book|title=Interactive Whiteboards for Education: Theory, research, and practice|lastlast1=Thomas|firstfirst1=Michael|last2=Schmid|first2=Euline|publisher=IGI Global|year=2009|isbn=9781605669823|___location=Hershey, PA|pages=1700}}</ref> Considering this, along with its unique characteristics, popular frameworks used include the spiral approach and business-oriented approach to application development, among other models that address the requirements for an iterative process.<ref name=":0" />

Just as with a traditional desktop application, web applications have varying levels of risk. A personal home page is much less risky than, for example, a stock trading web site. For some projects [[Computer security|security]], [[software bug]]s, etc. are major issues. If time to market or technical complexity is a concern, [[Software documentation|documentation]], [[test plan]]ning, [[change control]], [[requirements analysis]], [[software architecture|architectural description]] and formal design and construction practices can mitigate risk.

Line 11:

==Testing==

Web applications undergo the same [[Unit testing|unit]], [[Integration testing|integration]] and [[system testing]] as traditional desktop applications. It has the same goals, which involve: 1) the determination that the application is working correctly; and, 2) the identification of errors that need correction. The testing process of web applications, however, has some special characteristics, making it a little different from a test used for a software. These include the fact that web applications tend to have a great deal of information that could contain mistakes, omissions, incorrect labels, redundancy, and so on.<ref name=":1">{{Cite book|title=Web Based Application Development|last=Grove|first=Ralph|publisher=Jones & Bartlett Learning|year=2009|isbn=0763759406978-0763759407|___location=Boston|pages=218}}</ref> They can also entail multiple layers of web applications and multiple, dynamic configurations.<ref name=":1" /> Testing and finding errors, therefore, involves more complex process such as the inclusion of operational analysis for each layer or configuration.

Web application clients vary greatly, hence teams might perform some additional testing, such as: