The Role of a Systems Architect
Paul Booth, Senior ConsultantIT Architecture & [email protected] 344774
What is a Systems Architect?
The holistic approach
Structured MethodGlobal Services MethodEnterprise Architecture MethodEnd-to-End Design MethodSMFD (Systems Management)Availability MethodPerformance Engineering method
End-to-end (holistic)Requirements-driven
Viability - Non-functional RequirementsPerformance (response times, etc.)Availability (# breaks per year, etc.)Operability / Systems ManagementSecurityEtc.
Requirements Analysis
End-to-End Systems Architecture
Breadth of understanding & skill across IT
Depth of technical expertise
The T-shaped skills profile
Enterprise Architecture (EA) relative toEnd-to-End Systems Architecture (E2E)
Enterprise Architecture
Data Architecture
Process ArchitectureIT Strategy
Enterprise Strategy
ABCsystem
Current Systems
DEFsystem
GHIsystem etc..
EA
E2EE2E
E2EE2E
An Enterprise Architecture (EA) is much like a city plan in that it defines an infrastructure that will meet the current and future needs of a diverse user population and will adapt to changing business requirements and technology.
Strategy for I/T use across the enterprise
Guidance for investment and design decisionsOverall context and views for systems and usersStandard Components for high level design
Considerations for standards and product selectionGuidelines to which systems must conform
Process to allow additions & variances to ArchitecturePrioritized infrastructure projects & costs
City vision based on anticipated needs of residents
Zoning and building codes to ensure quality & consistency in constructionMaps and diagrams for infrastructure systems like water, sewer & electricPrefabricated building component specifications for off-site constructionConsiderations for component selection such as durability, cost, etc.Electrical wiring and plumbing standards
Process to change the city plan and allow for variances
City improvement plan
Architecture Components Usage City Planning Analogy
Vision
Principles
Models
Arch. Building Blocks
Criteria
Standards
Arch. Mgmt. Process
Transition Initiatives & Plan
Management:"I know I have a problem - it's impacting my business. But technically I don't really know where to begin."
Qualify the situationAnalyse background & context
Define problem
The Systems Architect
Problem Statement or
Analysis
Recommend and plan project to handle problemResource team with appropriate skills
Carry out researchMake recommendations
Solution Recommendations
Dealing with Fuzzy problems
The client has.. The client needs.. System Architect.. System Architect produces..
IT-related problem A solution Defines problemRecommends actions
Problem Analysis ReportProblem Recommendations
Business requirements
(possibly incomplete)
Outline of system solution & its
feasibility
Analyses & completes requirements
Creates first-cut IT solution
Reviews technical feasibility
Requirements AnalysisSystem Feasibility ReportSystem Proposal
Existing infrastructure
needs evolutionTechnical direction
Establishes business & technical context
Creates a recommended strategy
Technical Strategy Report
Systems Architecture situations (1)
The client has.. The client needs.. System Architect.. System Architect produces..
Fundamental change or increase in scale
to existing infrastructure
coming up
New technical architecture or system
model
Uses structured approach to create an architecture or
design
Enterprise Technical Architecture Report,Technical Infrastructure Design
Project with many disparate elements, or application but not
technical infrastructure
Overall system designUses structured method to review design elements and
create cohesive design
Technical Audit Report,System Architecture Report,Technical Infrastructure Design
Project under way or in plan
Assurance of technical viability
Reviews technical design in structured way.
Creates systems architecture if necessary.
Technical Audit / Assurance Report,System or Technical Architecture
Systems Architecture situations (2)
The client has.. The client needs.. System Architect.. System Architect produces..
Under-performing system (availability
or response)
Recommended way forward
Establishes where in end-to-end system the problem
lies.Recommends actions.
Performance Analysis,Availability Analysis,Scalability Analysis
Project starting To know what tasks required, in what order
Works with PM to create work breakdown structure
Work Breakdown Structure,Plan
Systems Architecture situations (3)
Benefits to the client
BusinessSpur to creativity, innovation
Reduces & manages riskLowers cost and raises quality overall
Ties IT actions more closely to business
ITRaises technical integrity of solution (i.e. it works better & offers better service to business)
Increases flexibility, scalability, adaptability (etc., etc.) of system
Positions IT better for business change
What skills do you need to do this?
Understand the business requirements
What does the business need? What business processes will be
supported? What system components are needed to
do this? Where are the business rules? Who are the key users? Who is really behind this?
Understand the technology
Disk (local, shared, NAS, SAN...) Windows, Unix, Linux, Solaris, z/OS,
OS/400, ... DB2, Oracle, SQL Server... Java, ActiveX LANs, WANs, Routers, Firewalls RSA, SSL, Intrusion Detection
-business
The data
Underlying data structures Tailored data groups Business Manager Tables Referential Integrity Interfacing requirements MIS requirements Imaging
CLIENT
COMPANY
CLIENTAS
CLTROLE
NAME
ADDRREF
FONREF
CLAIM
POLICY
CLTREF
CLTDET
PAYMNT
CLTLOG
CLTACT
CLTTH
ADDRESSBILACT
Architectural Alternatives
Client/Server or Web-model
Operational or Informational
Flexibility vs. Performance
Performance
MVS tuning CICS tuning DB2 tuning Efficient SQL Diagnostic tools:
STROBEDB2PMEPDMOMEGAMON
The operational environment
The overnight schedule The data centre view of life Interfacing requirements Disaster recovery
Human factors
Business scripts Dialog structure Number of screens Layout of screens Drag and Drop CUA look and feel Sequence of fields Use of help Menemonics
The development process
Overall Development approach
ToolsLibrary managementDebuggers
Table data vs. code Standards and Guidelines Work activities
Management systems
Risk management Project deliverables Escalation procedures Roles and Responsibilities Right of Veto Sign-off criteria
Testing
DEVELOPMENT UNIT TEST
INTEGRATION TEST
SYSTEM TESTSINGLE THREAD VOLUME
STRESSACCEPTANCE
What to test Types of test Entry criteria Exit criteria When to stop testing
The Compleat architect
A brain the size of a planet Eyes in the back of the head The memory of an elephant The armament of a tank The creativity of Salvador Dali An understanding spouse
Questions ?
Top Related