Download Technical Reference Model

e-Government Program (Yesser)
National Enterprise Architecture
Technical Reference Model
Version 1.0
Date:21/05/2014
e-Government Program (Yesser)
NEA - Technical Reference Model
Document Description
Document Title
Technical Reference Model
Document version
Document Status
Author
NEA Decision
1.0
Draft
NEA Team
Under Review
Versioning
Version
0.1
0.2
1.0
Date
7/1/2013
9/9/2013
21/5/2014
Description of changes made
Draft document
Initial draft
Final Draft
Document Validation
Version
Authors
0.1
0.2
MUHAMMED YASEEN
MOHAMMED A. AL-BARRAK
1.0
MOHAMMED A. AL-BARRAK
Review by
Date
Status
DRAFT
DRAFT
21/05/2014
FINAL DRAFT
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 2 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
References
S/No
1
2
3
4
5
6
7
Description & Location
FEA – FEDERAL ENTERPRISE ARCHITECTURE/ http://www.whitehouse.gov/omb/e-gov/FEA
AUSTRALIAN GOVERNMENT ARCHITECTURE REFERENCE
MODELS/http://agict.gov.au/sites/default/files/AGA-RM-Final-v3.0-July-2013.pdf
TOGAF® 9.1/ http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap43.html
U.S. DEPARTMENT OF VETERANS AFFAIRS – TRM/ HTTP://WWW.VA.GOV/TRM/
BUILDING A TANGIBLE TRM/ HTTP://WWW.SNYDERS.US/TANGIBLE_TRM.HTM
SHAW, ROBERT, COMPUTER AIDED MARKETING & SELLING (1991) BUTTERWORTH HEINEMANN
"GEOGRAPHIC INFORMATION SYSTEMS AS AN INTEGRATING TECHNOLOGY:
CONTEXT, CONCEPTS, AND DEFINITIONS". ESRI. RETRIEVED 9 JUNE 2011.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 3 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Table of Contents
1.
2.
3.
4.
Introduction ....................................................................................................................... 6
Value of TRM ..................................................................................................................... 7
Goals of TRM ..................................................................................................................... 8
TRM Structure ................................................................................................................... 9
4.1. TRM Overview ............................................................................................................. 9
4.2. TRM Service explanation: .......................................................................................... 11
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 4 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Table of Figures
Figure 1 TRM Structure .............................................................................................................. 6
Figure 2 : Information System Service Use and Offering .......................................................... 10
Figure 3 Service Access and delivery service area................................................................... 11
Figure 4 Service Platform and Infrastructure service area ........................................................ 16
Figure 5: Component Framework service area ......................................................................... 21
Figure 6 Service Interface and Integration Area ....................................................................... 25
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 5 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
1. Introduction
The Technical Reference Model (TRM) (Figure 1) is a component-driven, technical framework
categorizing the standards and technologies to support and enable the delivery of Service
Components and capabilities. The framework will also enable the unification across government
agencies and whole-of-government guidance by providing a foundation to asserts and spurs the
re-use and standardization of technology and Service Components from a government-wide
perspective.
The scope of the TRM is wide-ranging, as it may be applied within a single agency, within a
government sector or within multiple of government agencies.
The following (Figure 1) depicts the core components that are defined for the TRM in order to
enabling the ability for
categorizing,
unifying
and
standardizing
technological
components:
Figure 1 TRM Structure
As it is depicted above, the TRM structure is hierarchically organized to facilitate categorizing
standards and technologies that all together enable the secure delivery, exchange and
implementation of business and application Service Components that may be used and
leveraged in a component-based or service-oriented architecture. The structure is consisted of
the following major blocks:
Service Area: represent a technical tier supporting the secure construction, exchange, and
delivery of Service Components. Each Service Area consists of multiple Service Categories and
Service Standards.
Service Category: assemble lower levels of technologies and standards with having similar
aspects of business or technology function they serve.
Service Standard: define the standards and technologies that belong to a Service Category.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 6 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
2. Value of TRM
The TRM can provide values for both government agencies independently and across
government agencies from a government-wide perspective.
The major value of the TRM appears in the traceability by mapping the standards and
technologies with IT investment, and this is will enable of measuring and evaluating the
achievements and usability of the technologies and standards at the level of government
agency. In addition, aligning agency capital investments to the TRM will leverages a common,
standardized vocabulary that facilitates interagency discovery, collaboration, and
interoperability.
Furthermore, the TRM allows the traceability with other known reference model such as
business reference model which enable measuring/demonstrating the importance and the
usability of each technology and standard. For example: KPIs from the performance model
mapped to a specific service standards in the TRM offers additional insight for managers in
terms of feasibility, cost.
In addition, the TRM standards’ profiles are rich with technical details such as technology’s
maturity, product’s information, and technology age, which will help IT people to handle
technology life-cycle more accurately. They will easily decide whether relevant technology
should keep being used, updated or discarded by periodically analysis its properties. The
technical details for standards can also be utilized to classify their characteristics, and this will
easily help to find reusable components, or to find opportunity’s to combine systems into one to
reduce costs and efforts.
Finally, the structural and simpler design of the TRM will benefit the government from
economies of scale by identifying reusable solutions and best technological components from
different agencies and propose it to other agencies to support their business and save budget
and effort in national level.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 7 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
3. Goals of TRM
The TRM can accelerate enterprise and joint action around new opportunities afforded by
standardized approaches for accomplishing goals such as the following:
Enabling increased visibility and availability and traceability of technologies and solutions across
government agencies.
Fostering increased information sharing across government agencies to boost the concept of
reusability and openness.
Establishing the base of common information technology language across government
agencies by defining and classifying the whole information technology components in
standardized structure that facilitate communications across IT department of government
agencies.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 8 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
4. TRM Structure
4.1.
TRM Overview
NEA TRM is based on U.S Fedral Government TRM and then reflected with the Saudi
government agencies environment. This reflection was to simplify and abstract the model to
make a better utilization and realization of the value. The following table represents the high
level outlines of the TRM:
Service Area
Service Categories
Service Access and Delivery
Access Channels
Delivery Channels
Service Requirements
Service Transport
Service Platform and Infrastructure
Support Platforms
Delivery Servers
Software Engineering
Databases/Storage
Hardware/Infrastructure
Component Framework
Security
Presentation/Interface
Programming
Data Interchange
Data Management
Service Interface and Integration
Integration
Interoperability
Interface
The following diagram can simply visualize the way that a user interacts with government
agency’s systems, which is exactly reflecting the TRM method of classifying technological
components, HW, and SW.
Internal SW/HW Components
Customer Facing Service
External Service User
Database
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 9 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Figure 2 : Information System Service Use and Offering
From the diagram, It can be seen that all systems have external user who directly interact and
make use of it. Also, these systems are linked to so many other internal HW/SW components.
The relation between these three major entities, user, customer facing system/service and
internal components, is as the following:
1. External users or systems use the customer facing system through access unit,
network access, interface, etc.
2. The customer facing system, which offer services, realize and provide services by
utilizing various technologies such as programming, user interface, security, data
technology, etc.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 10 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
4.2.
TRM Service explanation:
Service Access and Delivery Service Area
This area (Figure 2) defines the collection of Access and Delivery Channels that will be used to
enable the access of the Service Component, and the legislative requirements that govern its
use and interaction
Service Access and Delivery
Access Channels
Mobile
Mobile Devices
Devices
Internet
Internet
Web
Web Browse
Browse
Extranet
Extranet
Telephony
Telephony
Collaboration
Collaboration //
Communications
Communications
Other
Other Electronic
Electronic
Channels
Channels
GSB
GSB Service
Service
Service Requirements
Delivery Channels
GSN
GSN
Legislative
Legislative //
Compliance
Compliance
Intranet
Intranet
Peer
Peer to
to Peer
Peer (P2P)
(P2P)
Hosting
Hosting
Authentication
Authentication //
Single
Single Sign-on
Sign-on (SSO)
(SSO)
Service Transport
Supporting
Supporting
Network
Network Services
Services
Service
Service Transport
Transport
Virtual
Virtual Private
Private
Network
Network (VPN)
(VPN)
Figure 3 Service Access and delivery service area
In the following tables, there are full elaborations of this service area along with identifying its
categories. In addition, there is variety of examples provided to assist in clarifying each service
standards. Agencies should consult whole of government policies, frameworks and standards
together with their agency SOE to determine product requirements.
ACCESS CHANNELS:
Access channels define any medium that enable users of accessing applications/services.
Service Standard
Web Browser
Mobile Devices
Define By
The program that serves as
your front end to the World
Wide Web on the Internet. In
order to view a site, you type
its address (URL) into the
browser's location field.
The
devices
that
use
transmission via the airwaves
and enable user to access
application through display
screen with touch input and/or
a miniature keyboard.
Examples
Microsoft IE, Mozilla Firefox,
Google Chrome.
Smart phones, Tablets.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 11 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standard
Collaboration
Communications
Telephony
Other Electronic Channels
Define By
/ The forms of electronic
exchange
of
messages,
documents
or
other
information.
Electronic
communication
provides
efficiency through expedited
time of delivery.
Examples
 Social
