Folder Hierarchy

The following folder hierarchy is recommended for your project. You will have to customise it according to your project need. All folders will be present in SVN under project specific repository.
In the below sample you will find main project name and under which you have project divided into multiple phases. Your project need not have phases.

Use dev/QA/prod directory structure for managing the development, testing and release/deployment to customer for acceptance.

1. Development is active in dev branch by developers. Developers label the build for QA and then copy it to QA.
2. Testing is active in QA branch by QA. QA files bugs against the build label in bugzilla. Developers fix the same in dev branch. Qa verifies the fixed bugs in next release from developers.
3. Customer gets copy from prod branch. He can file bugs against the release and/or provide feedback. Then cycle 1-2-3 starts again.
4. Any issue that come against a build in QA/prod are marked and logged in bugzilla against a label of build.

The following hierarchy is recommended for SVN

1. Trunks - Mainline of development. Touched by developers and unit testers.
2. Branches - Created on need basis for major feature, changes, QA or for intermediate deliveries.
3. Tags - A snapshot of deliverable to customer. Untouched and unchanged. Only for reference. Created by QA just before delivery to customers.

Projectname
|_
Phase 2[if required your project can have phases]
|_
Docs
|_
Design
|_
For Review
|_
DesignDocumentv0.2.doc
|_
DesignDocumentv1.0.doc
|_
Requirements
|_
Reviews
|_
DesignDocumentReviewChecklist.doc
CodeReviewChecklist.doc
|_
Dev
|_
Code
|_
Build
QA
|_
Code
|_
Build
Release
|_
Code
|_
Build

Project Management
|_
UseCaseTracking.doc
|_
ProjectTracking.doc