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.
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!
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 6 
