Return a combined list of City and its Zipcode as showable 
text on the list box. Place the list on the UpdatePanel 
with a trigger on change event of the State list box.

In the background... ( change event of the state box) do 
the data access, clear the city box and re-fill the box 
with selected State which is obtained from the EventArgs of 
the event handler.

Singleton design pattern is a a creational pattern to 
dictate how and when objects get created and it's main 
purpose is to ensure that a class has only one instance

Example:
#define NULL 0

class Singleton
{
private:
	Singleton(Singleton&){}
	Singleton& operator =(Singleton&);
	int nValue;
	static Singleton* pSingleton;
	Singleton():nValue(10)
	{
	}
public:
	static Singleton*Instance()
	{

		if(NULL == pSingleton)
		{
			pSingleton = new Singleton();
		}
		return pSingleton;
	}
	void setValue(int val)
	{
		nValue = val;
	}
	int getValue()
	{
		return nValue;
	}
};
Singleton* Singleton::pSingleton = NULL;

int main(int argc, char* argv[])
{
	Singleton *abc = NULL;
	cout<<Singleton::Instance()->getValue()<<endl;
	Singleton::Instance()->setValue(20);

	Singleton *xyz = NULL;
	cout<<xyz->Instance()->getValue()<<endl;
	Singleton *sss = Singleton::Instance();
	return 0;
}

MUM is best

MVC Architecture,disign pattern is best

what's proof of concept?

for preparing POCs, proof of concept.

Prototyping is the part of feasibility analysis phase of
SDLC. An simulated prototype of the target system is created
which gives the initial feel of the target system. This also
helps in pre-analyzing the behavior of the target system.

While analyzing and designing a system, we take into
consideration the flexibility, scalability, performance,
maintainability and testability.  When these capabilities
are not taken into consideration, we see a high probability
for system failure.  Conversely, if too much of analysis and
design goes into building a system, we see similar symptoms
of failure.  Considerable skill and practice goes into
building successful systems.  It is worth to note that only
20% or less of the software projects ever succeed.

Software development life cycle is a waterfall methodology,
it is a small to medium database software projects are 
generally broken down into six stages,project planning, 
requirements definition, design development, integration 
test, installation acceptance.....

SDLC is a methology in which covers all aspects of 
operations
It consists of 
Requirements Management.
System Analysis.
Design 
Coding
Testing
Support and Maintenance.
Post Audit.

SDLC is a complete proccess of analysis which includes 
feasiblity study,designing which includes conceptual 
desining&logical designing,coding,testing,implementation 
and then maintainaince.

SDLC for any project will have five phase
Initiation
Planning
Execution
Monitoring and control
Closing

Each phase will have various steps like project initiation
will start from project charter that is original 
confirmation of starting of the project and comes 
preparation of preliminary project scope statement, Scope 
planning, scope identification, creating wbs and wbs 
dictionary, scope verfication, scope control, time like 
duration and schedule of activities, estimation of project 
activities, definition of quality of project, defining 
communication ways and methods, acquiring resources, 
project integraton etc.,
these are general project managment process.
In case SDLC type of Water fall method, XP  and agile 
methodology, phase of project management project may vary 
for industry to industry like construction company will 
have different phase with that of manufacturing.
Project life cycle will be same for all project management 
life cycle or SDLC

design patterns are answers to the repetitive problems
encountered.

They help in communicating to other developers as they have
common language and nomenclature.

design patterns are above any language. They should be at
least same when u took all OO languages and may be separate
for non oo languages.

They are many of them.They mainly are categorized into 

1.Creational - Patterns used while creating an object.
2.Strucural - Patterns used when constructing objects, using
other small objects.
3.Behavioural - Useful in how the objects interact with each
other.

restart

Try to identify the problem..... button may fail because of 
various reasons like...
1) It is not ON yet.
2) Technical problem in that button.

We should create a solution space for the above scenarios.

For case-1) Try to switch it ON.If its not gettion ON 
still, may be bcoz of no charge in battery. So charge / 
change the cell and switch it ON.
For case-2) Assume your button 2 is not working, use button 
3 and then press -1 to get the result.

check for empty password it should fail.
check for all alphabetic password it should fail
check for all numeric password it should fail
check for all special character password it should fail
check for all mixed password it should suceed.

Data Access Layer which is receive a request from buisness 
object layer and speaks to database , get the result and 
return to buisness object.

All sqls and Stored procedure execution will be placed.

Hi... Data access layer is nothing but EIS(Enterprise 
Information Server)which can store the databse objects 
associated to the webapplication.

Data Access Layer or DAL in an application is the layer which 
takes care of interaction with database. In DAL , generally 
Insert, Update and Delete Queries are written. DAL sits 
between database and the Business layer.

DAL is a class which you can for talking to database. In 
this case you do not need to worry about creating DB 
connection, destroy db objects, connection pooling. 
Everything is handled by DAL for you. You only need to 
create class derived from DAL and define sored procedures 
and classes for storing result from stored procedures.

This is very convenient way of talking to DB.

Hi... Model is nothing but a class/bean having the setters 
and getters methods to providing the required information 
to the controller(SERVLET) and View(JSP).First the client 
will give the request by using the view(jsp),the view can 
forward the data to controller(servlet)then the controler 
process the request based on the Model components .Finally 
the servlet send the response to view.

If we will take in DotNet technology. Web based applications
has implemented MVC Pattern.

ASPX is the View Class
ASPX.CS is the controller class
If we are using any Application Blocks / DAL Components that
are model class.

View is Client side pages. Model is over underlying 
database. controlers are nothing but delegates that 
watching what ever view holds as data.
once, data changes in data model thru client pages or thru 
any other call. then, controller will initimate to view 
related to that changes and UI controls will reflect the 
changes accordingly.

Hi...
MODEL:Model is nothing but storing the databse objects.
VIEW: View is nothing but userinterface
CONTROLLER: Controller is nothing but handling the requests 
and sending the response.

MVC - is using for separation the business logic and
application data from the presentation data to the user.
MODLE :-Here we put all kind of business logic and methods
for data manipulation(CURD).
VIEW :- it is user interface here user can make request.
it is build by using(html, css, js, etc).
CONTROLLER :- it used for controlling and validating request
and response. it decides where to send the request whether
back to view as a response or send it ot model. Controller
make communication between model and view.

Hi... For this question u can answer like Singleton design 
pattern ,DAO and DTO,MVC.

The design pattern is broadly classified into 
1. Creational (Factory, Abstract Factory, Singleton 
Prototype, and Builder)
2. Structural (Composite)
3. Behavioural (Observer)

What is desing pattern?
  Commonly accepted solution for a particular problem is 
called design pattern.
We can classify the design patterns into two.
1. Java core patterns.
2. J2ee Design patters.

Core patterns.
1) Creational (Factory pattern, singleton pattern....etc)
2) Structural (Adaptor, Composite... etc)
3) Behavioural(Command, Template, Strategy... etc)

Entepise Patterns. (We can catagoize by layer)
1) Business Facade - Business Layer
2) Business Interface - Business Layer
3) DAO pattern - Persistent Layer
4) Composite View - Presentation Layer
5) synchronized - Presentation Layer
6) Service Locator... etc...

It is mainly divided into 3 types

1) creational
2) structural
3) Behavioral

It can also be divided into class and Object

            Creational       Structural          Behavioral


Class                         Adapter (Class)     Template

Object                        Adapter(Object)     Iterator
             Builder                              State
             Factory                             Strategy
                                                  Command
                                                  Mediator
                                                  Observer