networking
services
such
as:
Facebook,
twitter,
Youtube.
 Short message service
(SMS)
 Interactive
voice
response
(IVR):
a
telephony technology in
which someone uses a
touch-tone telephone to
interact with a database to
acquire information from
or enter data into the
database.
 Voice
over
internet
protocol (VOIP).
 Electronic mail (email).
 Kiosk: a small physical
structure (often including a
computer and a display
screen)
that
displays
information for people
walking by. Kiosks are
common
in
public
buildings. Kiosks are also
used at trade shows and
professional conferences.
Including phones and faxes.



System to system: which
include at least two
computers
that
communicate with each
other
directly
and
independent of human
intervention in order to
exchange data.
Web services.
Uniform
resource
locator (URL).
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 12 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standard
GSB Service
Define By
Examples
GSB is an entity that contains
intermediary
systems
of
integrated
infrastructure
components of hardware and
software
designed
to
activating the exchange of
shared
government
data
among agencies that are
authorized to access the data
in order to deliver their
respective
e-Government
services in an accurate,
speedy and safe manner
DELIVERY CHANNELS
Delivery channels define the type of network that used in order to access applications, services
and systems.
Service Standard
Define By
Examples
Internet
Intranet
A computer
network that
uses internet
protocol
technology
to
share
information,
operational
systems,
or
computing
services
within
an
organization.
Extranet
The private network that uses
the Internet protocol and the
public
telecommunication
system to securely share part
of a business's information or
operations with any external
parties like suppliers, vendors,
partners, customers or other
businesses.
Peer to Peer (P2P)
The class of applications that
operate outside the Domain
Name System (DNS), have
significant or total autonomy
from central servers and take
advantage
of
resources
available on the Internet.
GSN
Government Secure Network
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 13 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standard
Define By
Virtual Private Network (VPN)
The use of the public
telecommunication
infrastructure,
maintaining
privacy through the use of a
tunnelling
protocol
and
security procedures.
Examples
SERVICE REQUIREMENTS
Service requirements define the necessary aspects and prerequisites of an application, system
or service including legislation, performance and hosting aspects.
Service Standard
Define By
Examples
Legislation / Compliance
The prerequisites that an  Customization
and
application, system or service
bespoke development:
must have, as mandated by
refers
to
the
MCIT
the Saudi Government or any
Customization
and
other authorized governing
Bespoke
Development
bodies.
Policy, which mandates
specific requirements that
agencies
must
follow
when they customize or
bespoke
development
software.
 Open source
 IPv6
 Security
