Obviously. It doesn't mean that a project or product which 
has no CMM Certification wil not work fine. It is a 
recognization like a designation in our work environment.

this is depend up on personal alligations.
suppose if i work for consultencie up to now, for getting 
stability in my carrier i will looking for change.

change is the spice of life.if u don't change ur 
ideas,feelings,& attitude with respect to time then u will 
be stangnant in course of time.change in professionalism is 
not bad,it aquaints u with new environment and new work 
culture,new peoples and gain of knowledge.so everytime 
change is not bad.

My skills are not properly utilised at there so that i have 
least of chance to proof myself

Change is need for human lives why because it gives new 
energy.It provides us to perform our skills in a proper way.
It is a chance for improving our skills & it is stage for 
learning new things.

For better opportunity, Growth and future perspective.

yes..

(why?)

as i m not carrying any tag of MRP..

as far is workload is negotiable.

as far is workload is negotiable. as per your company 
policies then only you may decided.

I am really interested in doing here @ (name of
organization) than I am in the size of initial offer.

Hi, Appraisal process is depend upon company to company. 
But this process is accept evry company. this process is:
1. Establish performance standard
2. Communicate with standard
3. Measure the actual performance
4. Compare the performance with standard and discuss the 
appraisal
5. Taking corrective action.

Please ask atleast 30 days

ORACLE

Check whether it is possible or not. Provide reasons why it
is not possible.

Team management requires few skill like communication 
skill, control the imotions of employees towards 
organisational goals, most important try to understand 
whats in the mind of employees and also other personnel who 
are related to organisation and control them. I have all 
these skills.

I communicate with team members by mouth..!

I communicate with team members thru Mail like Outlook

by verbal comunication

i will communicate by mobile

Communicate with team members for all updates through mail 
and weekly meeting.

I always use to communicate with my team members over 
mails......that is safe and proof also...........

Effective communication is not about sending across a 
message from a sender to a receiver. It demands more. A 
personal and good rapport between team members should give 
fruitful results in this regard. I will try to develop a 
good rapport with my colleagues in an informal way; that is 
outside the office. This personal relationship will help us 
to send our ideas or concerns freely among ourselves.

i accept mythilis ans

how will i communicate to my team members, it's depend on 
the conditions, like if we sit together then, we'll talk 
face to face, if we're far, then by mobile or mails. we 
should consider the matter of confidentiality.

there  many modela for software development.
some of them is mentioned below:


Software Development Life Cycle Models

1>The General Model:

Software life cycle models describe phases of the software
cycle and the order in which those phases are executed. 
There are tons of models, and many companies adopt their
own, but all have very similar patterns.  The general, basic
model is shown below:
General Life Cycle ModelGeneralModel

Each phase produces deliverables required by the next phase
in the life cycle.  Requirements are translated into design.
 Code is produced during implementation that is driven by
the design.  Testing verifies the deliverable of the
implementation phase against requirements.

Requirements

Business requirements are gathered in this phase.  This
phase is the main focus of the project managers and stake
holders.  Meetings with managers, stake holders and users
are held in order to determine the requirements.  Who is
going to use the system?  How will they use the system? 
What data should be input into the system?  What data should
be output by the system?  These are general questions that
get answered during a requirements gathering phase.  This
produces a nice big list of functionality that the system
should provide, which describes functions the system should
perform, business logic that processes data, what data is
stored and used by the system, and how the user interface
should work.  The overall result is the system as a whole
and how it performs, not how it is actually going to do it.

Design

The software system design is produced from the results of
the requirements phase.  Architects have the ball in their
court during this phase and this is the phase in which their
focus lies.  This is where the details on how the system
will work is produced.  Architecture, including hardware and
software, communication, software design (UML is produced
here) are all part of the deliverables of a design phase.

Implementation

Code is produced from the deliverables of the design phase
during implementation, and this is the longest phase of the
software development life cycle.  For a developer, this is
the main focus of the life cycle because this is where the
code is produced.  Implementation my overlap with both the
design and testing phases.  Many tools exists (CASE tools)
to actually automate the production of code using
information gathered and produced during the design phase.

Testing

During testing, the implementation is tested against the
requirements to make sure that the product is actually
solving the needs addressed and gathered during the
requirements phase.  Unit tests and system/acceptance tests
are done during this phase.  Unit tests act on a specific
component of the system, while system tests act on the
system as a whole.

So in a nutshell, that is a very basic overview of the
general software development life cycle model.  Now lets
delve into some of the traditional and widely used variations.

 

2>Waterfall Model:

