Technical Architecture Document for Strata Limited's New System

This technical architecture document outlines the design and implementation of a new client/server system for Strata Limited, replacing the existing mainframe Merge system. The document details the system's N-tier architecture, encompassing presentation, middleware, componentware, and data tiers, along with the communication protocols between them. It specifies the technologies and tools to be used, including JBuilder, VisiBroker, and Oracle JDBC drivers. Furthermore, the document describes the software configuration management strategy and the technical resource requirements for both development and production sites, including hardware and software specifications for servers, workstations, and network infrastructure. Justifications for the architectural choices, advantages, and features are also provided, ensuring adaptability to changing business environments. Finally, the document covers the documentation strategy for both user and technical documentation.

Technical Architecture Document
Strata Limited
Information Systems Technology
Dec 16, 2017
Version 1.0
Presented by:

Table of Contents
1 OVERVIEW................................................................................ 1
1.1 Background............................................................................................1
1.2 Objective................................................................................................1
2 TECHNICAL ARCHITECTURE........................................................2
2.1 Presentation Tier....................................................................................4
2.2 Middleware Tier(s)..................................................................................4
2.2.1 Presentation Tier to Componentware Tier Communication.............4
2.2.2 Componentware Tier to Data Tier Communication..........................5
2.3 Componentware Tier..............................................................................5
2.4 Data Tier................................................................................................6
2.5 Documentation.......................................................................................6
2.6 Software Configuration Management.....................................................6
3 TECHNICAL RESOURCE REQUIREMENTS......................................7
3.1 Development Site...................................................................................7
3.1.1 Software Development Environment...............................................8
3.1.2 Software Configuration Management Environment.........................9
3.1.3 Test Environment.............................................................................9
3.2 Production Site.......................................................................................9
3.2.1 Test Environment...........................................................................10
3.2.2 Software Configuration Management Environment.......................10
3.2.3 Production Environment.................................................................11
3.3 Physical Deployment Diagram.............................................................12
4 JUSTIFICATIONS, ADVANTAGES, AND FEATURES........................13

1 INTRODUCTION
Strata Limited System (SLS) task and describes the overall goal of this
document relative to the particular project. The development of company
principle and data access elements provides the basis for establishing
adaptable strategies that will support changing business environments.
Company rules automate the business procedures, and the data access
elements automate the space for storage, look for, and selection of
information by the application and determine how the business rules connect
with the information in the data source.
1.1 Background
STRATA RESTRICTED Systems Management Unit (SLSMU) requested to
design, construct, check, and implement a new client/server system to
replace the current mainframe Merge system, referred to as STRATA LIMITED
also, since this particular cannot be remediated for Season 2000 (Y2K)
conformity.
1.2 Objective
It is crucial to resolve just about all technology requirements and options
before beginning the actual style and construction activities for that STRATA
LIMITED project. Deferring the choice or associated with specific technology
solutions may have a substantial impact on system advancement if these
decisions are created during later stages from the project.
2. Technical architecture
STRATA LIMITED shall be created according to a good N-tier client/server
architecture. This means that the software program will be designed as
several components deployed in several tiers. Defined interfaces will allow
the components within the divisions to communicate with each extra. N-tier
applications have the subsequent advantages over applications sticking with
other types of technical architectures (e. g., monolithic, 2-tier, 3-tier):
o They are easy to change in support of changing business guidelines.
o There is less risk adjusting the code that accessories any given
business rule.
o These are highly scaleable.
o They can assistance any combination of user interfaces (e. g.,
character, visual, web browser, and telephone).
o They provide the greatest potential for program code recycling and
sharing.

This diagram identifies the specialized architecture, the various
systems, as well as the actual items chosen with regard to STRATA
LIMITED. A brief dialogue of each tier and the particular product(s) to
be used within that will rate follows the plan.
.
The next sections address the various divisions (i. digital., presentation,
middleware, componentware, and data) portrayed in the above diagram, and
also the implementation of software and proof configurations management.
1.3 Presentation Tier
JBuilder 2 Client/Server Package deal will be used to generate the GUI
screens; the particular resultant code is fully pure Java and hence could be
applied on any system where a Java Virtual Device (JVM) is implemented.
These types of screens will contain the minimum of processing thinking in
order to more effectively separate the reasonable architectural divisions. The
GUI screens will be developed based on industry and DOT requirements.

