1. SOFTWARE QUALITY IN WEB DEVELOPMENT Adam Westerman Caio Balthazar Daniel Schepers

2. BACKGROUND

3. WHAT DOES SOFTWARE QUALITY MEAN IN WEB DEVELOPMENT  Software satisfies client requirements  System can run on many browsers and platforms

4. THE IMPORTANT QUALITY ATTRIBUTES IN WEB DEVELOPMENT

5. PROCESSES USED TO GUARANTEE QUALITY  Site maps  A graph of which page connects to which  Provides a visible representation of the system  Can get complex very quickly. See example of Wikipedia’s home page below:

6.  Grayscreen prototyping  Many projects cannot be seen until clients until late stages of development  To allow client to give feedback early on, use a simple HTML prototype  More effective than site maps and flow charts

7. MECHANISMS USED TO GUARANTEE QUALITY  For behind-the-scenes logic and database testing, use unit testing frameworks based on xUnit  JUnit, PyUnit, DBUnit, etc.  To simulate user interface, use a web browser automation tool such as IRobotSoft, Sahi, or Selenium.

8. WHAT METRICS ARE USED  Common metrics include:  Mean age of closed problems  Cost / earned value  Responsiveness  Maximum Capacity  Customer Satisfaction  Page Views/ Day  Top Search Engines  Top Key Words

9. SUGGESTED PROCESSES/MECHANISMS

10. SUGGESTES METRICS

11. EXAMPLES OF SOFTWARE DEVELOPMENT SUCCESSES AND FAILURES

12. STANDARDS/REGULATIONS THAT ARE IN USE

13. COMMON PROBLEMS ASSOCIATED WITH QUALITY ASSURANCE IN WEB DEV

14. QUESTIONS

15. REFERENCES