EP Project Directory structure

August 2nd, 2006

I suggest using following directory structure for every project:

Project Name\

Backup\ -- directory for backups

Analyst\ -- models archived, with timestamping

Databases\ -- all Contributor applications dbs + pad,common

Databases\ -- it's sometimes good to store db's in the same place

Documentation\ -- model related documents

Access Tables\ -- whether you are using some mechanism for creating access tables (VBA +Excel is a miracle cure), or just store them in txt files - it's the place

Elist and Users\ -- excel files for each contributor app, with following worksheets: elist, users, rights. Required for moving applications to another environments

Translations\ -- multilingual model? export it all here, it'll save you from troubles later

Technical Requirements\ -- documents, describing created model, interview protocols and such

\Model -- Analyst libraries

\Analyst library Name

\Contributor Application Name

\exp -- an _exp library for contributor application. See more on imp,skl,exp
\imp -- an _imp library for contributor application.

\skl -- skeleton library

\Scripts -- automation

\Bat Files -- good old bat's for all gtp'ing and so on

\Logs

\Contrib Macros and Links -- export

RSS feed | Trackback URI

Comments »

No comments yet.

Name (required)
E-mail (required - never shown publicly)
URI
Your Comment (smaller size | larger size)
You may use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> in your comment.

Trackback responses to this post