100% found this document useful (2 votes)
6K views

ISO Main Folder Structure

The document outlines an ISO folder structure for organizing project documents. It specifies a main project folder containing subfolders for code, documents, and third party controls. The code folder further divides code by development stage. The documents folder structures documentation by project initiation, requirements, design, development, testing, release, closure, reports, customer feedback, and correspondence. Specific documents needed for each stage are listed. A third party controls folder stores tools supplied by clients.

Uploaded by

Arthie Viswa
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC or read online on Scribd
100% found this document useful (2 votes)
6K views

ISO Main Folder Structure

The document outlines an ISO folder structure for organizing project documents. It specifies a main project folder containing subfolders for code, documents, and third party controls. The code folder further divides code by development stage. The documents folder structures documentation by project initiation, requirements, design, development, testing, release, closure, reports, customer feedback, and correspondence. Specific documents needed for each stage are listed. A third party controls folder stores tools supplied by clients.

Uploaded by

Arthie Viswa
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC or read online on Scribd
You are on page 1/ 5

ISO FOLDER STRUCTURE

ISO MAIN FOLDER STRUCTURE

Project Name Folder

1. Code 2. Document 3. Third Party

1. CODE FOLDER STRUCTURE:

Database Backup

Development

Production
CODE

Release

UAT

BY ARTHIE Page 1
ISO FOLDER STRUCTURE

2. DOCUMENTS FOLDER STRUCTURE:

DOCUMENTS
FOLDER

1. Project 3.
Design 4.
Developmen

2. 8.
5.
Requirement Reports
Testing 10.
Correspondence
6. 9. Customer
7.
Release Feedback
Closure

1. Documents Needed for Document Folder:

1. PROJECT INITIATION:

 Work Signed Order

 Project Kick-off Checklist

 Project Team Member List

 Project Phase Planning

 Project Task Allocation

 Risk Assessment and Identification Checklist

 Project Management Plan Document

 Project Metrics

 Review Checklist for PMP

BY ARTHIE Page 2
ISO FOLDER STRUCTURE

2. REQUIREMETNS:

 Requirements from Client End

 Chat Folder – chat with clients to be saved

 System Requirement Specification Document

 Review Checklist for SRS

 Requirement Traceability Matrix

3. DESIGN:

 High Level Design Document

 Low Level Design Document

 Review Checklist for High and Low Level Design Document

 Database Design Document

4. DEVELOPMENT:

 Code Review Checklist

 Coding Guidelines Document(either from Client end or Company’s)

5. TESTING:

 Project Test Plan Document

 Test Scenario

 Test Case

 Test Script

 Test Data

 Review checklist for TS, TC, TD and Test Script

BY ARTHIE Page 3
ISO FOLDER STRUCTURE

 Test Summary Report

 Bug Report Summary (if Bug tracker presents then no need of this
document).

6. RELEASE:

 Mile Stone Document

 Phase Review Checklist

 Release Committee Meeting Checklist

 Release Notes

7. Closure:

 Closure Meeting checklist

8. REPORTS:

 Minutes of Meeting checklist

 Status Report

 Learning and Improvement

 Configuration Audit checklist

 Activity Handover Form

 CAR Reports

 Root Cause Analysis Checklist

 Tool Evaluation Form

9. CUSTOMER FEEDBACK:

Customer Feedback Form

BY ARTHIE Page 4
ISO FOLDER STRUCTURE

10. CORRESPONDENCE:

 All Official Mails will stored here(Internal and External)

3. THIRD PARTY CONTROLS:

 The Tools that are supplied by the Client will be stored.

BY ARTHIE Page 5

You might also like