1.4 Middleware Tier(s)
Middleware can be used for both intra-application communication within the
several tiers of an N-tier program and inter-application communication
between system and external providers. It is possible for the logical divisions
inside a single N-tier application to reside on various bodily machines and
various systems. Thus, there is a need for dexterity and communication
among the reasonable tiers. Intra-application middleware easily simplifies
the deployment and advancement applications in a distributed atmosphere.
1.4.1 Presentation Tier to Componentware Tier Communication
STRATA LIMITED will use Inprise’s VisiBroker for Java three or more. 2 Object
Request Agent (ORB) to implement the particular CORBA standard. The
VisiBroker ORB for Java attaches a client program running on the Java digital
machine (presentation tier) with the objects this requests for use
(componentware tier).
1.4.2 Componentware Tier to Data Tier Communication
STRATA LIMITED will use the particular Oracle JDBC motorists because the
data access middleware. This particular middleware will provide
communication among info access programs (componentware tier) and the
relational data bank (data tier). Componentware Rate
o The database modeling plus design will be performed making use of
PowerSoft PowerDesigner Information Builder 6. 1 . This tool will give
you the repository of program organizations, attributes, and human
relationships. This has the capability of developing the following:
o Enterprise relationship layouts
o A details dictionary
o Extensive model reports
o The conceptual data model
o A bodily data model generated through the conceptual data model
o Data source explanation scripts from the real data model
1.5 Documentation
User and Technical evidence will be provided for STRATA LIMITED. User
paperwork is going to be created for helping users associated with STRATA
LIMITED and the Specialized Documentation will be developed mainly for use
merely by the tech support team for STRATA RESTRICTED. The STRATA
LIMITED proof shall be created using Microsoft Term. Both hardcopy and
softcopy versions will be made available.
1.6 Software Configuration Management
Software program Configurations Management (SCM) is usually essential to
maintaining regularity, coherence, and integrity in different software
application. SCM is also an essential component of the Carnegie Mellon
Software Engineering Institute’s (SEI) Capability Maturity Model (CMM) Level
3 practices.

2 TECHNICAL RESOURCE REQUIREMENTS
This section recognizes the recommended computing system requirements
needed to support the particular development, testing, and procedure
(production) of STRATA RESTRICTED. The development site will certainly
deploy the following environments:
The particular development environment, which will be utilized for design,
programming, and device test An excellent SCM atmosphere, which will be
used for dealing with the application products, model control, plus archive
The test atmosphere, which will be used for system check activities.
.
2.1 Development Site
Resources shared by all the environments at the development site are listed
in the table below. Resources specific to each environment are identified in
the appropriate sections that follow.
Resource Resource Specification Quantity
Application Server NT server with a minimum of 256
MB of RAM and an 8 GB or larger
hard disk drive
1
Database Server NT server with a minimum of 256
MB of RAM, a 16 GB or larger hard
disk drive, and a tape backup drive
1
RDBMS Oracle8 15-20
concurrent
connections
Workstations Desktop workstation with Windows
95/NT/98, a minimum of 64 MB of
RAM, and a minimum of 2 GB hard
disk drive
6
Network The application server, database
server and the developers at
Gateway Plaza should be on a 100-
Megabit Ethernet or a 16-Megabit
Token Ring network.
Not applicable
Printer HP LaserJet or compatible 1
Backup Media – Data Any tape compatible to the tape
drive in the database server
5 (to be
recycled)
Backup Media –
Source code
CDRW (read and write CD) 5 (to be
recycled)

2.1.1 Software Development Environment
The resources identified in the following table are required to support the
software development environment.
Resource Resource Specification Quantity
Development Tool JBuilder 2 Client/Server Suite
(including VisiBroker and PVCS)
5
Reporting Tool Enterprise Reports 3.0 Pro – Swing
Edition
3 (Designer
Licenses)
Disk Space –
Application Server
2 GB of hard disk space (also used
for disk backups)
Not applicable
Disk Space –
Database Server
4 GB of hard disk space Not applicable
Connectivity to Merge Access to the Merge application
and to Merge data for query and
conversion
5 users
Connectivity to Crash Access to the Crash Reporting
System (CRS) production and
replicated Oracle data.
2 users

