1. Waterfall
2. RUP (Iterative)
3. eXtreame Programming (Agile)
4. some others like Sprial, V-Shape etc.

also include RAD model in the above answer

1.waterefall model
2.prototyping model
3.iterative enhancement model
4.RAD model
5.spiral model
6.component based devlopment model(cbd model)
7.time boxing model e.t.c

waterefall model
2.prototyping model
3.iterative enhancement model
4.RAD model
5.spiral model
6.component based devlopment model(cbd model)
7.time boxing model e.t.c
8.MVC Model

2 types
1)inner join ,
2)outer join
  a)left outer
  b)right outer
  c)full outer

sql-server

inner join
outer join
left outer join
right outer join
full outer join
cross join


oracle sql

inner join
outer join
left outer join
right outer join
full outer join
cross join
natural join

IN ORACLE 9i.

Equi - Join = Both are same Names only different
                simple join 
                inner join 
                Natural join 
                join

Non - Equi Join

Outer Join 
                Left outer join
                Right outer joi
                Full outer join

Self join
Cartesian Product

CLR stands for Common Language Runtime. It's the runtime 
environment of .Net Framework. It has one component called 
JIT or JITTER (Just in time translator) which is 
responsible for translating code from MSIL To Native code 
on the fly.

The scene is like this on source machine
Any .net------> CLR-> MSIL Code
compliant code
On Detination MAchine
MSIL Code --> CLR(JIT)----> NAtive code--> os

1.	Native Support for Developing Mobile Web Applications 
2.	Enable Execution of Windows Forms Assemblies Originating
from the Internet
Assemblies originating from the Internet zone?for example,
Microsoft Windows? Forms controls embedded in an
Internet-based Web page or Windows Forms assemblies hosted
on an Internet Web server and loaded either through the Web
browser or programmatically using the
System.Reflection.Assembly.LoadFrom() method?now receive
sufficient permission to execute in a semi-trusted manner.
Default security policy has been changed so that assemblies
assigned by the common language runtime (CLR) to the
Internet zone code group now receive the constrained
permissions associated with the Internet permission set. In
the .NET Framework 1.0 Service Pack 1 and Service Pack 2,
such applications received the permissions associated with
the Nothing permission set and could not execute. 
3.	Enable Code Access Security for ASP.NET Applications
Systems administrators can now use code access security to
further lock down the permissions granted to ASP.NET Web
applications and Web services. Although the operating system
account under which an application runs imposes security
restrictions on the application, the code access security
system of the CLR can enforce additional restrictions on
selected application resources based on policies specified
by systems administrators. You can use this feature in a
shared server environment (such as an Internet service
provider (ISP) hosting multiple Web applications on one
server) to isolate separate applications from one another,
as well as with stand-alone servers where you want
applications to run with the minimum necessary privileges. 
4.	Native Support for Communicating with ODBC and Oracle
Databases 
5.	Unified Programming Model for Smart Client Application
Development
The Microsoft .NET Compact Framework brings the CLR, Windows
Forms controls, and other .NET Framework features to small
devices. The .NET Compact Framework supports a large subset
of the .NET Framework class library optimized for small
devices. 
6.	Support for IPv6
The .NET Framework 1.1 supports the emerging update to the
Internet Protocol, commonly referred to as IP version 6, or
simply IPv6. This protocol is designed to significantly
increase the address space used to identify communication
endpoints in the Internet to accommodate its ongoing growth. 

UDDI --Universal Description, Discovery and Integration.

A WSDL port describes the interfaces (legal operations) 
exposed by a web service.

Web Services Description Language

The following link provides the sequence of steps with
examples.: 

http://my.execpc.com/~gopalan/dotnet/classic_com/com.net_interop.html

we can sent and receive soap msg with the help of HTTP, FTP 
or SMTP protocols. we need to bind the soap envelope in 
protocol and then we can send and receive our msg over the 
netwok.

SOAP, the Simple Object Access Protocol, is an evolving W3C
standard developed by representatives of IBM, Microsoft,
DevelopMentor, and UserLand Software for the exchange of
information over a network. As more SOAP servers become
publicly available on the Web, SOAP is doing for programs
written in nearly any language -- even short little programs
written in popular, simple languages like Visual Basic,
JavaScript, and perl -- what HTML does for Web browsers: It
gives them a simple way to take advantage of an increasing
number of information sources becoming available over the Web.

Like HTML, SOAP provides a set of tags to indicate the roles
of different pieces of information being sent over the Web
using the HTTP transport protocol (and since SOAP 1.1, SMTP
as well). SOAP, however, gives you much more power than
HTML. With SOAP, your program sends a "SOAP request" (a
short XML document that describes a method to invoke on a
remote machine and any parameters to pass to it) to a SOAP
server. The SOAP server will try to execute that method with
those parameters and send a SOAP response back to your
program. The response is either the result of the execution
or the appropriate error message. Public SOAP servers are
available to provide stock prices, the latest currency
conversion rates, FedEx package tracking information,
solutions to algebraic expressions, and all kinds of
information to any SOAP client that asks.

Before SOAP existed, programs trying to use this kind of
information had to pull down Web pages and "scrape" the HTML
to look for the appropriate text. A visual redesign of those
Web pages (for example, putting the current stock price in a
table's third column instead of its second column) was all
it took to render these programs useless. The SOAP spec,
along with its brief accompanying schemas for SOAP requests
and responses, provides the framework for a contract between
clients and servers that creates a foundation for much more
robust information-gathering tools.

Stateless -SAO(Client activated object(using single call
,singleton)
stateful  -CAO(Cliend use proxy server to send to the server)
by
suresh s

stateless--->It dosen't keep data in memory
if state means session expires data will not update to 
backend
statefull----->vis-vers of stateless

- Discovery file is generated, which contains the 
information about the Web Service and references used.
- A Client XML Code is generated which will be helpfull to 
invoke Web service's methods.

A Proxy Class will be generated. When we add webreference 
of webservice.
After that we can communicate with Proxy Class in order to 
communicate with WebService