Lesson 2 - System

Architecture
Shaina Mae C. Bongo
 Prayer
Our Heavenly Father, we give you thanks and
praise. Thank you for all the blessings that you
have bestowed upon us, Thank you for the gift of
life, good health, and protection to our families
and loved ones. Father God, we humbly come
before you, asking for your blessings and
protection. Bless our discussions today, fill us
with knowledge and wisdom, and fill us with the
Holy Spirit to guide us to the path of
righteousness. May your Will be done and forgive
our shortcomings. In Jesus name, we pray, AMEN
CIS-552 Introduction 2
Architecture
System Architecture
• is the structural design of systems.
• The systems architecture process is where the
concepts that will be the backbone of the actual
system are developed. It is a conceptual model
that describes the structure and behavior of the
proposed system or of an existing system.
• The model could include the technical framework,
end user requirements, and a list of system
components (hardware and software).
• It is a conceptual model that
describes the structure and
behavior of the proposed
system or of an existing
system. The model could
include the technical
framework, end user
requirements, and a list of
system components
(hardware and software).
• The structural design of
systems. Systems are a class
of software that provide
foundational services and
automation. Slideshare.com
How to Define an Architecture
Defining an architecture, especially of an information
system, requires the following items to be described:
1. Processes that the system accomplish its intended
functions
2. The individual processes transform either data or
materials that “flow” between them
3. The processes or activities or operations follow rules
that establish the conditions under which they occur
4. The components that will implement the design
(hardware, software, personnel, and facilities must be
described)
How to Define an Architecture
• Defining the Functional Architecture
• A functional architecture is:
• A set of activities or functions that are arranged in
a specific order and when activated, achieves a set
of requirements
• Functional requirements drive the application
architecture of a system, while non-functional
requirements drive the technical architecture of a
system
• Functional Requirements = Functions or Working
• Non-functional requirements = Behavior of system
How to Define an Architecture
• Defining the Physical Architecture
• A physical architecture is:
• A representation of the physical resources
• Expressed as nodes that constitute the
system and their connectivity
• Expressed in the form of links
How to Define an Architecture
• Defining the Technical Architecture
• A minimal set of rules governing the
arrangement, interaction, and interdependence
of the elements that must ensure the specified
set of requirements
• Provides the framework upon which
engineering specifications can be derived,
guiding the implementation of the system
• Includes non-functional requirements
How to Define an Architecture
• Defining the Technical Architecture
• It is the name of the total concept that is
applied to the IT Infrastructure of an
organization. IT Infrastructure is a coherent set
of interconnected hardware and software, like
networks, clouds, servers, clients, printers,
tablet PC, smartphones.
Topic 2 - System
Architecture Checklist
Introduction
• An effective system combines elements into an
architecture, or design, that is flexible, cost-
effective, technically sound, and able to support
the information needs of the business
• System architecture translates the logical design
of an information system into a physical structure
that includes hardware, software, network
support, and processing methods.
System Architecture Checklist
• Enterprise Resource Planning (ERP)
• The objective of ERP is to establish a company-wide
strategy for using IT resources.
• Initial Cost and TCO (Total Cost of Ownership)
• During the final design stage, you make decisions that
will have a major impact on the initial costs and TCO
for the new system
• You should review all previews cost estimates
System Architecture Checklist
• Scalability
• Scalability, also called extensibility, refers
to a system’s ability to expand, change or
downsize easily to meet the changing need
of a business
• Especially important in implementing
systems that are volume-rated, such as
transaction processing systems
• Web Integration
• An information system includes applications
• Web-centric architecture
• Avoids many of the connectivity and
compatibility problems that typically arise
• E-marketplaces
• Legacy System Interface Requirements
• The new system might have to interface with
one or more legacy systems
• Interfacing a new system with a legacy system
involves analysis of data formats and
compatibility
• The analyst must know if the new application
eventually will replace the legacy system
• Processing Options
• In planning the architecture, designers
also must consider how the system will
process data – online or in batches
• Provision must be made for backup and
speedy recovery in the event of the system
failure
• Security Issues
• Security threats defenses are a major
concern to a systems analyst
• The analyst must consider security issues
that relate to system design specifications
• Web-based systems introduce additional
security concerns
 System Architect
• The architect is a member of the team that is
responsible for designing and building a system
• The architect’s contribution comes in the very
early stages of the systems engineering process
• When the operational concept is defined
• The basic structure of the system is conceptualized
• A system architect, not only knows about the
individual components but also understands the
interrelationships among the components
System Architecture for Online Shopping
System Architecture for Government
Online Voting System
Topic 3 – Information
System Architecture
Information System Architecture

