From my personal experience, I can say for sure that Zephyr
is the perfect test management system having all the above
mentioned features. You can check for more details in Zephyr
2.5.

Try www.getzephyr.com

It is best if u say "according to company nome's"

Ask as per your current CTC comparing with company norms and u may nogotiate with that

All Techniques which are included in Black box

Testing techniques is the apporach used for testing the 
software.It can be divided in to static and dynamic testing.

static testing is done without executing the software by 
conducting peer reviews, formal reviews and inspection.

Dynamic testing is done by executing the s/w to ensure the 
functionality is working fine and it meets the expectations 
of customers.

Dynamic testing further divided into three types
1.black box or specification based or functionality based 
or behavioral testing
under black box testing we have 
a.Boundary value analysis
b.equivalence partioning
c.decison table testing
d.state transtion testing
e.use case testing

2.White box testing or structual based or glass box testing
a.statement coverage
b.condition coverage
c.decision coverage

3.Experience based testing
a.exploratory testing
b.error guesing

If he is from IT background then it is easy .... give him
some documents related QA process and methodologies. so that
he will be familiar with the terminology

I will train the people by Pictorial Pesentation for better 
understanding

Sanity test we do to verify the new build. Its least 
required to write test cases for sanity but if u want then 
it will be very basic like pages are navigating properly 
after filling form value you are able to submmit 
successfully. In this test we dont verify the output

hi , It would be more appropriate if you say smoke testing 
also, see once the product is prepared or on initaial 
stages we write testcases for each module
(FUNCTIONAL/SAnity) is covered in that case,
then comes after the product prepared we have to test its 
daily report on Smoke asis as well as regression asis
so the answer will be SMOKEand REGRESSIOn test cases

Firstly we do not write sanity test cases. Apart from
Functional test cases we write System test cases,
integration test cases

The terms 32-bit and 64-bit refer to the way a computer's
processor (also called a CPU), handles information. The
64-bit version of Windows handles large amounts of random
access memory (RAM) more effectively than a 32-bit system

1.Open System by clicking the Start button, clicking Control
Panel, clicking System and Maintenance, and then clicking
System.
2.Under System, you can view the system type.

Testing team needs all the documents to be bundled and released.

In case of Black Box testing, tester will get the idea by
reading all those documents then he/she can start the testing.

Testing - meaning application testing starts after the 
first build arrives. At project kickoff stage, there is 
info avaliable on the product concept and some 
functionalities of the product. At project kickoff the 
product, the methodology, project monitoring and control, 
and build management is dicussed. Subsequent to this QA 
analyses the product and technology requirements and 
identifies the resources to test. QA then draws up a 
preliminary QA effort estimate. As more information becomes 
available, it is analysed and reveiwed by QA and the QA 
estimate is updated.

If any bug got fix and that bug is not directly affecting 
your component but we need to do testing(Eg: product is 
divided into 4 modules and in one module a bug got fixed 
(eg a audio codec got fixed)but you are not seperatly 
testing for audio in your module, but you test audio play 
back in your module then your component/module is buddy for 
that)

Deferred is the term used when developer fix the defect it
in next release.

Deferred situation arises in following cases.
1. When developer thinks that the defect is valid but this
change may affect the existing one.
2. When development team and testing team have an argument.
3. The first build is on high priority due to that this
defect will be moved with next build.That s why defect is
deferred.

Deffered: The bug or the functionality which is expected 
will be fined in the future build, that means it is 
postponed....

This happens due to the following reasons

1) Testers report the bug, the Developer asks for further 
requirement which the tester can't provide at that 
situation, so the bug which the tester reported will be 
deffered.

2) In another scenario, where the developer is convienced 
that this is a valid bug , but in the current realse or 
build that will not be of more important what the client is 
expecting , so the development team and the testing team 
will decide and deffer it..

3) In another scenario, if there is misunderstiding between 
the developer and the tester, what ever bug the tester 
proudces , the developer will not listen or give important 
and he will work on different bugs... so at this time also 
the bug can be deffered..