Practices
  Home arrow Practices arrow The Art Of Software Development (part ...
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
IBM Developerworks
 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? 
PRACTICES

The Art Of Software Development (part 4): Delivering Quality
By: icarus, (c) Melonfire
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 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:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb 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

    TestComplete™ automates software testing for a fraction of what the big guys charge. Easy functional and load testing for all Windows, .NET, Java and Web apps. Download a free trial now.

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

    If you've been following along, you now know all about the first threephases of a software development project: requirements analysis,software design and implementation. But in case you thought your jobended with the completion of the code, think again - you've still got away to go before you can call it a wrap.

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

    More Practices Articles
    More By icarus, (c) Melonfire


     

       

    PRACTICES ARTICLES

    - 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
    - Choosing the Right Team
    - Trees
    - Basic Array Searching in C++
    - Solving Problems with Recursion




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 1 hosted by Hostway