Authentication / Single Sign- The method that provides
on (SSO)
users with the ability to login
one
time,
getting
authenticated access to more
than one application and
resources.
Hosting
The service provider who
manages
and
provides
storage space, access and
availability to a website or
application, often bound to a
Service Level Agreement
(SLA). The Hosting entity
generally maintains a server
farm with network support,
power backup, fault tolerance,
load balancing and storage
backup.
SERVICE TRANSPORT
Service transport defines the end-to-end management of the communications session to include
the access and delivery protocols.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 14 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standard
Supporting Network
Services
Define By
The supporting protocols that
define
the
format
and
structure
of
data
and
information that is either
accessed from a directory or
exchanged
through
communications.
Service Transport
The core protocols that define
the format and structure of
data and information that is
either accessed from a
directory
or
exchanged
through communications.
Examples
 Internet Message Access
Protocol/Post Office.
 Protocol (IMAP/POP3).
 Simple
Mail
Transfer
Protocol (SMTP).
 Extended Simple Mail
Transfer
Protocol
(ESMTP).
 Simple
Network
Management
Protocol
(SNMP).
 Lightweight
Directory
Access Protocol (LDAP).
 Directory Services.
 Dynamic
Host
Configuration
Protocol
(DHCP).
 Domain Name System
(DNS).
 Border Gateway Protocol
