Endgame - Practices

Wondering why your software projects are always late, buggyand over budget? Well, this might come as a surprise to you, butprofessional software development involves a lot more than just writingcode. Over the course of this five-part tutorial on software developmentprocesses and practices, find out what you've been missing, and how youcan streamline your development to be more efficient and effective. Thisintroductory article discusses the analysis and documentation ofcustomer requirements.

TABLE OF CONTENTS:

By: icarus, (c) Melonfire

Poor Best

Rating:

/ 6

August 28, 2002

print this article

SEARCH DEV SHED

TOOLS YOU CAN USE

With the delivery of the requirements document, the corresponding commercial proposal, the proposed project schedule and associated documents, it's time to sit back and wait for a sign-off from your customer.

What do you do once that happens? Start designing the application, of course...not to mention writing a couple more documents. But you don't need to worry about that right now - I'll be covering all that in the second part of this article, which discusses how to put together a software development plan, develop and document a good architecture for your software, build a user interface prototype and create an acceptance test plan.

Till then...be good!

Note: Examples are illustrative only, and are not meant for a production environment. Melonfire provides no warranties or support for the source code described in this article. YMMV!