Professional Web developement

Web application development
From Wikipedia, the free encyclopedia
• Have questions? Find out how to ask questions and get answers. •
Jump to: navigation, search
This article or section contains instructions, advice, or how-to content.
The purpose of Wikipedia is to present facts, not to teach subject matter.
Please help improve this article by removing or rewriting the how-to content, which may qualify for a move to Wikibooks.

Web application development is the process and practice of developing web applications [citation needed].
Contents
[hide]

* 1 Risk
* 2 Technologies
* 3 Lifecycle Model
* 4 Testing
* 5 Tools
* 6 Frameworks and Reuse
* 7 See also
* 8 References
* 9 Further reading

[edit] Risk

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.

[edit] Technologies

* Ajax
* ASP
* ASP.NET
* CSS
* ColdFusion
* Java EE
* JavaScript
* Perl
* PHP
* Ruby, including Ruby on Rails
* CGI
* ISAPI/NSAPI

[edit] Lifecycle Model

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:

* Extreme Programming
* Scrum
* Timebox development
* Feature Driven Development

[edit] Testing

Like traditional desktop applications, web applications undergo the same unit, integration and system testing. But because web application clients vary so greatly, teams might perform some additional testing, such as:

* Security
* Performance, Load, and Stress
* HTML/CSS validation
* Accessibility
* Usability

Many types of tests are automatable. At the component level, one of the xUnit packages can be a helpful tool. Or an organization can create its own unit testing framework. At the GUI level, Watir is useful.

[edit] Tools

In the case of ASP.NET, a developer can use Microsoft Visual Studio to write code. But, as with most other programming languages, he/she can also use a text editor. Notepad++ is an example.

For PHP, the Zend Development Environment provides numerous debugging tools and provides a rich feature set to make a PHP developer's life easier.

Several code generation tools such as dbQwikSite are 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.

Other tools include various browsers, FTP clients, etc.
This short section requires expansion.

[edit] Frameworks and Reuse

Main article: Web application framework

Practicing code reuse and 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.

[edit] See also

* Device Independence
* List of Web based applications
* Search engine optimization
* Web Interoperability
* Web application framework

[edit] References

* McConnell, Steve (June 2004). Code Complete, Second Edition. Microsoft Press, 960. ISBN 0-7356-1967-0.
* McConnell, Steve (July 2, 1996). Rapid Development. Microsoft Press, 680. ISBN 1-55615-900-5.
* Rozanski, Nick; Eóin Woods (April 20, 2005). Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives. Addison-Wesley Professional, 576. ISBN 0-321-11229-6.
* Leffingwell, Dean; Don Widrig (May 16, 2003). Managing Software Requirements: A Use Case Approach, Second Edition. Addison-Wesley Professional, 544. ISBN 0-321-12247-X.

[edit] Further reading

* Whittaker, James A.; Mike Andrews (February 2, 2006). How to Break Web Software: Functional and Security Testing of Web Applications and Web Services. Addison-Wesley Professional, 240. ISBN 0-321-36944-0.

Retrieved from "http://en.wikipedia.org/wiki/Web_application_development"

Categories: Articles containing how-to sections | All articles with unsourced statements | Articles with unsourced statements since February 2007 | Articles with sections needing expansion | Web applications | World Wide Web | Web development
Views

* Article
* Discussion
* Edit this page
* History

Personal tools

* Sign in / create account

Navigation

* Main page
* Contents
* Featured content
* Current events
* Random article

interaction

* About Wikipedia
* Community portal
* Recent changes
* Contact Wikipedia
* Donate to Wikipedia
* Help

Search

Toolbox

* What links here
* Related changes
* Upload file
* Special pages
* Printable version
* Permanent link
* Cite this article

Powered by MediaWiki
Wikimedia Foundation

* This page was last modified 18:36, 21 August 2007.
* All text is available under the terms of the GNU Free Documentation License. (See Copyrights for details.)
Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a U.S. registered 501(c)(3) tax-deductible nonprofit charity.
* Privacy policy
* About Wikipedia
* Disclaimers

Make a donation to Wikipedia and give the gift of knowledge!