(BGP).
 Transmission
Control
Protocol (TCP).
 Internet Protocol (IP).
 Hyper
Text
Transfer
Protocol (HTTP).
 Wireless
Application
Protocol (WAP).
 File Transfer Protocol
(FTP).
 IP Security (IPSEC).
Service Platform and Infrastructure Service Area
The Service Platform and Infrastructure Service Area (Figure 3) define the collection of
platforms, hardware and infrastructure standards that enable Component Based Architectures
and Service Component re-use.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 15 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Platform and
Infrastructure
Wireless
Wireless Mobile
Mobile
Platform
Platform
Independent
Independent
Platform
Platform dependent
dependent
Software
Engineering
Delivery Systems
Support Platforms
Web
Web Servers
Servers
Media
Media Servers
Servers
Application
Application Servers
Servers
Portal
Portal Servers
Servers
Integrated
Integrated
Development
Development
Environment
Software
Environment (DE)
(DE) Software
Configuration
Configuration
Management
Management
Test
Test Management
Management
Modelling
Modelling
Database/Storage
Hard/Infrastructure
Database
Database
Servers
Servers //
Computers
Computers
Storage
Storage
Peripherals
Peripherals
Local
Local Area
Area
Network
Network (LAN)
(LAN)
Video
Video
Embedded
Embedded
Technology
Technology
Devices
Devices
Wide
Wide Area
Area Network
Network
(WAN)
(WAN)
Network
Network Devices
Devices //
Standards
Standards
Figure 4 Service Platform and Infrastructure service area
In the following tables, there are full elaborations of this service area along with identifying its
categories. In addition, there is variety of examples provided to assist in clarifying each service
standards. Agencies should consult whole of government policies, frameworks and standards
together with their agency SOE to determine product requirements.
SUPPORT PLATFORMS
Support platforms refer to hardware and software architectures. This service area is to list the
standard platforms with considering their dependencies to any operating systems.
Service Standard
Wireless/Mobile
Platform Independent
Platform Dependent
Define By
The radio transmission via the
airwaves.
Various
communications techniques
are used to provide wireless
transmission including infrared
‘line
of
sight’,
cellular,
microwave, satellite, packet
radio and broad spectrum.
The definition of the platforms
which are able to execute and
run on any operating systems.
A platform is consisted of the
underlying
hardware
and
software comprising a system.
The
description
of
the
platforms which are able to
execute and run on a specific
operating systems. A platform
is the underlying hardware
and software comprising a
system.
Examples
Java 2 Platform, Micro Edition
(J2ME).
Hypervisor, Java 2 Platform
Enterprise Edition (J2EE),
Linux, Eclipse.
Windows, Mac OS, Net.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 16 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
DELIVERY SERVERS
Delivery Servers are front-end platforms that provide information to a requesting application. It
includes the hardware, operating system, server software and networking protocols. Front-end
platforms’ functionalities stop when it engages with the back-end or client management using
service integration.
Service Standard
Web Servers
Media Servers
Application Servers
Portal Servers
Define By
The computer that provides
world wide web services on
the Internet. It includes the
hardware, operating system,
web server software, TCP/IP
protocols and the website
content (web pages).
The provision of optimized
management of media- based
files such as audio and video
streams and digital images.
In an n-tier environment, a
separate
computer
(application server) performs
the business logic, although
some part may still be
handled
by
the
user's
machine. Business Rules
Engine are software systems
that executes one or more
business rules in a runtime
production environment.
Focus points for interaction,
providing integration and
single source corporate
information.
Examples
 Apache.
 Internet
