Up next in 10
UML - Unified approach and layered architecture
Show More Show Less View Video Transcript
0:00
unified approach and layered
0:02
architecture it is a very important
0:05
concept the unified approach UA is based
0:09
on the methodologies of butch Romberg
0:13
and Jacobsen it combines the best
0:16
practices and processes and guidelines
0:18
along with the object management group
0:21
so that is an OMG and unified modeling
0:25
language UML so that is our unified
0:29
approach and layered architecture so in
0:32
case of unified approach processes and
0:34
here we are having the second column
0:36
head is unified approach of
0:39
methodologies and technology so if you
0:42
go for the process like use case driven
0:44
development in case of methodologies
0:48
we'll be having that UML that is the
0:50
unified modeling language in case of
0:52
eBay processes that is object oriented
0:54
analysis so a here you can go for the
0:57
layered architecture which which we'll
0:59
be discussing in our next slides next
1:02
one is the object oriented design and
1:04
here we are having object oriented
1:06
repository for object oriented system
1:09
development patterns and the respective
1:11
frameworks next next one is incremental
1:14
development prototyping and continuous
1:16
testing here we are having the component
1:19
based development that is CPD so on the
1:23
left column we are having the UA
1:24
processes on the right hand side we're
1:26
having the UF methodologies and the
1:29
respective technologies to be used now
1:32
let us go for the layered architecture
1:34
for the better understanding so the
1:36
layered approach of UA is followed in
1:39
client-server application development
1:41
environment that tend to lean towards
1:45
the entire architecture we know that in
1:47
case of client-server architecture the
1:49
server is containing the full version of
1:51
the database at the client machine some
1:54
software's are running and those
1:55
software's are having some user
1:56
interface with the help of which the
1:59
users will be interacting and requests
2:01
will be going to the server and then a
2:04
responses will be coming from the server
2:06
after being processed at the server end
2:08
the corresponding response will be
2:11
coming from the
2:12
to the client machine so that is our
2:14
client-server environment in short in a
2:17
nutshell we can describe it in this way
2:19
so here in case of layered architecture
2:21
here we are considering the three layers
2:24
in this layered approach the first one
2:27
is the access layer so what is the main
2:29
purpose of this access layer there is
2:31
access storage and the respective
2:34
storage retrieval and then business
2:36
layer which is holding the business
2:38
logic business constraints and the
2:41
queries and then we are having the view
2:43
layer where this user will be
2:45
interacting containing the user
2:47
interface so here we are having this
2:50
database server and here we are having
2:52
this user or the client so now we are
2:55
having three layers are there so in the
2:57
in the first layer we are having this a
2:59
there is object-oriented analysis and
3:02
that is a view layer and in the second
3:04
layer we are having this Oh a an
3:06
application web application or web
3:08
server here we can containing the
3:10
business layer containing the different
3:13
constraints rules and regulations and
3:15
queries and this is our object-oriented
3:18
design and prototyping here we are
3:20
considering this access layer which will
3:23
be having the inner protocol the enough
3:25
protocol to have that database storage
3:28
retrieval and accessing so in this way
3:31
we have mentioned the three layers and
3:33
in this diagrams the three layers have
3:35
got displayed here so here we are having
3:38
this database so RB internet and etc
3:41
here you are having this access layer
3:43
which will be interacting with this
3:44
database for the fruitful and efficient
3:47
database storage and retrieval operation
3:49
and this business layer will be holding
3:51
the different business logic the
3:54
business constraints and the queries and
3:57
this is a view layer with with which the
3:59
client or the user will be interacting
4:01
some in some interface will be provided
4:04
so that they will feel a very convenient
4:06
way to interact with the system
4:10
so here you will be having the access
4:13
objects then we are having this Business
4:16
Objects and here we are having this view
4:18
objects so this view objects will be
4:20
made available to the client or the user
4:22
this access objects will be will be
4:25
there to having the access over the
4:27
database storage and retrieval and this
4:30
Business Objects will be holding the
4:32
business logic the constraints and their
4:34
respective queries so this is the three
4:37
layered our approach in case of layered
4:39
architecture
4:40
so using this proper diagrams we have
4:42
discussed what is the unified approach
4:44
and what is a layered architecture in
4:48
the next videos will be going for more
4:50
detailing on them please watch all of
4:53
them so that you can have a good
4:54
conception over this unified approach
4:57
and this layered architecture thanks for
5:00
watching this video
#Programming
#Java (Programming Language)
#Software
#Business & Productivity Software
#Software Utilities
#Educational Software