2.1.2 Software Configuration Management Environment
The resources identified in the following table are required to support the
SCM environment.
Resource Resource Specification Quantity
SCM Tool PVCS (included as part of the
JBuilder 2 Client/Server Suite,
identified in the development
environment)
5
Disk Space –
Application Server
2 GB of hard disk space Not applicable
2.1.3 Test Environment
The resources identified in the following table are required to support the
test environment.
Resource Resource Specification Quantity
Disk Space –
Application Server
2 GB of hard disk space Not applicable
Disk Space –
Database Server
4 GB of hard disk space Not applicable
Connectivity to Crash Access to CRS production and
replicated Oracle data
2 users
2.2 Production Site
Resources shared by all the environments at the production site are listed in
the table below. Resources specific to each environment are identified in the
appropriate sections that follow.
Resource Resource Specification Quantity
Application Server NT server with a minimum of 256
MB of RAM and an 8 GB or larger
hard disk drive
1
Database Server NT server with a minimum of 256
MB of RAM, an 8 GB or larger hard
disk drive, and a tape backup drive
1

Resource Resource Specification Quantity
RDBMS Oracle8 15-20
concurrent
connections.
This will
change
depending on
the use of an
ad hoc query
tool.
Workstations Desktop workstation with Windows
95/NT/98, a minimum of 64 MB of
RAM
As required
Network The application server, database
server and the users at the Traffic
Engineering and Safety Systems
Branch should be on a 100-
Megabit Ethernet network. DOT-
IST personnel at the Raney
Building should have either T-3 or
T-1 connectivity to this network.
Not applicable
Printer HPLasetJet or Compatible 1
Backup Media – Data Any tape compatible to the tape
drive in the database server
As required
Backup Media –
Application
Any tape compatible to the tape
drive in the application server
As required
2.2.1 Test Environment
The resources identified in the following table are required to support the
test environment.
Resource Resource Specification Quantity
Disk Space –
Application Server
2 GB of hard disk space Not applicable
Disk Space –
Database Server
4 GB of hard disk space Not applicable
Connectivity to Crash Access to CRS production and
replicated Oracle data
1 user

2.2.2 Software Configuration Management Environment
The resources identified in the following table are required to support the
SCM environment.
Resource Resource Specification Quantity
SCM Tool PVCS (included as part of the
JBuilder 2 Client/Server Suite,
identified in the development
environment)
1
Disk Space –
Application Server
2 GB of hard disk space Not applicable
3.2.3 Production Environment
The resources identified in the following table are required to support the
production environment.
Resource Resource Specification Quantity
Run-Time License VisiBroker Run-Time To be
determined
Disk Space –
Application Server
2 GB of hard disk space Not
applicable
Disk Space –
Database Server
4 GB of hard disk space Not
applicable
Connectivity to Crash Access to CRS
production/replicated Oracle data
1 user

2.3 Physical Deployment Diagram
The physical deployment of the production environment is represented in the
diagram below.
E th e rn e t
10 0 M e g ab it E th e rn et
A p p licatio n S e rv er D a ta ba se S erve r
C lien t
W in d o w s 9 5 /N T /9 8
64 M B R A M
C lie n t
W in d o w s 9 5 /N T /9 8
6 4 M B R A M
N T S e rv e r
2 5 6 M B R A M
8 G B H D D
N T S e rv er
25 6 M B R A M
8 G B H D D
V is iB rok e r
R un -T im e O ra c le 8
P rin te r(s )
R ou te r
T -3 o r T -1 Lin e
C lien t
W ind o w s 9 5 /N T /9 8
64 M B R A M
D O T -IS T s u p p o rt
p e rs o n n e l a t th e
R a n e y B u ild in g
P ro d u c tio n s ite
a t th e T h o m p s o n
B u ild in g

3 JUSTIFICATIONS, ADVANTAGES, AND FEATURES
The following table provides justification, advantages, and features for each
of the technical architecture hardware and software system components
chosen for STRATA LIMITED.
System Component Specific
Product(s)/Versio
n
Justifications,
Advantages, and
Features
Presentation
Environment
Microsoft (MS)
Windows 95/98/NT
 Windows has been
adopted as DOT’s
standard desktop
environment
Application Server MS Windows NT
Server 4.0 with
Service Pack 2 or
higher
 Windows NT clustering is
available to improve
reliability
 Windows NT support
personnel are available
within ETS
 The development tools
of choice are readily
available on this
platform
Database Server(s) MS Windows NT
Server 4.0 with
Service Pack 2 or
higher
 Oracle has consistently
performed well when
deployed on Windows
NT
Presentation Tier JBuilder 2
Client/Server Suite
 Produces pure Java
applications for cross-
platform deployment
 Tight CORBA standards
integration
 Integrated PVCS version
manager for team
development
 Complies with the NC
Statewide Technical
Architecture standards
Middleware VisiBroker for Java
3.2
 Complete support of
CORBA standards
 Integrated with the
development tool
Jbuilder 2 Client/Server
Suite