Server.
Information


Real Audio.
Windows Media Services.

IBM’s
WebSphere
Application Server.
Oracle Application Server

SOFTWARE ENGINEERING
Software engineering defines platforms associated with building software systems, as well as
technical solutions that handle management issues such as testing, modeling and versioning.
Service Standard
Define By
Examples
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 17 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standard
Define By
Integrated
Development The combination of hardware,
Environment (IDE)
software and technology that
facilitate the development of
software applications and
systems.
Software
Configuration Systems related to all aspects
Management
of
software
development
which
controlled
and
managed by the software
development
lifecycle
methodology starting from
design to delivery, specifically
focused on the control of all
work products and artifacts
generated
during
the
development process.
Examples
 Rational
Developer.
 VS.Net








Application
Version
management:
refers to tracking and
controlling versions of
files. Version Management
includes capabilities such
as labelling, branching,
merging, version content
comparisons and security
and
permission
management
across
version controlled projects
Defect tracking: refers to
the
identification,
assignment
and
management
of
discovered defects within
an application, product or
solution. Defect tracking
tools provide searchable
defect data to identify
urgent and related defects
or bugs. The architecture
should be built to facilitate
the pushing of software
patches
across
the
enterprise.
Issue
management:
refers to the management
of business, technical and
infrastructure
issues
throughout the entire lifecycle of a project.
Task management.
Deployment management.
Change management.
Deployment management.
Requirements
management
and
traceability.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 18 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standard
Test Management
Modeling
Define By
Examples
Systems
support
management
and
consolidation of all testing
activities and results. Test
Management activities include
test planning, designing (test
cases), execution, reporting,
code coverage and heuristic
and harness development.
The provision of support for  Unified
Modelling
the process of representing
Language (UML)
entities, data, business logic  Computer Aided Software
and capabilities for aiding in
Engineering
(CASE)
software engineering.
software
DATABASE/STORAGE
Database/storage refers to programs that enable storing, modifying and extracting of
information from a database, and various techniques and devices/hardware for storing large
amounts of data.
Service Standard
Database
Storage
Define By
A collection of
information organised
in such a way that a
computer program can
quickly select desired
pieces of data. A
database management
system (DBMS) is a
software application
providing management,
administration,
performance, and
analysis tools for
databases.
Devices designed to
provide shared storage
access across a
network. These devices
provide extended
storage capabilities to
the network with
reduced costs
compared to traditional
file servers.
Examples
 Database 2 (DB2)
 Oracle
 SQL Server
 Sybase


Network attached storage
(NAS)
storage
area
network
(SAN)
HARD / INFRASTRUCTURE
This category defines the physical devices, facilities and standards providing the computing and
networking within and between enterprises.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 19 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standards
Servers / Computers
Defines
Any type of programmable
machines which are capable
of
responding
to
and
preforming sets of instructions
and executing programs.
Technology Any devices or parts that form
a server or computer as well
as devices that execute
specific functions outside of a
server or computer.
Examples
 Enterprise server
 Mainframe
Embedded
Devices

