|
#REDIRECT [[Web application#Development]]
{{Howto|date=September 2009}}
{{Cleanup-rewrite|unnecessary details|date=February 2016}}
'''Web application development''' is the process and practice of developing [[web application]]s.
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.
==Technologies==
* [[AJAX (programming)|Ajax]]
* [[Active Server Pages|ASP]]
* [[ASP.NET]]
* [[ActionScript]]
* [[Cascading Style Sheets|CSS]]
* [[ColdFusion]]
* [[Common Gateway Interface|CGI]]
* [[HTML5|HTML]]
* [[Java (programming language)|Java]]
* [[JavaScript]]
*
* [[LANSA (development environment)|Visual LANSA]]
* [[Lasso (programming language)|Lasso]]
* [[Node.js]]
* [[OSGi|OSGI]]
* [[Perl]]
* [[PHP]]
* PSGI
* [[Python (programming language)|Python]]
* [[Ruby (programming language)|Ruby]]
* [[Xojo]]
* [[WordPress]]
* [[Yii]]
==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 software development|Agile]] practices. Some agile lifecycle models are:
* [[Extreme programming]]
* [[Scrum (development)|Scrum]]
* [[Timeboxing|Timebox]] development
* [[Feature-driven development]]
==Testing==
Web applications undergo the same [[Unit testing|unit]], [[Integration testing|integration]] and [[system testing]] as traditional desktop applications. But because web application clients vary so greatly, teams might perform some additional testing, such as:
* Security
* [[Software performance testing|Performance]], [[Load testing|Load]], and [[Stress testing|Stress]]
* [[HTML]]/[[Cascading Style Sheets|CSS]] validation
* [[Web accessibility|Accessibility]]
* [[Usability testing|Usability]]
* [[Cross-browser]]
Many types of tests are [[Test automation|automatable]]. At the [[Component test|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]] or [[iMacros]] are useful.
==Tools==
In the case of [[ASP.NET]], developers can use [[Microsoft Visual Studio]] to write code. But, as with most other programming languages, they can also use a text editor ([[Notepad++]] for example). [[WebORB Integration Server]] for .NET can be used to integrate .NET services, data and media with any web client. It includes developer-productivity tools and APIs for remoting, messaging and data management.
For [[ColdFusion]] and the related open-source CFML engines, there are several tools available for writing code. These include Adobe [[Dreamweaver]] CS4, the [[CFEclipse]] plugin for [[Eclipse (software)]] and Adobe CF Builder. One can also use any text editor, such as [[Notepad++]] or [[TextEdit]].
Many tools support the [[Java (programming language) | Java programming language]]. The most popular include [[Apache Tomcat]], [[GlassFish]], [[JDeveloper]] and [[NetBeans|Netbeans]], but there are numerous others.
For [[PHP]], the [[Zend Development Environment]] provides numerous [[debugging]] tools and provides a rich feature-set to make [[PHP]] development easier. [[WebORB Integration Server]] for PHP can be used to integrate PHP classes and data with any web client. It includes developer productivity tools and APIs for remoting, messaging and data management. Tools such as [[Hammerkit]] abstract [[PHP]] into a visual programming environment and utilise [[Component-based software engineering|component-based software]] methods to accelerate development.
Other tools include Caribou,<ref>
{{cite web
| url = https://caribou.github.io/caribou/docs/what-is-caribou.html
| title = What is Caribou?
| website = let-caribou-in
| publisher = github
| access-date = 2017-04-18
| quote = Caribou is a dynamic web application ecosystem for crafting production ready web inhabitants with minimal effort.
}}
</ref>
various [[Web browser|browsers]], [[File Transfer Protocol|FTP clients]], etc. See [[:Category:Web development software]].
{{Expand section|date=May 2008}}
==Frameworks and use==
{{Main|Web application framework}}
Practicing [[code reuse]] and using [[web application framework]]s can greatly improve both productivity and [[time to market]] (McConnell 1996:537). Reusing externally developed [[Software componentry|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 [[Application programming interface|API]]s. Also, if a component is essential to the business, an organization might want to control its development.
==See also==
{{Portal|Software Testing}}
*[[Device Independence]]
*[[List of Web based applications|List of Web-based applications]]
*[[Web Interoperability]]
*[[Web application framework]]
==References==
*{{cite book | last = McConnell | first = Steve | authorlink = Steve McConnell |
title = Code Complete, Second Edition | publisher = Microsoft Press | date = June 2004 | isbn = 0-7356-1967-0 |
page = 960 }}
*{{cite book | last = McConnell | first = Steve | authorlink = Steve McConnell |
title = Rapid Development | publisher = Microsoft Press | date = July 2, 1996 | isbn = 1-55615-900-5 |
page = 680 }}
*{{cite book | last = Rozanski | first = Nick |author2=Eóin Woods |
title = Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives | publisher = Addison-Wesley Professional | date = April 20, 2005 | isbn = 0-321-11229-6 |
page = 576 }}
*{{cite book | last = Leffingwell | first = Dean |author2=Don Widrig |
title = Managing Software Requirements: A Use Case Approach, Second Edition |
publisher = Addison-Wesley Professional | date = May 16, 2003 |
isbn = 0-321-12247-X | page = 544 }}
;Notes
<references />
==Further reading==
*{{cite book | last = Whittaker | first = James A. |author2=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 | isbn = 0-321-36944-0 |
page = 240 }}
{{DEFAULTSORT:Web Application Development}}
[[Category:Web applications]]
[[Category:Web development]]
| 