• An information system architecture is a formal

definition of the business processes and rules,
systems structure, technical framework, and
product technologies for a business or
organizational information system.
• An information system architecture usually
consists of four layers: business process
architecture, systems architecture, technical
architecture, and product delivery architecture.
Information System Architecture

• The architecture of an information system

encompasses the hardware and software used to
deliver the solution to the final consumer of
services.
• The architecture is a description of the design and
contents of a computerized system.
Different Types of System Architecture

• Mainframe
• Client-Server
• Distributed system
• Cloud Architecture
 Mainframe
• Mainframes are a type of
computer that generally is
known for its large size,
amount of storage,
processing power, and high
level of reliability. Large
organizations primarily use
them for mission-critical
applications requiring high Techerati.co

volumes of data processing m

 Client-Server Architecture
• the architecture of a computer
network in which many clients
(remote processors) request
and receive service from a
centralized server (host
computer).
• Client computers provide an
interface to allow a computer
user to request services of
the server and to display the
results the server returns.
 Web-Based
• Like the client server model here instead of an
application, web browsers are there. The client machine
is connected to a web server through LAN, WAN, etc.
• Initial HTML was used. Pages were static
• With java script and AJAX, dynamic pages are seen
• The client sends a request to the server through an
application program.
• Role of the client is handle query of the user and
translate in the desired protocol for forwarding it to
server.
 Cloud Computing
• Cloud computing is the delivery of
different services through the Internet.
These resources include tools and
applications like data storage, servers,
databases, networking, and software.
Digitalconnectmag.com

• When something is in the cloud, it means

it is stored on servers on the Internet
instead of on your computer.
• It lets you access your calendar, email,
files, and more from any computer that
has an Internet connection. If you’ve ever
used a web-based email, you’ve used the
cloud.
slideshare.com
Types of Cloud Services
• Email
• Storage, backup, and data retrieval
• Creating and testing apps
• Analyzing data
• Audio and video streaming
• Delivering software on demand
Types of Cloud Computing
• Software-as-a-service (SaaS) involves the licensure of a software
application to customers. Licenses are typically provided through a
pay-as-you-go model or on-demand. This type of system can be
found in Microsoft Office 365.
• Infrastructure-as-a-service (IaaS) involves a method for delivering
everything from operating systems to servers and storage through
IP-based connectivity as part of an on-demand service. Clients can
avoid the need to purchase software or servers, and instead
procure these resources in an outsourced, on-demand service.
Popular examples of the IaaS system include IBM Cloud and
Microsoft Azure.
Types of Cloud Computing
• Platform-as-a-service (PaaS) is considered the most
complex of the three layers of cloud-based computing.
PaaS shares some similarities with SaaS, the primary
difference being that instead of delivering software
online, it is actually a platform for creating software that
is delivered via the Internet.
 Distributed Computing
• refers to multiple computer systems
working on a single problem. In
distributed computing, a single problem is
divided into many parts, and different
computers solve each part. As long as the
computers are networked, they can
communicate with each other to solve the
problem. Of done properly, the computers
perform like a single entity.
• The ultimate goal of distributed computing
is to maximize performance by connecting
users and I.T. resources in a cost-effective,
transparent, and reliable manner. It also
ensures fault tolerance and enables
resource accessibility if one of the
components fails.
Benefits and challenges of distributed
systems
There are three reasons that teams generally decide to implement
distributed systems:
• Horizontal Scalability—Since computing happens independently
on each node, it is easy and generally inexpensive to add
additional nodes and functionality as necessary.
• Reliability—Most distributed systems are fault-tolerant as they
can be made up of hundreds of nodes that work together. The
system generally doesn’t experience any disruptions if a single
machine fails.
• Performance—Distributed systems are extremely efficient because
workloads can be broken up and sent to multiple machines.
 Types of Distributed Systems
Distributed systems generally fall into one of four different
basic architecture models:
• Client-server—Clients contact the server for data, then
format it and display it to the end-user. The end-user can
also make a change from the client-side and commit it
back to the server to make it permanent.
• Three-tier—Information about the client is stored in a
middle-tier rather than on the client to simplify
application deployment. This architecture model is most
common for web applications.
Types of Distributed Systems
• n-tier—Generally used when an application or server
needs to forward requests to additional enterprise
services on the network.
• Peer-to-peer—There are no additional machines used to
provide services or manage resources. Responsibilities are
uniformly distributed among machines in the system,
known as peers, which can serve as either client or
server.
N-Tier Architecture