Peripherals
Local Area Network
(LAN)
Wide Area Network (WAN)
Network Devices/Standards
Refers to computer devices
that are not part of the
essential computer (i.e. the
memory and microprocessor)
but can be connected to it and
they can either be external
and internal.
A network that interconnects
devices over a geographically
small area, typically in one
building or a part of a building.
This type of network enables
the sharing of resources such
as printers, scanners and the
exchange of any type of data.
A data network extending a
LAN outside a building or
beyond a campus. This is
typically created by using
bridges or routers to connect
geographically
separated
LANs.
Network
devices/standards
enable the connection among
mutable
LANs/WANs
for
exchanging
information.
Connection
can
be
permanent, via cable, or
temporary, through telephone
or other communications links.
The transmission medium can
be physical (e.g. fibre optic
cable) or wireless (e.g.
satellite).






Random access memory
(RAM)
Hard disk drive
Microprocessor:
Redundant
array
of
independent disks (RAID).
Printer.
Scanner.
Facsimile (fax).
Graphics tablets.
Cameras.
Assistive devices.



Ethernet.
Token ring.
Virtual LAN (VLAN).


Frame relay.
Asynchronous
mode (ATM).




Hub.
Switch.
Router.
Network Interface Card
(NIC).
Transceivers.
Gateways.
Integrated services digital
network (ISDN).
Digital subscriber line
(DSL).
Firewall.








transfer
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 20 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standards
Video
Defines
Video conferencing provides
communication across long
distances with video and
audio contact that may also
include graphics and data
exchange.
Digital
video
transmission systems typically
consist of camera, codec
(coder decoder), network
access equipment, network
and audio system.
Examples
 Bridge.
 Codec.
 Receiver.
Component Framework Service Area
The Component Framework Service Area (Figure 4) defines the underlying foundation and
technical elements by which service components are built, integrated and deployed across
component-based and distributed architectures.
The component framework consists of the design of application or system software that
incorporates interfaces for interacting with other programs and for future flexibility and
expandability. This includes, but is not limited to, modules that are designed to interoperate with
each other at run-time.
Components can be large or small, written by different programmers using different
development environments and may be platform independent. Components can be executed on
stand-alone machines, a LAN, intranet or the Internet.
Component Framework
Security
Public
Public Key
Key
Technology
Technology
Presentation / Interface
Static
Static Display
Display
Supporting
Supporting Security
Security
Services
Services
Content
Content
Rendering
Rendering
Programming
Platform
Platform Independent
Independent
Dynamic
Dynamic // ServerServerPlatform
Platform Dependent
Dependent
Side
Side Display
Display
Data Interchange
Data
Data Exchange
Exchange
Data Management
Database
Database Connectivity
Connectivity
Reporting
Reporting and
and Analysis
Analysis
Wireless
Wireless // Mobile
Mobile //
Voice
Voice
Figure 5: Component Framework service area
In the following tables, there are full elaborations of this service area along with identifying its
categories. In addition, there is variety of examples provided to assist in clarifying each service
standards. Agencies should consult whole of government policies, frameworks and standards
together with their agency SOE to determine product requirements.
SECURITY
Security defines the methods and mechanisms of protecting information and information
systems from unauthorized access, use, disclosure, disruption, modification or destruction in
order to provide integrity, confidentiality as well as privacy for users’ information. Use of
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 21 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
encryption technologies such as biometrics, two factor identification should align with the
requirements of the YEFI standards.
Service Standards
Public Key technology
Supporting security services
Defines
Examples
Software and services used
by the National Center for
Digital
Certification
to
generate digital keys and
certificates to secure access
to information.
The different protocols and  Secure Sockets Layer
components to be used to
(SSL).
support
public
key  Transport Layer Security
technologies.
(TLS)
 Secure Shell (SSH)
 Security Assertion Markup
Language (SAML)
PRESENTATION/INTERFACE
Presentation/interface defines the interface content of the software that represented on the
screen for the end-user.
Service Standards
Static Display
Defines
The software protocols that
are used to create a predefined, unchanging graphical
interface between the user
and the software.
Dynamic / Server Side Display The software that is used to
create
graphical
user
interfaces with the ability to
change while the program is
running.
Content Rendering
The software and protocols
used for graphically changing
data for presentation in a user
interface.
Examples
 Hypertext
Markup
Language (HTML).
 Portable
Document
Framework (PDF/A/X).







Wireless / Mobile /
Voice
The software and protocols 
used for wireless- and voice
enabled presentation devices. 
Java Server Pages (JSP)
Active
Server
Pages
(ASP)
Active Server Pages .Net
(ASP.Net)
Dynamic HTML (DHTML)
Extensible
HTML
(XHTML).
Cascading Style Sheets
(CSS).
Extensible 3D Graphics
(X3D).
Wireless
Markup
Language (WML).
XHTML Mobile Profile
(XHTMLMP).
PROGRAMMING
Programming defines the software, protocol or method by which business rules are enforced
within applications.
Service Standards
Defines
Examples
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 22 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standards
Defines
Platform
Independent A description of all software
languages
languages that are able to
execute and run on any type
of operating system or
platform.
Platform
Dependent A
description
of
the
languages
programming languages and
methods
for
developing
software
on
a
specific
operating system or platform.
Examples
 Enterprise
(EJB)
 C, C++
 JavaScript



Java
Beans
Visual Basic
Visual Basic.Net (VB.Net)
C-Sharp (C#)
INTEGRATED PACKAGE
Integrated Package defines the common-use application software which combines a set of
commonly used functions of many productivity software programs into one application.
Service Standards
ERP (Enterprise Resource
Planning)
Defines
Examples
A description of
business  ORACLE ERP
management
software—  SAP
usually a suite of integrated
applications—that a company
can use to store and manage
data.
CRM (Customer Relationship A description of is a system
Management)
for managing a company’s
interactions with current and
future customers.
Portal
A description of single window
web page at a website which
brings information together
from diverse sources in a
uniform way.
KMS
(Knowledge A description of knowledge
Management System)
management system that
used
to
improve
organizational
competitiveness
by
systematizing and sharing
individual knowledge which
organizational
human
resources accumulate.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 23 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standards
BPM
(Business
Management)
Defines
Examples
Process A description of tool that
supporting explicit process
management which includes
(process definition, execute,
monitoring, analysis, etc.).
The tool supports managing
different kind of process
interactions that happens
between person and person,
person and system, system
and system.
A description of system
designed to capture, store,
GIS (Geographic Information
manipulate, analyze, manage,
System)
and
present
all
types
of geographical data.
A description of system that
EDM (Electronic Document
used to store, track and
Management)
manage documents.
A description of system that
used to support and manages
the
project
management
PMS
business
which
include
planning,
executing,
monitoring,
and
closing
projects.
DATA INTERCHANGE
Data interchange defines the methods in which data is transferred and represented in and
between software applications.
Service Standards
Data Exchange
Defines
The languages and protocols
of sending of data over a
communications network and
the
definition
of
data
communicated
from
one
application to another. Data
exchange
provides
the
communications
common
denominator
between
disparate systems.
Examples
 XML Metadata Intercharge
(XMI).
 XQuery.
 Simple Object Access
Protocol (SOAP).
DATA MANAGEMENT
Data management is the management of all data/information in government agency. It includes
data administration, the standards for defining and classifying data and the way in which people
comprehend and use it.
Service Standards
Defines
Examples
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 24 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standards
Database Connectivity
Reporting and Analysis
Defines
Examples
The protocol or method in  Java
Database
which an application connects
Connectivity (JDBC).
to a data store or database.
 Open
Database
Connectivity (ODBC).
 Active Data Objects .Net
(ADO.Net).
 Object
Linking
and
Embedding/Database
 (OLE/DB).
 Data
Access
Objects
(DAO).
 DB2 Connector.
The tools, languages and  Extensible
Business
protocols used to extract data
Reporting
Language
from a data store and process
(XBRL).
it into useful information.
 Java Online Analytical
Processing (JOLAP)
 Online
Analytical
Processing (OLAP).
Service Interface and Integration Service Area
The Service Interface and Integration Service Area (Figure 5) define the technologies
enable the communications, discovery and integration among disparate systems
information providers. SOAs is the software design and architecture that leverage
incorporate Service Interface and Integration standards to facilitate interoperability
scalability.
that
and
and
and
Service Interface and
Integration
Interoperability
Integration
Middleware
Middleware
Enterprise
Enterprise Application
Application
Integration
Integration
Data
Data Format
Format //
Classification
Classification
Interface
Service
Service Discovery
Discovery
Data
Data Types
Types //
Validation
Validation
Data
Data Transformation
Transformation
Service
Service Description
Description //
Interface
Interface
Figure 6 Service Interface and Integration Area
In the following tables, there are full elaborations of this service area along with identifying its
categories. In addition, there is variety of examples provided to assist in clarifying each service
standards. Agencies should consult whole of government policies, frameworks and standards
together with their agency SOE to determine product requirements.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 25 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
INTEGRATION
Integration defines the software services enabling data of different distributed applications to
interoperate. This integration can enable sharing function, content and communications across
heterogeneous computing environments. In particular, service integration which provides a set
of architecture services such as platform and service location transparency, transaction
management, basic messaging between two points, and guaranteed message delivery.
Service Standards
Middleware
Enterprise
Integration (EAI)
Defines
Middleware increases the
flexibility, interoperability and
portability
of
existing
infrastructure by linking or
‘gluing’
two
otherwise
separate applications.
Application The processes and tools
specializing in updating and
consolidating applications and
data within an enterprise. EAI
focuses on leveraging existing
legacy applications and data
sources so that enterprises
can add and migrate to
current technologies.
Examples
 Remote Procedure Call
(RPC).
 Message
Oriented
Middleware (MOM): IBM
WebSphere MQ.
 Database
Access:
PL/SQL.
 Database
Access:
ISQL/w.
 Transaction
Processing
Monitor.
 Object Request Broker
(ORB). Component Object
Model (COM).
 Object Request Broker
(ORB).
 Component Object Model
(DCOM).
 Object Request Broker
(ORB): Component Object
Model + (COM+).
 Business
process
management.
 application connectivity
 transformation
and
formatting
INTEROPERABILITY
Interoperability defines the capabilities of discovering and sharing data and services across
disparate systems and vendors.
Service Standards
Defines
Examples
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 26 / 27
e-Government Program (Yesser)
NEA - Technical Reference Model
Service Standards
Data Format / Classification
Data Types / Validation
Data Transformation
Defines
The structure of a message
files that used to design a
message in a commonly
standardized format. There
are different of file formats
and every application has its
selection of those formats
based on many different
variations (database, word
processing,
graphics,
executable program, etc.).
Each format defines its own
layout of the data and the
simplest and common format
is text file.
The standards used in
identifying
and
affirming
common
structures
and
processing
rules.
This
technique is referenced and
abstracted from the content
document or source data.
The protocols and languages
that change the presentation
of data within a graphical user
interface or application.
Examples
 Extensible
Markup
Language (XML).
 XML Linking Language
(XLINK).
 Namespaces.
 Electronic
Data
Interchange (EDI)



Document Type Definition
(DTD).
XML Schema.
Extensible
Language
(XSLT).
Style Sheet
Transform
INTERFACE
Interface defines the capabilities of communicating, transporting and exchanging information
through a common dialogue or method. Delivery channels provide the information to reach the
intended destination, whereas interfaces allow the interaction to occur based on a predetermined framework.
Service Standards
Service Discovery
Service Description / Interface
Defines
The
method
in
which
applications, systems or web
services are registered and
discovered.
The method for publishing the
way in which web services or
applications can be used.
Examples
 Universal
Description
Discovery and Integration
(UDDI)


Web Services Description
Language (WSDL).
Application
Program
Interface (API) / Protocol.
Confidential e-Government Program (Yesser)
This document (either in whole or in part) cannot be modified or
reproduced without the prior written permission of the e-Government Program (Yesser)
Page 27 / 27