Embed Size (px)
Citation preview
Systems Management
Class Overview
Review Systems Management UML Quiz Details
IT Infrastructure
Hardware and Operating systems Software
• System Software (Server, db..etc)
• Application Software
Network (Hardware and Software) Resources
Factors Effecting IT Infrastructure
Size of the company Maturity Orientation of a firm and its IT
organization
IT Organization CIO (Chief Information Officer)
• Applications• Development
• Maintenance
• Infrastructure/Operations/Systems Management• Technical services
• Computer/Network Services
• Customer service/Help Desk
• Administration and Planning (PMO, HR, Training)
• IT Technical Architecture
• Security
• IT Audit
Systems Management
Availability of System Performance and Tuning Production Acceptance Change Management Problem Management Storage Management Network Management
Systems Management
Configuration Management Capacity Management Strategic Security Disaster Recovery Facilities Management
Major Components System Management Support
Data Center facility Server Hardware(Process, Memory) Server System Software Application Software Network Data Storage (Disk hardware, db
software)
Availability
The process of optimizing the readiness of production systems by accurately measuring, analyzing and reducing outages to those production systems
Associated terms• Uptime
• Downtime
• Slow Response
High Availability
Redundancy• Redundant power supplies, segmented disks
• Multiple processors Recoverability
• Overcome a momentary failure
• Fail-over Robustness
• Ability to withstand variety of forces
• Documentation and Training
Performance and Tuning
Goals• Maximize the Throughput
• Minimize the response time
How it is done• Tasks have continuous and ongoing nature
• Process is highly iterative
Improving performance
Server – number and size of buffer Disk storage – Prefetch algorithms and
high speed cache Data Base – run stats, Indexes
Production Acceptance
A methodology to consistently and successfully deploy application systems into production environment regardless of platform
Production Acceptance
Coordinate Implementation(applications, DBAs, Help Desk)
Ensure Capacity for the new system Ensure implementation is according to
company policies Documentation Ensure that back out procedures are in
place
Change Management
A process to control and coordinate all changes to a IT Production environment.
Problem Management
A process to identify, log, track, resolve and analyze problems impacting IT services
Storage Management
A process to optimize the use of storage devices and to protect the integrity of data for any media on which it resides
Storage Management
Back ups and recovery of data• Full backup
• Incremental backup
• Online backup
Disk Configuration • RAID (Redundant array of independent disks)
Network Management
A process to maximize the reliability and utilization of network components in order to optimize network availability and responsiveness
Network Management
Capacity Security
• Assure data and application security
Maintenance Trouble Shooting
Configuration Management
A process to ensure that the interrelation of varying versions of Infrastructure hardware and software are documented accurately and efficiently.
Documentation and training
Capacity Planning
A process to predict the types of quantities and timing of critical resource capacities that are needed within an infrastructure to meet forecasted workloads.
Capacity Planning
Network bandwidth Processors/Servers Storage capacity
Security
A process designed to safeguard availability,integrity and confidentiality of designated data and programs against unauthorized access, modification or destruction
Disaster Recovery
A methodology to ensure the continuous operation of critical business systems in the event of widespread or localized disasters to an infrastructure environment
Systems Management Tool
A systems management tool is anything that provides a way for all the component parts of an information technology system to share data about the system. If there is a problem in one part of the system, it can have a ripple effect on other parts of the system. The main component of virtually every systems management tool is a central event handler that continuously gathers all the available information about the system in real-time and immediately alerts the administrator when something
goes wrong.
Log files
UNIX• SYSLOG
Windows• Event Log
Applications• Can write to logs and generate alerts
Tool
Agent Manger (Central Event Handler) GUI/Display Manger Information base/Data base
Tools
CA Unicenter IBM Tivoli BMC PATROL HP OpenView
SNMP
Simple Network Management Protocol• Protocol used to manage devices on a
network
• Agent/Manger and MIB
• Retrieves data at fixed intervals by polling
• SNMP comes as part of many tools
UML
Phases of Systems development
Requirement analysis Analysis Design Programming Test
UML
Usable models• Accurate
• Consistent
• Easy to communicate
• Easy to change
• Understandable - simple
UML
UML can describe following systems• Information systems
• Technical Systems
• Embedded real time systems
• Distributed systems
• System software
• Business systems
Parts of UML
Views Diagrams Model Elements
Views
Use-case view• Functionality of the systems (Requirements)
Logical view• Systems behavior (Design)
Implementation view • Organization of the code (Development)
Process view – Performance Deployment view - Production implementation
Diagrams
Use-case view• Use case diagrams
Logical view• Class diagrams
• Object diagrams
• State diagrams
• Activity diagrams
• Interaction diagrams
Diagrams
Implementations view• Enhanced class and object diagrams
• Code and progress reports
Process diagrams• Activity diagrams
• Interaction diagrams
• State diagrams
Diagrams
Deployment view• Deployment diagram
Model Elements
Concepts used in the diagrams Representation for different elements in
the diagrams
UML
Dynamic Modeling
Dynamic Modeling
Behavior of the system Interaction between objects UML Diagrams
• State diagrams (State machines)
• Activity diagrams
• Interaction diagrams
Activity Diagram
Activity diagrams capture actions and results
Shows instance of use case Describe the Workflow
Activity1
Activity2Activity3
Activity5
Receive Order
Fill Order Send Invoice
Nextday delivery Ground DeliveryReceive Payment
Close Order
State Diagram
States object can have during its lifecycle
What events state to change
State diagram
State Name Activity Transition
State1
State2
-End1*
-End2*
Sequence Diagrams
UML provides a graphical means of depicting object interactions over time in Sequence Diagrams.
Object1
Message1
User Login Manager SecurityManger UserDataAccesObject
Login
ValidateUser
RequestUserDetails
ValidateUser
UserDetails
Results
Model Qualities
Capture essence of problem domain Goal oriented Easy to communicate Easy to maintain Consistent Uses good naming conventions Easy to integrate
AIT 600AIT 600 IT Infrastructure IT Infrastructure
Today’s Class OverviewToday’s Class Overview
AIT600 Course overview Class Structure Overview of the course topics Introductions IT Infrastructure Components Strategic planning Next Class
Course DescriptionCourse Description
A discussion and survey of enterprise-information system architectures including software systems, hardware, operating systems, databases, component technologies, networking, architecture patterns, and unified modeling language (UML). Discussions will include the review of case studies of information technology systems. An introduction to the systems development process, including the analysis, design, development, implementation, and post-implementation phases will also be provided
Ethernet
Server
ComputerComputer Computer
Minicomputer
Mainframe
ServerServer
Laptop
Pen computer
Scanner
Cloud
40000 ft view of IT infrastructure
UML
Unified Modeling Language Enterprise Architecture Systems development Design patterns
Text Books, Syllabus etc.Text Books, Syllabus etc.
IT Architectures and middleware, Britton UML2 Toolkit, Eriksson, H., Penker Course documents – Towson University
Blackboard
Course Documents
Blackboard Academic Suite
How do I enroll
https://bbweb.towson.edu
Access Code:CAIT600E_Spr08
(Write down URL and access Code)
Access code is case sensitive
Grading CriteriaGrading Criteria
Assignments(2)10% Quizzes(2) 10% Mid-term exam: 25% Final exam: 20% Research Paper 25% Presentation 10%
Final Grade
A - 90 and above B - Between 80 and 89 C – Between 70 and 79
Presentation TopicsPresentation Topics
Case Studies Case Analysis Current IT trends
•Open source software
•Wireless technologies – 802.11n, RFID
•Security – Biometrics
•HIPPA and SOX
Presentation DetailsPresentation Details
10 to 12 minutes Distribute the copies of the slides to the
class (Optional) Grading Criteria
• Content of Presentation - 50%
• Slides and Presentation - 50%
Research PaperResearch Paper
Research Paper details will be discussed in the next class.
Class Structure
Review of previous class topic Topic discussion Go over the topic Presentation Case study – Provides real world
examples Group Activity, Presentation, Quiz etc. Q & A
Overview of AIT600 TopicsOverview of AIT600 Topics
Course Topics Course Topics
IT Infrastructure and Planning Systems Management /IT Operations IT Architecture Applications development Current trends (Web Services, ERP etc.)
Enterprise systemsEnterprise systems
Enterprise Application Integration Business Processes Management
systems ERP EA Data Warehousing
UMLUML
Unified Modeling Language• Views
• Diagrams
• Model Elements
Questions???Questions???
IntroductionsIntroductions
Name Brief description of your occupation IT Experience
IT InfrastructureIT Infrastructure
Infrastructure ComponentsInfrastructure Components
Hardware & Operating Systems Software
• System Software
• Middleware
• Application Software Network Data Storage Resources IT Compliance and Governance
Ethernet
Server
ComputerComputer Computer
Minicomputer
Mainframe
ServerServer
Laptop
Pen computer
Scanner
Cloud
IT Infrastructure
Hardware
OS
Software
Database
Networks
Resources
IT Infrastructure
Hardware and Network(Ex:CPUs, data Storag, routers, switches, cables)
Opreating System(Ex:Windows, UNIX, Linux, Mac, Solaris, AIX, MVS,
Protocols)
System Software(Ex:Application Servers, DB Servers, .Net, J2EE)
Application Software(Software to Support Business)
USER(Not Part of Infrastructure)
SystemsManagement
ApplicationsDevelopmentand Support
Help Desk
ITManagement
HardwareHardware
Servers PCs – Desktops Handhelds Network devices – Routers, Cables Storage Devices – Disks, Tapes
Operating SystemOperating System
What an operating system does:• Interpreter between you and all SW/HW
• Controls internal components:• external devices
• Memory
• Monitors
• Modems
• Storage devices and the look and feel of user interface
Operating SystemsOperating Systems
Windows Macintosh OS IBM's MVS (OS/390, Z/0S) Unix Linux
SoftwareSoftware
System Software• Set of programs coordinating the activities and
functions of the HW and various programs throughout the system
• Application-independent software that supports the running of application software
• DBMS, RDBMS
• Also includes: Software for managing network, diagnostic, performance, etc.
SoftwareSoftware
Application Software• Consists of programs that help users solve
particular business problems
• Order entry systems, Payroll, HR, University Online Registration etc.
MiddlewareMiddleware
SW that connects applications to communicate
Ex: CORBA, COM
Data StorageData Storage
Database systems• Oracle
• SQL Server
Storage Networks• SAN – Storage Area Network
• NAS – Network Attached Storage
NetworkNetwork
Computer Networks• Networking is defined as concept of
connecting computers and other devices to enable sharing of resources
LAN, WAN, Internet
ResourcesResources
Operations/System Administration Network support Database administration Applications development and Support Help Desk
Role of ITRole of IT(Technology Perspective)(Technology Perspective)
Making sure systems are available for business
Delivering information systems needed for business on time and within budget
Maintaining IT Infrastructure
Role of ITRole of IT(Business Perspective)(Business Perspective)
Improve bottom line Better and Quicker services to
Customers Improve Productivity Reduce Costs Give competitive advantage
Strategic PlanningStrategic Planning
IT has a Strategic RoleIT has a Strategic Role
No distinction between Business and IT initiatives
IT is critical to growing business in the Internet era
For IT to deliver…For IT to deliver…
Strategic Planning Align Business with IT
Strategic PlanningStrategic Planning
Predict – Have a Vision• Company growth
• Competitive landscape
• Process and Technology changes
Risks• Obsolescence due technological changes
• Economic environment before implementation
How to planHow to plan
Understand the desired future state of the Company
Understand Present state Come up with a plan to close the gap
Basics Basics
Project prioritization Risk analysis Analysis of likelihood of changes in the
industry and technology
Planning Do’s & Don’tsPlanning Do’s & Don’ts
Gather requirements using proven methods• Talk to all levels of management
• Review the business processes
Start earlier and don’t be reactive Both business and IT plans should be
written collaboratively
Plan should have…Plan should have…
High level details Flexible to accommodate future changes Include infrastructure details, upgrades
and architectural details Review as needed
Aligning IT With BusinessAligning IT With Business
To survive challenges, organizations• Regrouping
• Restructuring
• Refocusing
Non-aligned companyNon-aligned company
People are not focused on what they do together
People hoard info People go off by themselves to develop ideas
and projects There is a lot of conversation about how we
need to communicate better There is a lot of finger pointing
Aligned CompanyAligned Company
Your success is a team success The corporate culture values
entrepreneurship risks are encouraged Failure is a part of the learning process People are applauded for sharing what they
learned from a failed hypothesis There are no rules or hierarchy about idea
generationSlide assistance courtesy of Sundhar Sarma
BPMand
ApplicationsDevelopment
Overview
Business Process Management Application Development UML – Class Diagrams Presentations
Different Business Processes
Finance and Accounting Asset management Business Planning Services Human Resources/Payroll Customer Relations Sales and Marketing
What is Business Process
One definition of business process could be a set of connected functions, where the connections are controlled by business rules. Those business rules are specific for an enterprise and specific at a certain point in time.
Need for Integration
Traditional Business• Designed for Internal use
• Individual processes
• People interacted with customers rather than processes and internal applications
Business partners or customers can interact with the business processes via the Web
Drivers for Integration
Technology Globalization Power of Consumer (B2B, B2C and
B2G)
Integration Methods
Infrastructure level• Moves data around enterprise
• Message oriented middleware (MOM) Data level
• Data transformation and Integration
• XML Business Process Level
• Business functions integration
Integration Technologies
EAI – Enterprise Applications Integration BPM – Business Process Management Enterprise Portals and Dash Boards Data Integration
BPM
Workflow• A person is presented with an electronic version of a
document he or she had to complete or approve or act upon
• People oriented Applications Integration
• Linked by middleware BPM
• Can be viewed as union of Workflow and Application Integration
BPMS
Technological implementation of BPM is called a Business Process Management system
Objectives• Ability to rapidly implement changes in business rules
and objectives
• Measure effectiveness of changes
• Define,change and implement business process in consistent way
Components of BPMS
Process Engine• Manages different activities/business functions
Resource Manager• Makes resources available for activities
Scheduler – Match time constraints and resources Audit Manger
• Tracking Security
Vendors and Products
BEA• BEA WebLogic Enterprise Platform
• WebLogic Portal
• WebLogic Integration
• WebLogic Server
Magic• IBOLT Integration suite
• iBOLT Studio
• iBOLT Server
• iBOLT Monitor
• iBOLT Portal
Applications Development
Planning Requirement Analysis Design Development Implementation
Planning
Identifying business value Analyze feasibility Develop work plan Staff the project Control and direct project
Requirement Analysis
Analysis strategy Gathering business requirements Requirements definition Process modeling Data modeling
Techniques
Interviews Meetings with stakeholders Prototyping Flow diagrams UML – Use Cases
Design
Design selection Architecture design Interface design Data storage design Program design
Design
Methodologies• Prototyping (Proof of concept)
• JAD – Joint application Design
• UML
• Patterns
Patterns
Describe successful solutions to common software problems
Recurring solutions to a standard problem
Good Patterns arise from practical experience
Recognizes the human dimension in software development
MVC
Model-View-Controller Pattern• Model
• Business logic
• View• User interface logic
• Controller• Interaction control logic
JAD
Executive Sponsor• Project owner
• Makes Decisions Project Lead
• Development team lead Facilitator
• Chairs meetings and directs traffic Documentation Expert Participants and Observers
Development
CASE Tools • Computer Aided Software Engineering
IDEs and Frameworks Component based development
Implementation
Construction - Development• Program building
• Program and system testing
Installation• Conversion strategy
• Training plan
• Support plan
Deliverables
Systems Request Feasibility Analysis Work plan System Proposal System Specification System ready for Users Warranty period and Maintenance
Methodologies
Application development methodologies• Waterfall
• Parallel development
• RAD
• XP
• Component based development
Waterfall Method
Parallel development
Component Based Development
Component-based software development (CBSD) focuses on building large software systems by integrating previously-existing software components
Components include• Commercial off-the-shelf components
• In house developed components
CBSD Activities
Component Qualification• Discovery and Evaluation
Component adaptation• Customization
Assembling components into system System Evolution
• Support and Maintenance
RAD
RAD (rapid application development) is a concept that products can be developed faster and of higher quality through:
• Gathering requirements using workshops or focus groups
• Prototyping and early, reiterative user testing of designs
• The re-use of software components
• A rigidly paced schedule that defers design improvements to the next product version
• Less formality in reviews and other team communication
• Mostly uses CASE tools
XP
Extreme Programming (XP) is a pragmatic approach to program development that emphasizes business results first and takes an incremental, get-something-started approach to building the product, using continual testing and revision.
Lightweight methodology as per Kent Beck Don’t have get it right first time
Best Practices
Develop Software Iteratively Manage Requirements Use Component based architectures Visually model software Verify software quality Control changes to software
CMMI
The Capability Maturity Model (CMM®) Integrated (CMMISM) is for projects or organizations that want to use common, integrated, and improving processes for Systems and Software. It is a process improvement method that provides a set of best practices that address productivity, performance, costs, and stakeholder satisfaction.
http://www.sei.cmu.edu/cmmi/
Questions???
Class Diagrams
Class Diagram
+getGrades() : string+getName() : string+getAddress() : string
-name : char-studentId : int-city : char
Student
Class
Automobile Class
Components
Name Attributes Operations/Methods Associations
Association
When two classes are connected to each other in any way, an association relation is established.
Association
Class1
Class2 Class3
End1
End2
End3
End4
Multiplicity
University StudentEnd1 End2
AITClass InstructorEnd3 End4
Aggregation
When a class is formed as a collection of other classes, it is called an aggregation relationship between these classes. It is also called a "has a" relationship.
AggregationClass1
Class2 Class3Class4
Composition
Composition is a variation of the aggregation relationship. Composition connotes that a strong life cycle is associated between the classes
Composition
Class1
Class2
-End11
-End2*
Generalization(Inheritance)
Also called an "is a" relationship, because the child class is a type of the parent class. Generalization is the basic type of relationship used to define reusable elements in the class diagram. Literally, the child classes "inherit" the common functionality defined in the parent class.
Generalization
Vechicle
Car Boat Truck
Interface
Interface: An interface is a variation of a class. An interface provides only a definition of business functionality of a system. A separate class implements the actual business functionality.
Package
Package: A package provides the ability to group together classes and/or interfaces that are either similar in nature or related. Grouping these design elements in a package element provides for better readability of class diagrams, especially complex class diagrams.
Package
Class Diagram Steps
Identify classes Identify attributes and operations Draw relationships between classes
Modeling Language
Syntax Semantics
EAIEnterprise Architecture
Overview
Review – SOA, Web Services EAI Enterprise Architecture UML – Class Diagrams Midterm Presentation
EAI
Enterprise Application Integration EAI combines separate applications into a co-
operating federation of applications. Ex: Connecting apps through a central message-
routing hub, similar to middleware tools like IBM MQSeries
EAI tools are also equipped to:• parse and translate data• automatically route info according to business processes
Advantages of EAI Tools
Speed Cost savings Flexibility(?) Can save as much as 80% of the cost of
doing a custom integration project ROI depends on volume
Drivers of EAI
Globalization Mergers and acquisitions Business demands
Integration Methods
Data-level integration User interface level integration Applications level integration Method level integration
Integration Components
Common XML Schema Data Transformation Define processes
EAI Architectures
Point to Point Middleware bus
EAI Best Practices
Building with deployment in mind Profile performance early and often Build a Traceable system
• Runtime debugging
Review secondary scenarios
Enterprise Architecture
References for following slides: http://www.opengroup.org/architecture/togaf8-doc/arch/chap02.html
http://www.zifa.com
http://www.enterprise-architecture.info/index.htm
Enterprise Architecture
The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution.
Conceptual tool that assists organizations with the understanding of their own structure and the way they work. It provides a map of the enterprise and is a route planner for business and technology change.
Use of EA
Systematic IT Planning Better IT Architecting Enhanced decision making
EA Models
Objectives and goals. Processes and organization. Systems and data. Technology used.
Different Views of EA
Business Perspective Applications Perspective Information Perspective Technology Perspective
Business Perspective
The enterprise's high-level objectives and goals.
The business processes carried out by the entire enterprise, or a significant portion of the enterprise.
The business functions performed. Major organizational structures. The relationships between these
elements.
Application Perspective
Descriptions of automated services that support the business processes.
Descriptions of the interaction and interdependencies (interfaces) of the organization's application systems.
Plans for developing new applications and revising old applications based on the enterprises objectives, goals, and evolving technology platforms.
Information Perspective(Data Perspective)
Standard data models. Data management policies. Descriptions of the patterns of
information production and consumption in the organization
Technology Perspective
Desktop and server hardware. Operating systems. Network connectivity components. Printers. Modems.
Different views
Conceptual View• Users view of the system
• Functional Requirements Logical View
• How functionality is implemented
• Architecture of the application Physical View
• Illustrate the specific implementation components and their relationships
Implementation View
EA Frameworks
Zachman Framework TOGAF
• The Open Group Architectural Framework
FEAF – Federal EA Framework C4ISR
• Command, Control, Communications, Computers,
Intelligence, Surveillance and Reconnaissance EA Framework IEEE 1471
TOGAF1. Business (or business process) architecture: This defines the business strategy, governance, organization, and
key business processes. 2. Application architecture: This kind of architecture provides a blueprint for the individual
application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.
3. Data architecture: This describes the structure of an organization’s logical and physical
data assets and data management resources. 4. Technology architecture: This describes the software infrastructure intended to support the
deployment of core, mission-critical applications. This type of software is sometimes referred to as “middleware.”
Zachman Framework The Zachman Framework is a framework providing a
view of the subjects and models needed to develop a complete Enterprise architecture.
The Zachman Framework is a widely used approach for developing and/or documenting an enterprise-wide information systems architecture. Zachman based his framework on practices in traditional architecture and engineering. This resulted in an approach, which on the vertical axis provides multiple perspectives of the overall architecture, and on the horizontal axis a classification of the various artifacts of the architecture.
Zachman Framework
1. Scope (Ballpark view): Definition of the enterprise’s direction and business purpose. This is an industry view, concerned with the things that define the nature and purpose of the business. This is necessary to establish the context for any system development effort.
2. Model of the business (Owner’s view): This defines — in business terms — the nature of the business, including its structure, functions, organization, and so forth.
3. Model of the information system (Architect’s view): Defines Businesses described in Owner’s view
Zachman framework 4. Technology model (Designer’s view): This describes how
technology may be used to address the information processing needs identified in the previous rows. Here relational databases are chosen over network ones (or vice versa), kinds of languages are selected and program structures are defined, user interfaces are described, and so forth.
5. Detailed representations (Builder’s view): This is a view of the program listings, database specifications, networks, and so forth that constitute a particular system. These are all expressed in terms of particular languages.
6. Functioning system: Finally, a system is implemented and made part of an organization.
Users of EAClientAcquirerOwnerUserOperatorArchitectSystem EngineerDeveloperDesignerBuilderMaintainerService ProviderVendor
EA Tools
Model Store Manage Distribute/Share
Class Diagrams
Questions ??
Computer NetworksComputer Networks
Courtesy of Sundhar Sarma
Class Overview
Review of IT Infrastructure Case Study Research Paper Assignment Computer Networks Next Class
Review
Components of IT Infrastructure Importance of Strategic Planning Strategic plan steps Risks associated with Strategic Planning
Case Study
Model for Research Paper• Goals and Objectives
• Technology projects to meet the business goals and objectives
• Schedule
• Benefits
Research Paper Specific goals and objectives Current IT infrastructure – Should include Hardware,
Network, software details Summary of Recommendations Proposed IT infrastructure Implementation schedule and other issues
expected/anticipated Criteria to be used for selecting components and tools Important decisions taken and your recommendations
(with reasoning)
Research Paper Due date
Refer to syllabus for the due date
Internet
Clients
Servers
Network components?
Resource SharingResource Sharing
Networking Networking is defined as concept of
connecting computers and other devices to enable sharing of resources
NetworkNetwork
A group of Computers and other devices connected together is called a Network
NetworkNetwork
Computers that are part of the network share• Data
• Application Software
• Messages
• Hardware resources (Processing power)
• Peripherals Printers, modems…etc)
Benefits of NetworkingBenefits of Networking
Decentralized data processing Sharing information is easy and faster Optimum resource utilization (Ex.
Printers, Disk drives) Sharing Applications
Any other benefits?
Components of NetworkComponents of Network
Servers• File and Print Server
• Application Server
• Mail Server
• Directory Services Server Clients - Desk Tops, Laptops Medium – Cable, RF, Satellites Peripherals – Printers, disk drives, modems,
Routers, Switches
Software Components …
Network TypesNetwork Types( Range)( Range)
LAN – Local Area network• Communication range is confined to a building or
cluster of buildings
MAN – Metropolitan Network• Communication range is spread across a city or state
• Two or more LANs connected together
WAN – Wide area network• Range spreads across the country or countries
• Linking together LANs or MANs
Node-Based NetworksNode-Based Networks(Technology)(Technology)
Peer-to-Peer Networks Server Based Networks
Peer to Peer
Peer-to-Peer NetworkPeer-to-Peer Network
All computers on the network are equals Roles change based on which computer
has data/application to share Workgroup Simple, Inexpensive to install and
maintain Users are administrators
Sever Based
Server Based NetworkServer Based Network
Dedicated servers Handles large number of clients Provides better data security Provides for easy back up of data Redundancy is possible Easily scalable
Combination NetworkCombination Network
Server based + Peer to Peer network
Combination Network
Network TopologiesNetwork Topologies
Physical layout of the network components
Topology determines• Arrangement of computers, cables and other
resources in a network
• Communication method also dependent on topology
TypesTypes
Basic types of topologies• Point to Point
• Bus
• Ring
• Star
Point-to-Point TopologyPoint-to-Point Topology
Simplest of the physical layouts of network devices 2 devices (nodes) have a single path for data to
travel between them Nothing breaks up the path Similar to how terminals connected to mainframes Basic building block of larger, more complicated,
topologies
BUS TOPOLOGY
Bus TopologyBus Topology
All devices share a common wire to transmit and receive data
Each device can communicate directly with all other devices on the network
Cheaper and easier to install Difficult to troubleshoot Devices all share a common cable for
transferring data in a bus topology
STAR
Star TopologyStar Topology
Has a central hub or computer system Other devices are located at the end of
communication lines that originate from the central hub or computer system
May be sophisticated enough to disconnect any misbehaving machine
Require more cable than a simple bus topology Troubleshooting easier than bus topology
RING TOPOLOGY
Ring TopologyRing Topology
Ring is created to which each device (workstation, server, etc.) is attached
Special signal, called a token, travels around this ring visiting each machine, letting it know that it is that machine’s turn to transmit
Since token visits every node, everyone gets a chance to transmit
Token ring LANs are the most sophisticated, fault tolerant (FDDI)
Hybrid TopologyHybrid Topology
Network combination of several different topologies
Require special management tools capable of interacting with several different types of LAN environments
ProtocolsProtocols
Data exchange performed by network operating system using set of rules known as protocols
Protocol• Procedure (and rules) for communication
between hardware and software
OSI Model
APPLICATION
PRESENTATION
SESSION
TRANSPORT
NETWORK
DATALINK
PHYSICAL
APPLICATION
PRESENTATION
SESSION
TRANSPORT
NETWORK
DATALINK
PHYSICAL
APPLICATION
PRESENTATION
SESSION
TRANSPORT
NETWORK
DATALINK
PHYSICAL
packetH T
packetH T TH
packetH T THH T
OSI Model
ProtocolsProtocols
NFS• Network file system
• Allows applications on one computer to access files on a remote computer
NetBIOS• Used to locate nodes(resources) by name with the
help of a naming system
• Acts as a interface between two networks
AppleTalk
TCP/IPTCP/IP
IP – (Internet Protocol) is responsible for moving packet of data from node to node. IP forwards each packet
based on a four byte destination address (the IP number). TCP – (Transmission Control Protocol) is
responsible for verifying the correct delivery of data from client to server. Data can be lost in the intermediate network. TCP adds support to detect errors or lost data and to trigger retransmission until the data is correctly and completely received.
TCP/IP Stack
APPLICATIONHTTP HTTPS DNS FTP SMTP
TRANSPORTTCP UDP
NETWORKIP
NETWORK INTERFACE
Useful commands
Ping• http://us.geocities.com/Petsburgh/1174/help/pingtr/ping.html
• http://usertools.plus.net/tutorials/id/34
Ipconfig • http://www.ncsu.edu/resnet/windows/ipconfig/
• http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/pref_tts_vfra.mspx?mfr=true
Tracert http://support.microsoft.com/kb/314868
InternetInternet
The Internet is a interconnected set of networks and millions of computers across the world that all work together to share information.
InternetInternet
The Internet consists of the following groups of networks:
• Backbones: Large networks that exist primarily to interconnect other networks. Currently the backbones are large commercial backbones.
• Regional networks connecting, for example, universities and colleges.
Who Controls WebWho Controls Web
The World Wide Web Consortium (W3C) sets the standards for HTML and other specifics of the Web.
The Internet Engineering Task Force (IETF) focuses on the evolution of the Internet with a specific eye toward keeping the Internet running smoothly as a whole.
The Internet Engineering Steering Group (IESG) is a related organization responsible for managing IETF activities and the Internet standards process.
The Internet Architecture Board (IAB) is responsible for defining the overall architecture of the Internet (the backbone and all the networks attached to it), providing guidance and broad direction to the IETF.
The Internet Society (ISOC) is a supervisory organization made up of individuals, corporations, nonprofit organizations, and government agencies from the Internet community. The group comments on Internet policies and practices and oversees a number of other boards and task forces--including the IAB and IESG--dealing with Internet policy issues.
The Internet Assigned Numbers Authority (IANA) and the Internet Network Information Center (InterNIC) lead the organizations responsible for assigning IP addresses and domain names, respectively.
IPv6IPv6
128 bits address To better support real time audio and
video To better serve complex application
needs Network security is based on filtering and
IPsec, suitable for faster networks
ETHERNETETHERNET
Ethernet is the most widely-installed local area network (LAN) technology
Specified in a standard, IEEE 802.3 Devices are connected to the cable and compete for
access using a Carrier Sense Multiple Access with Collision Detection (CSMA/CD) protocol
10Base-T (10 Mbps) Fast Ethernet ( 100 Mbps) Gigabit Ethernet (1 gigabit per second)
IEEE 802IEEE 802
LMSC (or IEEE Project 802) develops LAN and MAN standards, mainly for the lowest 2 layers of the Reference Model for Open Systems Interconnection (OSI). LMSC coordinates with other national and international standards groups, with some standards now published by ISO as international standards. There is strong international participation, and some meetings are held outside the U.S.
Network SecurityNetwork Security
Network Administrator Share Level Security
• Password is assigned to resource
User Level Security• Access rights to each user
• Server determines whether to give access to a resource or not
Network SecurityNetwork Security
Confidentiality Integrity Availability
Network SecurityNetwork Security
Access control Security Policy Encryption Firewall
Questions???
ERP
What is ERP
An enterprise resource planning (ERP) system is a sophisticated software package that aims to integrate and run an organization’s core business and major business processes. Typically, such a system supports and automates a company's business processes and functions such as order entry, procurement, finance, manufacturing, warehousing, shipping, human resources, etc.
ERP Objectives
Enterprise-wide integration Fix broken processes Integrate vendors and customers Increase efficiency Gain competitive edge
Need for Integration and ERP
Lack of integration because data was scattered across a variety of legacy systems
Incompatibility between systems Inconsistent and/or redundant data Inability to provide real-time enterprise-wide
information Inability to support easy consolidation of
groups
Need …ERP
Limited scalability and upgrade limitations of existing systems (hardware, software and
functionality) Integration problems for enterprise-wide
upgrades Need to deal with multiple vendors High cost of maintenance due to disparate
and obsolete systems
Benefits of ERP Systems Business
• Supports companies with global operations
• Accommodates rapidly changing business conditions
• Enables companies to better understand their business
• Meets customer demands involving multiple locations and interrelated items
Internal integration• Integrates company-wide data and information
• Enables easy consolidation of groups due to availability of centralized data in one system
• Combines functions of many applications, that an organization needs to operate, and integrates them
Benefits… Flexibility
- Permits addition or upgrade of other system components or functionality due to open
• system architecture
• Any change can be implemented for all locations/groups through a configuration
• change at one central point
• Flexibility for changes for both business users and IT Reporting and Information access
• Availability and easy access to transaction flows and document history
• Standard reports are available but customized reports can also be developed
• Provides drill down capability, i.e., access to detailed data
Benefits…
Technical• Provides real-time information
• Portable across operating systems, databases and presentation formats
• Provides high reliability Tangible Benefits
• Inventory reduction
• Personnel reductions
• Productivity improvements
• Order management improvements
ERP Problems and Challenges
Implementation Time and Cost Customization and Consulting Cost Total Cost of Ownership Inadequate Preparation Fear of failure
SAP Modules Asset Management (AM) Financials (FI) Controlling (CO) Human Resources (HR) Plant Maintenance (PM) Production Planning (PP) Project System (PS) Quality Management (QM) Sales and Distribution (SD) Materials Management (MM) Service Management (SM) Industry Specific Solutions (IS) Business Workflow (WF) Basis (includes ABAP/4 ® programming language) (BC)
Financial & Asset Accounting
General ledger Accounts receivable Accounts payable Asset accounting Leased assets Special purpose ledger Legacy consolidations Financial accounting information system
Human Resources
Personnel administration• Payroll
• Benefits administration
• Recruitment
• Time management
• Travel management
• Compensation management Personnel planning and development
• Organization management
• Training
Materials Management
Procurement Inventory management Materials planning Vendor evaluation Invoice verification Warehouse management Logistics information system Consumption-based planning
Sales and Distribution
Quotations Sales order management Pricing Shipping Billing Foreign trade Sales information system Availability check and requirements Computer aided sales
SAP Architecture
Multi-Tier architecture• Database layer
• Application layer
• Presentation layer
Database layer
Central Storage of Data Data Base Server
• Oracle
• SQL Server
• Informix
Application Layer
Application Server Business logic/rules
Presentation Layer
ERP Software GUI
Benefits of Architecture
Scalability Work load distribution (load balancing) Ease of use (GUI)
Supported Platforms for SAP
Windows UNIX LINUX AS/400
ERP Packages
SAP People Soft (Oracle) Baan JD Edwards Oracle Financials
Project Failures
Delays: implementation took much longer than expected
Cost overruns: cost to implement was much greater than anticipated
Cancellations: after spending years and millions of dollars
Suggestions for Success
Training Operational Tests (Pilot project) Check references Phased implementation Realistic timelines
Basic Steps
Company should be ready for the big change
Develop implementation plan Develop the budget Select the implementation partners
Implementation roadmap
Modeling• To be business process
Mapping• ERP processes to existing process
Gap Analysis Project Scope – what can be implemented Customizing Testing
Implementation Approaches
Big bang approach• All modules required by the company are
implemented
Phased approach• Step by step implementation
Implementation Methodologies(SAP)
Conventional Methodology• Procedural model
ASAP Methodology
Conventional Methodology
Organization and conceptual design (logical design)
Detailed design and system setup (physical design)
Go-live preparations Productive operations
Drawbacks
Lengthy implementation periods Scope continued to increased as
analysis dragged on
ASAP(Accelerated SAP)
Components, Tools and Accelerators Tools
• Business Engineer• Modeling tool
• Project Estimator
• Implementation Assistant
• Accelerator• Examples, checklists, templates
Conventional Versus ASAP
Slow implementation Extensive analysis Comprehensive Significant employee
participation More customization
Fast implementation No in-depth analysis Focused and narrow Consultants
Minimal Customization
Case Study URLhttp://www.cfo.com/article.cfm/2987370/1/c_2984788?f=RequiredReadingFavorites
Information Management
References
http://www.dwinfocenter.org/ http://www.cio.com/sponsors/
030104emc/complete.pdf Some of the content of this presentation
is based on content from the above URLs.
Data Warehouse Definitions
A data warehouse is a copy of transaction data specifically structured for querying and reporting (& Analysis)
A data warehouse is simply a single, complete, and consistent store of data obtained from a variety of sources and made available to end users in a way they can understand and use it in a business context
Why Data Warehouse
To perform server/disk bound tasks associated with querying and reporting on servers/disks not used by transaction processing systems
To use data models and/or server technologies that speed up querying and reporting and that are not appropriate for transaction processing
To provide a repository of "cleaned up" transaction processing systems data that can be reported against and that does not necessarily require fixing the transaction processing systems
Cont…
To provide a repository of transaction processing system data that contains data from a longer span of time than can efficiently be held in a transaction processing system and/or to be able to generate reports "as was" as of a previous point in time
To prevent persons who only need to query and report transaction processing system data from having any access whatsoever to transaction processing system databases and logic used to maintain those databases
Characteristics of Data Warehouse
Subject-Oriented• Ex: Customer related data from different systems
Integrated• Integrate disparate data
Non-volatile• Once data is entered it is almost never changed
Time Variant• Timestamp the data
Data Warehouse Vs Operational System
Mostly used by management
Supports strategic direction
Used for on-line analysis
Historical data
Used by customers and front line staff
Supports day to day operations
Used for transaction processing
Current data
Critical success factors An Identified, involved user community
• JAD Executive sponsorship – (money and say so) A balanced project team – (people with the right skill
set) Incremental approach – (little at a time) A well designed architecture
Data Warehouse Tools
ETL• Extract, Transform and load
Data Mart• Miniature data warehouse
• Built for solving a specific problem OLAP
• Online analytical processing Data Mining (Web data mining)
• Tool used to apply Artificial Intelligence to the analysis of data
Data Warehouse Tools
Oracle Informatica IBM SAS Institute Thinking Machines Siebel
Decision Support System
A decision support system or tool is one specifically designed to allow business end users to perform computer generated analyses of data on their own.
DSS
We cannot say that decision support systems or tools necessarily support the making of decisions
DSS helps user to make decision rather than making decision
Data warehousing and decision support systems and tools do not necessarily go hand in hand
ILM
Information Lifecycle Management A strategy that uses people, processes
and technology to store and tap critical business data throughout its lifespan of value.
The idea of managing the entirety of an enterprise's data throughout its useful life
Need for ILM
Explosive growth of data Eliminate Manual processes Dispersed enterprise data Regulatory Compliance
• Sarbanes-Oxley Act – (hold upper management responsible)
• HIPPA (get info about patients) Reducing costs
New challenges
Store and Retrieve • Email
• Pictures
• Video
• Audio data
ILM Steps
Improve classification• Inventory what you have
Leverage existing assets Automate the processes based on
Company and regulatory compliance requirements
Tiered storage based on value
Description of data Data element category (e.g., regulated content,
internal, unprotected). Data element ownership (e.g., business unit,
position title). (group ownership/permissions) Trigger events that stimulate a given action Description of action(s) required to manage content Retention requirements Access requirements Security requirements Disposal requirements
ILM
EMC Corp Veritas Software Corp HP
ILM
ILM is a on-going Process
Case study links
Case studies• http://www.ciol.com/content/search/
showArticle.asp?arid=35360
• http://www.saberconsulting.com/case-canon.htm
Systems Management
Part II
Class Overview
On demand Computing ITIL UML Intro to IT Architectures Quiz
Review
Storage Management• Back ups
• Recovery
• Storage Capacity/Performance Management• Magnetic Disks, Digital Linear tapes, Advanced
Intelligence Tapes
• SAN – Storage Area Network
• NAS – Network Attached Storage
On demand Computing
Enhanced levels of business alignment with IT
Being proactive Other terms used are
• Adaptive Infrastructure
• Utility Computing
IT Evolution as per EMA
Active Infrastructure Management Efficient Infrastructure Management Responsive Infrastructure Management Business-driven Infrastructure
Management
ITIL
Information Technology Infrastructure Library• UK Office of Commerce Govt.
• Guidelines for IT Infrastructure Services
• Integrated, Process based, best practice framework for managing IT Infrastructure
• Open source
ITIL Service Support
Service desk (Help desk)• Single point of contact between users and IT
service Organization Incident Management
• Restore process as early as possible and minimize the impact to business
Problem Management• Performs Proactive prevention
ITIL Service Support
Change Management• Standardized methods and procedures
• Improve day to day operations Release Management
• Production acceptance Configuration Management
• Identifying, Controlling, maintaining and verifying configuration items
ITIL Service Delivery
Availability Management• Cost effective and sustained level of service
Capacity Management• Planning, implementing and running the
process
IT Service Continuity Management• Disaster Recovery
ITIL Service Delivery
Service Level Management• Eradicate poor service
• Develop strong relationship with customer
Financial Management• Budget planning, IT Accounting and charging
Security Management ICT Infrastructure Management
On Demand Vendors
Computer Associates HP IBM Microsoft
Products
DSI – Dynamic Systems Initiative • From Microsoft
• Self Managing Windows Environment Websphere (new version )
• From IBM
• Manage applications running on different servers as if running on single environment
VM Ware Unicenter Network and Systems Management
• From CA
• Track IT infrastructure capacity
Advantages of On Demand
Cut Costs Reduce Complexity (?) Better Control Resources
UML
Phases of Systems development
Requirement analysis Analysis Design Programming Test
UML
Usable models• Accurate
• Consistent
• Easy to communicate
• Easy to change
• Understandable - simple
UML
UML can describe following systems• Information systems
• Technical Systems
• Embedded real time systems
• Distributed systems
• System software
• Business systems
Parts of UML
Views Diagrams Model Elements
Views
Use-case view• Functionality of the systems (Requirements)
Logical view• Systems behavior (Design)
Implementation view • Organization of the code (Development)
Process view – Performance Deployment view - Production implementation
Diagrams
Use-case view• Use case diagrams
Logical view• Class diagrams
• Object diagrams
• State diagrams
• Activity diagrams
• Interaction diagrams
Diagrams
Implementations view• Enhanced class and object diagrams
• Code and progress reports
Process diagrams• Activity diagrams
• Interaction diagrams
• State diagrams
Diagrams
Deployment view• Deployment diagram
Model Elements
Concepts used in the diagrams Representation for different elements in
the diagrams
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
303
A Tutorial on the
Zachman Framework for
Enterprise Architecture
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
304
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Zachman Framework
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
305
Zachman Framework
Row 1 – ScopeExternal Requirements and DriversBusiness Function Modeling
Row 2 – Enterprise ModelBusiness Process Models
Row 3 – System ModelLogical ModelsRequirements Definition
Row 4 – Technology ModelPhysical ModelsSolution Definition and Development
Row 5 – As BuiltAs BuiltDeployment
Row 6 – Functioning EnterpriseFunctioning EnterpriseEvaluation
1
2
3
4
5
6
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
306
Framework Rules
Rule 1: Columns have no order
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
Rule 2:
Each column has a simple, basic model
Rule 3:
Basic model of each column is unique
Rule 4:
Each row represents a distinct view Rule 5:
Each cell is unique
Rule 6:
Combining the cells in one row forms a complete description from that view
Basic Model = Entities and Relationships
EntityRelationshipEntity
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
307
Zachman Framework – Row 1Scope/Planner’s View
External Requirements and Drivers
Business Function Modeling
Motivation/WhyBusiness goals, objectives and performancemeasures related to each function
Function/HowHigh-level business functions
Data/WhatHigh-level data classes related to eachfunction
People/WhoStakeholders related to each function
Network/WhereVA locations related to each function
Time/WhenCycles and events related to eachfunction
1 Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
308
Zachman Framework – Row 2Enterprise Model/Designer’s View
Business Process Models Business Function Allocation Elimination of Function
Overlap and Ambiguity
Motivation/WhyPolicies, procedures and standards for eachprocess
Function/HowBusiness processes
Data/WhatBusiness data
People/WhoVA roles and responsibilities in eachprocess
Network/WhereVA locations related to each process
Time/WhenEvents for each process and sequencingof integration and process improvements
2
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
309
Zachman Framework – Row 3System Model/Designer’s View
Logical Models Project Management Requirements Definition
Motivation/WhyVA policies, standards and proceduresassociated with a business rule model
Function/HowLogical representation of informationsystems and their relationships
Data/WhatLogical data models of data and datarelationships underlying VA information
People/WhoLogical representation of access privilegesconstrained by roles and responsibilities
Network/WhereLogical representation of the distributedsystem architecture for VA locations
Time/WhenLogical events and their triggered responses constrained by business events and their responses
3
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
310
Zachman Framework – Row 4Technology Model/Builder’s View
Physical Models Technology Management Solution Definition and
Development
Motivation/WhyVA business rules constrained by informationsystems standards
Function/HowSpecifications of applications that operateon particular technology platforms
Data/WhatDatabase management system (DBMS) typerequirements constrained by logical data models
People/WhoSpecification of access privileges tospecific platforms and technologies
Network/WhereSpecification of network devices and theirrelationships within physical boundaries
Time/WhenSpecification of triggers to respond to systemevents on specific platforms and technologies
4
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
311
Zachman Framework – Row 5As Built/Integrator’s View
As Built Configuration Management Deployment
Motivation/WhyVA business rules constrained by specific technology standards
Function/HowPrograms coded to operate on specific technology platforms
Data/WhatData definitions constrained by physical data models
People/WhoAccess privileges coded to control access to specific platforms and technologies
Network/WhereNetwork devices configured to conform to node specifications
Time/WhenTiming definitions coded to sequence activities on specific platforms and technologies
5
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Contextual
Conceptual
Logical
Physical
As Built
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
312
Zachman Framework – Row 6Functioning Enterprise/User’s View
Functioning Enterprise Operations Management Evaluation
Motivation/WhyOperating characteristics of specific technologies constrained by standards
Function/HowFunctioning computer instructions
Data/WhatData values stored in actual databases
People/WhoVA personnel and key stakeholders working within their roles and responsibilities
Network/WhereSending and receiving messages
Time/WhenTiming definitions operating to sequence activities
6
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Contextual
Conceptual
Logical
Physical
Integrated
Functioning
Why
Why
Who
Who
When
When
Where
Where
What
What
How
How
April 10, 2023 A Tutorial on the Zachman Enterprise Architecture
Framework
313
VA Zachman Framework Portal
IT Architectures
Overview
Utility Computing Review Components of a system IT Architectures Review of Quiz Intro to Middleware UML – Use Cases
Components of System
Database Transactions Batch jobs
Databases
Hierarchical Database Relational Database Object Oriented Database
Relational Database
Tables Views Normalization(Rules and Constraints)
SQL
DDL - Data definition language DML - Data Manipulation language DCL – Data Control language
Transaction
Logical unit of work Commit and Rollback
Transactions
ACID• Atomic
• Consistent
• Isolation
• Durable
IT Architecture
A Guideline A Pattern A Formal model
IT Architecture
Different layers of application• Presentation layer
• Business logic
• Data base
Purpose of Architecture• Determine what parts of the application
software will be assigned to what hardware.
IT Architecture
Hardware options:• Clients
• Input/output devices employed by users
• PCs, laptops, handheld devices, cell phones
• Servers• Larger computers storing software
• Accessible by many users
Different Architectures
Mainframe Architecture File Sharing Architecture Client/Server Architecture Two Tier Architecture Multi-Tier Architecture Service Oriented Architecture
Mainframe Architecture
All intelligence/processing in Central Host Computer
Access thru terminals, PCs and UNIX workstations
No good GUI Difficult to access distributed databases
Mainframe
Terminals
Mainframe Architecture
File Sharing Architecture
File Server Files downloaded by servers to PCs Good GUI Data is processed on PCs Data Traffic and Update contention
File Sharing
ApplicationFile
Server
Client/Server Architecture
Database server Database Management System (DBMS) Multiple clients updating shared
database
Client Server
GUIApplication
DB Access thruSQL
Data Base
Two Tier Architecture
Database management server Processing split between Client and
Server Stored Procedures and Triggers
Two Tier Architecture
GUIApplication Database
Application (Stored
Procedures/Triggers)
Multi-Tier Architecture
Middle tier added between client and database
Improves Performance/Handle large number of users
Three Tier Architecture(Multi-tier n-Tier)
GUI
ApplicationDatabase
Stored procedures/Triggers
Multi-Tier Architecture
ApplicationDatabase
Stored procedures/Triggers
Web Server
Pros and Cons
Benefits• Separates processing
to better balance load on different servers
• More scalable
Limitations• Greater load on the
network
• More difficult to program and test
Order Entry System
Order Entry Warehousing (Inventory Management) Accounts/Billing Shipping
Distributed Transactions
A transaction involving multiple transaction managers. In a distributed transaction environment, a client application may send requests to several servers resulting in resource updates at multiple resource managers. To complete the transaction, the transaction manager for each participant (client, servers, and resource managers) must be polled to coordinate the commit process for each participant within its domain.
Updating multiple databases simultaneously
Two Phase Commit
Protocol for Distributed Transaction Processing
Data Integrity and accuracy
Questions???
Middleware
Overview
Middleware CORBA and DCOM MOM Internet and Session management
Why Middleware
Programs communicating across network with another program
Complex programming
Issues
Client to Server Socket communication• Names
• Addresses
• Protocols
• Ports
• Complex programming
• Repetitive in nature
Issues
Different data representation
RPC Paradigm
Divides tasks into sets Shorter procedures to handle each set Procedures with Input and Output
parameters
RPC
Client Program + Stub Server Program + Skeleton IDL Marshalling – Data Translation
RPC Middleware
ONC RPC/Sun RPC• Has eXternal Data Representation (XDR)
DCE RPC• Distributed computing environment
• Client can access more than one server MSRPC
• Similar to DCE RPC
Object Oriented Middleware
Method Invocation• Get reference to the object
• Call the object’s method
Object Oriented Middleware
CORBA MSRPC2 COM/DCOM Java RMI
CORBA
Common Object Request Broker Architecture
Standard From OMG – Object Management Group• Open, vendor-independent architecture and
infrastructure that applications use to work together over networks
CORBA Overview
Interface to server object is defined using IDL
Client use IDL Interface to invoke an operation
Interface definition is used to marshal and unmarshal arguments and results
CORBA Parts
IDL ORB – Object Request Broker IIOP – Internet Inter-ORB protocol
Remote Invocation
Client obtains object reference Client invokes the operation ORB discovers that this is a remote
invocation Routes it to remote ORB using IIOP
COM/DCOM
From Microsoft Has its own IDL based on DCE ORPC – Object remote procedure call as
protocol
DCOM
Interface is a group of related functions Client gets pointer to the Interface Type library describes Interfaces and
parameters
Java/RMI
RMI - Remote method Invocation Remote Java Object methods invoked
from another JVM across a network
Message-Oriented Middleware
Distributed Systems Message queues provide temporary
storage Asynchronous mechanism
Products
MSMQ IBM MQSeries BEA Tuxedo/Q
Where to use
If application you are communicating with is not running at the same time as your application
Message is too important If application can not maintain reliable
connection Applications communicating
asynchronously
Middleware Requirements
Scalability Flexibility Interoperability Quality
Middleware elements
Communication Link Middleware Protocol API Common data format Server Process control Naming/Directory Services Security Administration
Alternatives to Middleware
Web Services(?)
Internet
Http – Hyper text transfer protocol
Session Management
Store User log on information Carrying data between the screens Saving data between user sessions
Session Management
Cookies Storing state information in database URL Rewriting Hidden fields
Service Oriented Architecture
A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed.
Service
A service is a function that is well-defined, self-contained, and does not depend on the context or state of other services.
Benefits
Easier to integrate applications Better alignment between IT and
Business
SOAP
Simple object access protocol SOAP provides a way to communicate
between applications running on different operating systems, with different technologies and programming languages.
SOAP (Ref:www.w3c.org) SOAP is a communication protocol SOAP is for communication between applications SOAP is a format for sending messages SOAP is designed to communicate via Internet SOAP is platform independent SOAP is language independent SOAP is based on XML SOAP is simple and extensible SOAP allows you to get around firewalls SOAP will be developed as a W3C standard
Web Services
Web Services provide a robust way for businesses to communicate over the Internet. Expedia.com uses web services to communicate with airlines, rental car companies, and hotels to get the best rates. Some business might use a web service to perform credit card validation.
Web Service Concepts Web Services is a platform and language
neutral architecture that supports B2B commerce. B2B applications are used to allow
businesses to communicate much like EDI. Web Services are applications that are built
upon core web technologies, including: TCP/IP, HTTP, and SMTP.
Technologies used in Web Services
Web Services implement a Service Oriented
Architecture. Web Services can be implemented using
any language or platform, including Java
and .NET. Web Services are implemented using the
following core W3C, XML-based standards:
UDDI, SOAP, and WSDL.
Core Components of Web Services
SOAP WSDL UDDI Web Services Tool Kits are used to
ease the implementation details.
UDDI Registry
Web ServiceProvider
Consumer
Web Services
Use Case Diagrams
Components• Use cases
• Actors
• System being modeled
Purpose of Use cases
Requirements Gathering Describe Functionality of the systems To help in Design and Testing Validating the completed system
Users of Use cases
Stakeholders Developers Project Managers System Integrators
Actor
User External System Represented by “Stickman” figure
Major Steps
Identify use cases System boundary Identify actors Add relationships
Questions???
