Unit 3

Q.1 Explain ADL Descriptive Model Framework.

Ans:
A software architecture describes the structure and behavior of a software system and
the non-software entities the system interfaces with. In a software architecture, a
system is represented as a set of software components, their connections, and their
important behavioral interactions. Creating a software architecture promotes better
understanding of the system, thus aiding the design process. It also provides a basis
for rigorous analysis of the system design, making possible the early detection of
design errors and flaws that lead to improvements in software quality and help ensure
correctness.

An architectural description language (ADL) is used to describe a software

architecture. An ADL may be a formal or semi-formal descriptive language, a
graphics language, or include both. The advantage of using an ADL lies in the ability
to rigorously specify an architecture so that it can be analyzed. An ADL may have
associated with it a set of tools for doing useful analysis of architectures specified in
the language. In recent years, there has been a considerable amount of research into
developing ADLs.

Important Properties of ADL

• Composition – composition of independent components and connections
• Abstraction – need to describe design elements clearly and explicitly
• Reusability – ability to reuse components, connectors in different architectural
descriptions
• Configuration – ability to understand and change the architectural structure
• Heterogeneity – ability to combine multiple, heterogeneous architectural
descriptions
• Analysis - possible to perform rich and varied analysis of architectural
description
• The positives
• ADLs represent a formal way of representing architecture
• ADLs are intended to be both human and machine readable
• ADLs support describing a system at a higher level than previously
possible
• ADLs permit analysis of architectures – completeness, consistency,
ambiguity, and performance
• ADLs can support automatic generation of software systems
• The negatives
• There is not universal agreement on what ADLs should represent,
particularly as regards the behavior of the architecture
• Representations currently in use are relatively difficult to parse and are
not supported by commercial tools
 • Most ADL work today has been undertaken with academic rather than
commercial goals in mind

Q.2 Describe ADLs and their relationship to other languages.

Ans; Architecture Description Language (ADL) is defined as "a language (graphical,
textual, or both) for describing a software system in terms of its architectural elements
and the relationship among them".

In other words, ADL is a language enabling formalization, description, specification,

modeling and reasoning on software architectures. Each of these features should be
fulfilled by a language that is proclaimed to be ADL. A good ADL must provide
abstractions that are adequate for modeling a large system. Each ADL embodies a
particular approach to the specification and evolution of architecture.

Q.3 Illustrate the working of Struts and Hibernate web framework.

Ans: Struts is used to create a web applications based on servlet and JSP. Struts
depend on the MVC (Model View Controller) framework. Struts application is a
genuine web application. Struts are thoroughly useful in building J2EE (Java 2
Platform, Enterprise Edition) applications because struts takes advantage of J2EE
design patterns. Struts follows these J2EE design patterns including MVC.
Working of Struts:

In the initialization phase, the controller rectify a configuration file and used it to
deploy other control layer objects. Struts configuration is form by these objects
combined together. The struts configuration defines among other things the action
mappings for an application.
Struts controller servlet considers the action mappings and routes the HTTP requests
to other components in the framework. Request is first delivered to an action and
then to JSP. The mapping helps the controller to change HTTP requests into
application actions. The action objects can handle the request from and responds to
the client (generally a web browser). Action objects have access to the applications
controller servlet and also access to the servlet’s methods. When delivering the
control, an action objects can indirectly forward one or more share objects,
including javabeans by establish them in the typical situation shared by java servlets.

Hibernate: Hibernate is a framework which is used to develop persistence logic

which is independent of Database software. In JDBC to develop persistence logic
we deal with primitive types. Whereas Hibernate framework we use Objects to
develop persistence logic which are independent of database software.
Flow of working during operation in Hibernate Framework :
Suppose We want to insert an Object to the database. Here Object is nothing but
persistence logic which we write on java program and create an object of that
program. If we want to insert that object in the database or we want to retrieve the
object from the database. Now the question is that how hibernate save the Object to
the database or retrieve the object from the database. There are several layers
through which Hibernate framework go to achieve the above task. Let us
understathe nd the layers/flow of Hibernate framework during performing
operations:
Q.4 llustrate distributed transaction processing with JDBC.
Ans: In distributed java enterprise application, transaction is processed by Transaction
Manager. Transaction manager is the primary component of distributed transaction
infrastructure. The transaction manager is responsible for cordinating transaction
among multiple resources of the application, and it also provides the additional low
level services to process the transaction across the multiple resource manager. An
application server uses the transaction manager to perform transaction across the
multiple resource manager. The transaction manager is responsible for committing
transaction or roll back transaction. It also manages the transaction across multiple
resource manager and supports propagation of transaction across distributed system. It
supports XA Transaction management contract with resource manager. The resource
manager supports two type of transaction -
1. JTA/XA Transaction- The transaction manager that coordinates and controls to
those transaction which is external to the resource manager, is referred as JTA or XA
transaction.
2. RM or Local transaction- The transaction manager that coordinates and controls
to those transaction which is internal to the resource manager, is referred as RM or
Local Transaction.
 Distributed Transaction in java EE
In the above diagram the client call the EJS A and this EJB A access the resources
managed by EIA and also calls the EJB B to access EIB B. A Resource
manager supports XA transaction management contract with resource manager. The
XA transaction interface is used manage transaction across the resource manager. At
first the application sends a transaction request to transaction manager. A transaction
is a single logical unit, there can be many transaction branches on the transaction
managet.
Q. 5 Describe CORBA Reference Model Architecture.
Ans: Common Object Request Broker Architecture (CORBA) could be a
specification of a regular design for middleware. It is a client-server software
development model.
Using a CORBA implementation, a shopper will transparently invoke a way on a
server object, which may air a similar machine or across a network. The middleware
takes the decision, associated is to blame for finding an object which will implement
the request, passing it the parameters, invoking its methodology, and returning the
results of the invocation. The shopper doesn’t need to remember of wherever the
item is found, its programming language, its software package or the other aspects
that don’t seem to be a part of the associated object’s interface.
CORBA Reference Model:
The CORBA reference model known as Object Management design (OMA) is
shown below figure. The OMA is itself a specification (actually, a group of
connected specifications) that defines a broad vary of services for building
distributed client-server applications. several services one may expect to search out
in a very middleware product like CORBA (e.g., naming, dealings, and
asynchronous event management services) are literally fixed as services within the
OMA

Different parts communicate victimization ORB. ORB is additionally referred to as

the item bus. An associate example of the application interface is a distributed
document facility. In a very domain interface, it will have domain dependent
services, for instance, producing domain.
Object interface has some domain freelance services:
1. Naming Service:
Naming service is additionally known as a white page service. victimization
naming service server-name will be searched and it’s location or address pointed
out.

2. Trading Service:
Commercialism service is additionally known as a yellow page service.
victimization commercialism service a selected service will be searched. this is
often corresponding to looking out a service like an automobile store in a very
yellow page directory.