Web application development: Difference between revisions

Revision as of 18:30, 29 October 2006

Revision as of 23:33, 14 December 2006

Line 7:

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_documentationSoftware documentation|documentation]], [[test plan]]ning, [[change control]], [[requirements analysis]], [[software architecture|architectural description]], design and construction practices.

==Technologies==

Line 44:

* [[Performance Engineering|Performance]] (download speed)

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

==Tools==

Line 71:

*{{cite book | last = McConnell | first = Steve | authorlink = Steve McConnell |

title = Code Complete, Second Edition | publisher = Microsoft Press | date = June 2004 |

pages = 960 | id = ISBN 07356196700-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 15561590051-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 03211122960-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 032112247X0-321-12247-X }}

==Further reading==

*{{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 03213694400-321-36944-0 }}

[[Category:Web applications]]