Software Methodology

This blog can make you understand the process of software :
Crystal Methodology
http://weblogs.java.net/blog/chet/archive/2008/01/crystal_methodo.html

How to Generate a Thread Dump For a Java Process

press Ctrl-Break in the terminal console you used to start the JVM
send the QUIT signal to the Java VM running the application
kill -QUIT process_id
process_id is the process number of the respective java process

Using keyword expansion in CVS

One rather nice feature of cvs is the ability to use keyword expansion (or keyword substitution), this allows for rather nice tracking of stats within the file itself.
One example of using the ID tag can be demonstrated like this:
$Id: keywords.html,v 1.11 2008/03/28 04:37:40 erhanyi Exp $
All that cvs requires is that you insert: $Id: $ all on one line. During the commit process, that keyword is automatically expanded to fill out the proper information.

Keyword options
$Author: erhanyi $
$CVSHeader$
$Date: 2005/07/29 19:41:45 $
$Header: /home/cvs/keyword_list.html,v 1.7 2005/07/29 19:41:45 willn Exp $
$Id: keyword_list.html,v 1.7 2005/07/29 19:41:45 erhanyi Exp $
$Name: $
$Locker: $
$RCSfile: keyword_list.html,v $
$Revision: 1.7 $
$Source: /home/cvs/keyword_list.html,v $
$State: Exp $$Log: keyword_list.html,v $

Importing into Oracle

I need to export from user 'A' in a production database and import to a user 'B' in a development database with a different tablespace. Do you have very detailed step-by-step procedure?

This is a pretty common procedure, which isn't too hard to accomplish. So here is a step-by-step guide.
Export the entire schema from production:
exp userid=system file=user_a.dmp log=user_a.log owner=a

FTP the dump file (in BINARY mode) to the development server.
Make sure user B exists in your development instance.

Run this command:
imp userid=system file=user_a.dmp log=imp.log fromuser=a touser=b

The only big sticking point is that user B may have a different default tablespace than user A, if user A exists. If this is the case, and user B has been granted the CONNECT role, then user B's tables will be created in user A's default tablespace. To stop this, make sure that user B has the correct default tablespace and make sure that you revoke UNLIMITED TABLESPACE from user B.