Practices
  Home arrow Practices arrow The Art Of Software Development (part 4): Delivering Quality
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
VPS Hosting  
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid  
Request Media Kit
Contact Us  
Site Map  
Privacy Policy  
Support  
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
Google.com  
PRACTICES

The Art Of Software Development (part 4): Delivering Quality
By: icarus, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 4
    2002-09-24


    Table of Contents:
  • The Art Of Software Development (part 4): Delivering Quality
  • Code To Zero
  • Casing The Joint
  • A Man With A Plan
  • Bug-bustin'
  • The Write Stuff
  • Endgame

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article

     
     
    ADVERTISEMENT


    The Art Of Software Development (part 4): Delivering Quality
    ( Page 1 of 7 )

    Just writing code isn't enough - you also need to test it thoroughly before you release it to a customer. This article discusses the testing phase of the software development cycle, providing you with an overview of test cases and testing processes, together with a discussion of how to go about documenting your software in a clear and concise user manual.If you've been following along, you now know all about the first three phases of a software development project: requirements analysis, software design and implementation. But in case you thought your job ended with the completion of the code, think again - you've still got a way to go before you can call it a wrap.

    In this fourth article of a five-part series, I'm going to be spending some time discussing what happens *after* you've finished writing the code that meets your customer's requirements. I'll be discussing the various types of testing your code must go through, providing you with a brief overview of how test cases should be prepared and software problems should be reported, and explaining how software is released to a customer. I'll also be discussing that bane of developers everywhere - documentation - with some tips and tricks that might make the process more painless. So let's get started.

     
     
    >>> More Practices Articles          >>> More By icarus, (c) Melonfire
     

       

    PRACTICES ARTICLES

    - More Techniques for Finding Things
    - Finding Things
    - Finishing the System`s Outlines
    - The System in So Many Words
    - Basic Data Types and Calculations
    - What`s the Address? Pointers
    - Design with ArgoUML
    - Pragmatic Guidelines: Diagrams That Work
    - Five-Step UML: OOAD for Short Attention Span...
    - Five-Step UML: OOAD for Short Attention Span...
    - Introducing UML: Object-Oriented Analysis an...
    - Class and Object Diagrams
    - Class Relationships
    - Classes
    - Basic Ideas





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 3 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek