|
Based on the Model 2 implementation of the Model-View-Controller
(MVC) design
pattern, the UIX framework encourages application architectures
to define a clear separation between presentation and application
logic.
UIX provides the View and Controller portions of an application
while making it easy to connect the presentation layer to any
standard data access technology such as Enterprise JavaBeans.
This architecture enables each member of a web application development
team to focus on their area of expertise. For example, web page
authors can concentrate on designing the presentation layer while
application developers who write the application code can focus
on business logic, data access, and event handling.
Using UIX to build web applications enables you to divide development
tasks among three types of developers:
- UI designers/developers—Create the View. Output is UIX
pages for the front-end of an application.
- Model developers—Create the Model independently of the
View and Controller. Output is Java classes for the back-end
of an application.
- Controller developers—Make the View and Model work together
by adding data manipulating, event handling, and workflow pieces
to the UIX pages.
In real life, however, there is often an overlap of roles in
any application development team. For instance, some developers
may work on both the View and Controller layers. How you divide
the tasks among your application team members is entirely up to
you.
|
Bookmark