This is the most common and classic of life cycle models,
also referred to as a linear-sequential life cycle model. 
It is very simple to understand and use.  In a waterfall
model, each phase must be completed in its entirety before
the next phase can begin.  At the end of each phase, a
review takes place to determine if the project is on the
right path and whether or not to continue or discard the
project.  Unlike what I mentioned in the general model,
phases do not overlap in a waterfall model.
Waterfall Life Cycle ModelWaterFallModel

Advantages

    * Simple and easy to use.
    * Easy to manage due to the rigidity of the model ? each
phase has specific deliverables and a review process.
    * Phases are processed and completed one at a time.
    * Works well for smaller projects where requirements are
very well understood.

Disadvantages

    * Adjusting scope during the life cycle can kill a project
    * No working software is produced until late during the
life cycle.
    * High amounts of risk and uncertainty.
    * Poor model for complex and object-oriented projects.
    * Poor model for long and ongoing projects.
    * Poor model where requirements are at a moderate to
high risk of changing.

 

3>V-Shaped Model

Just like the waterfall model, the V-Shaped life cycle is a
sequential path of execution of processes.  Each phase must
be completed before the next phase begins.  Testing is
emphasized in this model more so than the waterfall model
though.  The testing procedures are developed early in the
life cycle before any coding is done, during each of the
phases preceding implementation.

Requirements begin the life cycle model just like the
waterfall model.  Before development is started, a system
test plan is created.  The test plan focuses on meeting the
functionality specified in the requirements gathering.

The high-level design phase focuses on system architecture
and design.  An integration test plan is created in this
phase as well in order to test the pieces of the software
systems ability to work together.

The low-level design phase is where the actual software
components are designed, and unit tests are created in this
phase as well.

The implementation phase is, again, where all coding takes
place.  Once coding is complete, the path of execution
continues up the right side of the V where the test plans
developed earlier are now put to use.
V-Shaped Life Cycle ModelVShapedModel

Advantages

    * Simple and easy to use.
    * Each phase has specific deliverables.
    * Higher chance of success over the waterfall model due
to the development of test plans early on during the life cycle.
    * Works well for small projects where requirements are
easily understood.

Disadvantages

    * Very rigid, like the waterfall model.
    * Little flexibility and adjusting scope is difficult
and expensive.
    * Software is developed during the implementation phase,
so no early prototypes of the software are produced.
    * Model doesn?t provide a clear path for problems found
during testing phases.

 

4>Incremental Model

The incremental model is an intuitive approach to the
waterfall model.  Multiple development cycles take place
here, making the life cycle a ?multi-waterfall? cycle. 
Cycles are divided up into smaller, more easily managed
iterations.  Each iteration passes through the requirements,
design, implementation and testing phases.

A working version of software is produced during the first
iteration, so you have working software early on during the
software life cycle.  Subsequent iterations build on the
initial software produced during the first iteration.
Incremental Life Cycle ModelSpiralModel

Advantages

    * Generates working software quickly and early during
the software life cycle.
    * More flexible ? less costly to change scope and
requirements.
    * Easier to test and debug during a smaller iteration.
    * Easier to manage risk because risky pieces are
identified and handled during its iteration.
    * Each iteration is an easily managed milestone.

Disadvantages

    * Each phase of an iteration is rigid and do not overlap
each other.
    * Problems may arise pertaining to system architecture
because not all requirements are gathered up front for the
entire software life cycle.

 

5>Spiral Model

The spiral model is similar to the incremental model, with
more emphases placed on risk analysis.  The spiral model has
four phases: Planning, Risk Analysis, Engineering and
Evaluation.  A software project repeatedly passes through
these phases in iterations (called Spirals in this model). 
The baseline spiral, starting in the planning phase,
requirements are gathered and risk is assessed.  Each
subsequent spirals builds on the baseline spiral.

Requirements are gathered during the planning phase.  In the
risk analysis phase, a process is undertaken to identify
risk and alternate solutions.  A prototype is produced at
the end of the risk analysis phase.

Software is produced in the engineering phase, along with
testing at the end of the phase.  The evaluation phase
allows the customer to evaluate the output of the project to
date before the project continues to the next spiral.

In the spiral model, the angular component represents
progress, and the radius of the spiral represents cost.

Spiral Life Cycle ModelSpiralModel

Advantages

    * High amount of risk analysis
    * Good for large and mission-critical projects.
    * Software is produced early in the software life cycle.

Disadvantages

    * Can be a costly model to use.
    * Risk analysis requires highly specific expertise.
    * Project?s success is highly dependent on the risk
analysis phase.
    * Doesn?t work well for smaller projects.