- Web application development
Web application development is the process and practice of developing
web applications Fact|date=February 2007.
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 security,
software bugs, etc. are major issues. If time to market, or technical complexity is a concern, documentation, test planning, change control, requirements analysis, architectural description and formal design and construction practices can mitigate risk.
Time to market, company-growth and requirements churn, three things that are emphasized in web-based business, coincide with the principles of the Agile practices. Some agile lifecycle models are:
Feature Driven Development
Web applications undergo the same unit, integration and
system testingas traditional desktop applications. But because web application clients vary so greatly, teams might perform some additional testing, such as:
Many types of tests are automatable. At the component level, one of the
xUnitpackages can be a helpful tool. Or an organization can create its own unit testing framework. At the GUI level, Watiror iMacrosare useful.
In the case of
ASP.NET, a developer can use Microsoft Visual Studioto write code. But, as with most other programming languages, he/she can also use a text editor. Notepad++is an example.
PHP, the Zend Development Environmentprovides numerous debuggingtools and provides a rich feature set to make a PHPdeveloper's life easier.
code generationtools such as dbQwikSiteare available to automate the development of code. Using such tools, non-technical users can produce working code, and experienced coders can accelerate the development cycle.
Frameworks and Reuse
code reuseand using web application frameworks can greatly improve both productivity and time to market(McConnell 1996:537). Reusing externally developed components can allow an organization to reap the above benefits, while potentially saving money. However, for smaller components, it might be just as easy to develop your own components as it would be to learn new APIs. Also, if a component is essential to the business, an organization might want to control its development.
List of Web based applications
Web application framework
*cite book | last = McConnell | first = Steve | authorlink = Steve McConnell | title = Code Complete, Second Edition | publisher = Microsoft Press | date = June 2004 | pages = 960 | id = ISBN 0-7356-1967-0
*cite book | last = McConnell | first = Steve | authorlink = Steve McConnell | title = Rapid Development | publisher = Microsoft Press | date = July 2, 1996 | pages = 680 | id = ISBN 1-55615-900-5
*cite book | last = Rozanski | first = Nick | coauthors = Eóin Woods | title = Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives | publisher = Addison-Wesley Professional | date = April 20, 2005 | pages = 576 | id = ISBN 0-321-11229-6
*cite book | last = Leffingwell | first = Dean | coauthors = Don Widrig | title = Managing Software Requirements: A Use Case Approach, Second Edition | publisher = Addison-Wesley Professional | date = May 16, 2003 | pages = 544 | id = ISBN 0-321-12247-X
*cite book | last = Whittaker | first = James A. | coauthors = Mike Andrews | title = How to Break Web Software: Functional and Security Testing of Web Applications and Web Services | publisher = Addison-Wesley Professional | date = February 2, 2006 | pages = 240 | id = ISBN 0-321-36944-0
Wikimedia Foundation. 2010.