V Enterprise Architectural overview

V object oriented software development for enterprise

V Component Based software development for enterprise.
Java Enterprise System. Enterprise Data
V Basis of JDBC ² interfaces -drivers.
V Advanced JDBC features.
An enterprise architecture (EA) is a rigorous description of the structure
of an enterprise, which comprise enterprise components (business
entities), the externally visible properties of those components, and the
relationships (e.g. the behavior) between them. An enterprise
architecture framework collects together tools, techniques, artifact
descriptions, process models, reference models and guidance used by
architects in the production of enterprise-specific architectural
description.
 —he term "enterprise" is used because it is generally
applicable in many circumstances, including
Public or Private Sector organizations
An entire business or corporation
A part of a larger enterprise (such as a business unit)
A conglomerate of several organizations, such as a joint venture or
partnership
A multiply-outsourced business operation
m Enterprise systems are software applications that
automate and integrate all many of the key business
processes of an organization.
m You will develop core skills in object-oriented analysis
and design, allowing you to develop software that is fit
for purpose, reusable and amenable to change.
 Constructing enterprise systems is a complex engineering
endeavor.
 Before entering into the subject you want to learn about what
is
SDLC
UML
CASE — LS
Ô Software life cycle tells about the activities should be carried out
in relation to one another, and how often each activity should be
revisited. —here are some fundamental development activities
that are common to most processes. —hese are:
 Analysis- ‘

  
   

 
‘
 
 
 Design-
    ‘   ‘ 

 
 ‘   
  
 umplementation- ‘
 ‘
 ‘
 —esting-
   

 
Œ £alidation- º   ‘
  
 
 
‘
Œ £erification- º   ‘
  
 
‘ 

¢
 ¢
  



 
m —he waterfall process has been widely used and has
produced many successful software products.
However, it makes several assumptions that have been
criticized.
m However, its rigidity in the face of changes and its lack of
support for reuse make it unsuitable for modern enterprise
systems development, where coping with continuous business
changes and short time-to-market is paramount
 —he term ¶iterative· indicates the repetition of one or more activities;
the term ¶incremental· indicates that development proceeds from an
initial subset of the requirements to more and more complete
subsets, until the whole system is addressed. uncremental development
involves an initial partition of the intended functionality; some or all
of the subsequent development activities can be carried out
independently and in parallel. —he final product results from the total
integration of the partitions.
 ¢ 


 UP promotes a set of best practices, namely that development

should be organized in short time-boxed iterations, and that it
should be adaptive to accommodate inevitable change.
 —ime boxing means that a (usually) short fixed period of time is
devoted to each iteration.
 Adaptive means that adjustments are allowed at each iteration. each
iteration may provide an increment over, or simply revisit the output
of, the previous one.
A UP project is organized into four major phases:
 unception ² this is where the business case is developed, together with
an idea of the scope of the system and a rough estimate of the effort
required.
 Elaboration ² this is where the core of the system is developed in an
iterative fashion. un this phase, all major risks are addressed and
resolved; most of the requirements are identified and dealt with; and a
more realistic estimate of the effort required is made.
 Construction ² this is where the remaining lower risk and easier
elements of the system are constructed, again in an iterative fashion.
 —ransition ² this includes beta
testing and deploying the system.


 
¢ 


 
 Component-based software development advocates developing
software systems by selecting reliable, reusable and robust software
components and assembling them within appropriate software
architectures.
 Component-based enterprise software development (CBESD) is the
rapidly emerging trend in software engineering.
 —he purpose of CBSD is to develop large systems, incorporating
previously developed or existing components, thus cutting down on
development time and costs. ut can also be used to reduce
maintenance associated with the upgrading of large systems.
 CBSE embodies the ´the ¶buy, don·t build philosophy".CBSE is
aiming at realizing long-waited software reuse by changing both
software architecture and software process.
 —he CBSE generally embodies the following
fundamental software development principles:
 A. Independent Software Development
 B. Reusability
 C. Software quality
 D. Maintainability

—he life cycle of component-based software systems
can be summarized as follows:
 Requirements analysis
 Software architecture selection, construction, analysis, and
evaluation;
 Component identification and customization
 System integration
 System testing
 Software maintenance.
 

¢
CBSD is an inevitable next wave solution that has
potential to improve time ²to-market and man
power/cost trends that have been ongoing. CBSD
is best implemented using more modern software
technologies like:
 C M
 JA£A
 EJB
 C RBA
 ActiveX
 
 

¢
  

 


 
a
 a
a 
   

 a


  a
 
a 

a
a
* 0

a  
a
  
  ! 
"a

 a
 
   



* =a
 


a


    


aa
   #

   #  
$=  % 
   

    
   
 
  




* a

   $= 


   
a
   
##

   


 

 &'   
a
$= 

 



  
*
 
 
  
 
 

       


 
†

  
´







 









 
m —he APu technology provides the industrial standard for
independently connecting Java programming language and
a wide range of databases. —he user not only execute the
SQL statements, retrieve results, and update the data but
can also access it anywhere within a network because
of it's "Write nce, Run Anywhere" (W RA)
capabilities.
m JDBC application programmming interface is a part of
the Java platform that have included Java Standard Edition
(Java SE ) and the Java Enterprise Edition (Java EE) in
itself.
   ¢
—he JDBC APu has four main interface:
 —he latest version of JDBC 4.0 application
programming interface is divided into two packages
u-) java.sql
ii-) javax.sql.
 Java SE and Java EE platforms are included in both the
packages.
Ë a
  
—he JDBC Driver Manager is a very important class that defines
objects which connect Java applications to a JDBC driver.
Usually Driver Manager is the backbone of the JDBC architecture.
ut's very simple and small that is used to provide a means of
managing the different types of JDBC database driver running on
an application. —he main responsibility of JDBC database driver is
to load all the drivers found in the system properly as well as to
select the most appropriate driver from opening a connection to a
database. —he Driver Manager also helps to select the most
appropriate driver from the previously loaded drivers when a new
open database is connected.
 —he function of JDBC driver test suite is to make
ensure that the JDBC drivers will run user's program or
not . —he test suite of JDBC application program
interface is very useful for testing a driver based on
JDBC technology during testing period. ut ensures the
requirement of Java Platform Enterprise Edition
(J2EE).
—he JDBC- DBC bridge, also known as JDBC type 1 driver is
a database driver that utilize the DBC driver to
connect the database. —his driver translates JDBC method calls into
DBC function calls. —he Bridge implements Jdbc for any database
for which an dbc driver is available. —he Bridge is always
implemented as the sun.jdbc.odbc Java package and it contains a
native library used to access DBC.
V —his first two component of JDBC, the JDBC APu and
the JDBC Driver Manager manages to connect to the
database and then build a java program that utilizes SQL
commands to communicate with any RDBMS. n the
other hand, the last two components are used to
communicate with DBC or to test web application in
the specialized environment.
    
 
Au
 

   


  


 
 

Πc

    



c !"#$
 #%
Πc


&'  
!(!()
*
Πc


&'  
%%%%)
#
Πc

  
'
)
  
))'c