2 Using  A Little Architecture
Upcoming SlideShare
Loading in...5
×
 

2 Using A Little Architecture

on

  • 1,230 views

Illustrating how an architecture framework is used to inspire passion through vision & innovation.

Illustrating how an architecture framework is used to inspire passion through vision & innovation.

Statistics

Views

Total Views
1,230
Views on SlideShare
1,221
Embed Views
9

Actions

Likes
0
Downloads
33
Comments
0

2 Embeds 9

http://www.linkedin.com 7
http://www.slideshare.net 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

2 Using  A Little Architecture 2 Using A Little Architecture Presentation Transcript

  •  Using Architecture Developing passion through vision & innovation “One world | one purpose | one team” “Segment by risk, manage by exception” “Unlocking the Value of Content Bound by the Title’s Cover” ®®
  •  Gartner Architecture Framework Technical Standards Technology components Technology lifecycle Infrastructure, security & systems management Systems & software products Data interchange protocols System integration map Physical data stores Detailed Processes L4-6 Guidelines Standards Business rules Physical Technical reference model Infrastructure design rules Technology patterns Technology services Business systems (people, process & data) Functional requirements Business Services Boundaries models Data design rules Logical data model Information flow map Processes L 1-3 Organisation Policy Constraints Logical Technology principlesApplication principlesInformation principles Integration requirements Conceptual data model  Subject areas  Data stewardship (accuracy & ownership) Business strategy Product strategy B. Scorecard  Objectives  Roadblocks  KPIs Business initiatives Conceptual Technology (Infrastructure) Application (Solutions) InformationBusinessPerspective Roadmap Projects = Target Architecture (logical) - Current Architecture (physical)
  •  Enterprise Architecture Models Perspective Business Information Application (Solutions) Technology (Infrastructure) Conceptual L0 Business Model -People perform processes collecting data to fulfil downstream dependencies 1. Information must be consistent, timely and accurate; as such the quality of information should be continuously monitored and improved. 1. Business applications will exist as independent components and communicate via services that are exposed by the middleware. 1. All applications will conform to the technology reference architecture and standards. 2. Middleware technology will be used to define the navigation between system services, so they can be re-used by other applications. Logical L1-3 Business Process Technical Reference Model Physical L4-6 Business Process Roadmap Projects = Target Architecture (logical) - Current Architecture (physical) Manage Corporate Strategy Manage Workplace Safety Administer System Compliance Manage the Programme Support Activities Primary Activities Management & Administration Services Human Resource Management IT Services ValueServices Financial Management Services Provide Compensation Administration Pr od uc t Pe rio d Location Cu sto me r Company KPI Measure Fa mi ly Br an d Mo nth Da y Ye ar Division Department Op Co Ch an ne l Section Se gm en t Cli en t Region Country Postcode Pr od uc t Pe rio d Location Cu sto me r Company KPI Measure Fa mi ly Br an d Mo nth Da y Ye ar Division Department Op Co Ch an ne l Section Se gm en t Cli en t Region Country Postcode Data Customer Product Early Notification (FNOL) Adaptor 3r Evolution (package) Rules Engine I Adaptor Build e-file Adaptor TRIM (package) MQ Integrator Middleware Infrastructure Case Management Adaptor Build Claims Administration Adaptor ACCtion (legacy) Adaptor Build Rules Configurator XML Header Source = Transaction ID = Claim ID Date = Data Medical only = XML Header Source = Transaction ID = Claim ID Date = Data Medical only = HP-UX/NT/Windows Oracle Visual C++ Iona Orbix+ Java MQ Series Entire X OS/390 Adabas Natural MQ Series HP-UX/Window Oracle J2EE MQ Series HP-UX J2EE MQ Series Windows SQL Server MQ Series Lotus Notes DB Lotus Script MQ Series HP-UX .NET Early Notification (FNOL) Adaptor 3r Evolution (package) Rules Engine I Adaptor Build e-file Adaptor TRIM (package) MQ Integrator Middleware Infrastructure Case Management Adaptor Build Claims Administration Adaptor ACCtion (legacy) Adaptor Build Rules Configurator XML Header Source = Transaction ID = Claim ID Date = Data Medical only = XML Header Source = Transaction ID = Claim ID Date = Data Medical only = Early Notification (FNOL) Adaptor 3r Evolution (package) Early Notification (FNOL) Adaptor 3r Evolution (package) Rules Engine I Adaptor Build Rules Engine I Adaptor Build e-file Adaptor TRIM (package) e-file Adaptor TRIM (package) MQ Integrator Middleware Infrastructure Case Management Adaptor Build Claims Administration Adaptor ACCtion (legacy) Adaptor Build Rules Configurator XML Header Source = Transaction ID = Claim ID Date = Data Medical only = XML Header Source = Transaction ID = Claim ID Date = Data Medical only = MQ Integrator Middleware Infrastructure Case Management Adaptor Build Case Management Adaptor Build Claims Administration Adaptor ACCtion (legacy) Claims Administration Adaptor ACCtion (legacy) Adaptor Build Rules Configurator XML Header Source = Transaction ID = Claim ID Date = Data Medical only = XML Header Source = Transaction ID = Claim ID Date = Data Medical only = HP-UX/NT/Windows Oracle Visual C++ Iona Orbix+ Java MQ Series Entire X OS/390 Adabas Natural MQ Series HP-UX/Window Oracle J2EE MQ Series HP-UX J2EE MQ Series Windows SQL Server MQ Series Lotus Notes DB Lotus Script MQ Series HP-UX .NET Middleware Broker Middleware Infrastructure Early Notification (FNOL) Adaptor CRM Rules Engine I Adaptor CASE Claims Administration Adaptor CMS Rules Dbase Adaptor Rules Configurator Local Rules Engine Rules Configurator Case Management Adaptor Rules Engine XML Header Source = Transaction ID = Claim ID Date = Data Medical only = XML Header Source = Transaction ID = Claim ID Date = Data Medical only = e-file Adaptor ERDMS Middleware Broker Middleware Infrastructure Early Notification (FNOL) Adaptor CRM Early Notification (FNOL) Adaptor CRM Rules Engine I Adaptor CASE Rules Engine I Adaptor CASE Claims Administration Adaptor CMS Claims Administration Adaptor CMS Rules Dbase Adaptor Rules Configurator Local Rules Engine Rules Configurator Case Management Adaptor Rules Engine Case Management Adaptor Rules Engine XML Header Source = Transaction ID = Claim ID Date = Data Medical only = XML Header Source = Transaction ID = Claim ID Date = Data Medical only = e-file Adaptor ERDMS e-file Adaptor ERDMS Data Warehouse Claims Management Directory Segment & Profiling Workflow Data Warehouse MS Office Case Management MS Office Case Management Risk Management Rules Administrator Rules Configurator Message Services Claims Analyst Identify fraud profile Define fraud segmentation rules Conduct rule impact analysis Establish case management plan Prepare rule test cases Maintain standard rule parameters Define risk assessment message flow Test risk assessment message Deploy fraud rule sets (test) Test new fraud segment rule set Deploy production rule set & parameters pass test [pass test] [pass test] [fail test] newattributes [fail test] Accident Finance Activity Communication Hazard Claim Policy CaseRegulation registers granted performed by manages covers compensates earns pays generates causes earns Party & Location Permission specifies fined
  •  Enterprise Process Architecture Risk Management Rules Administrator Rules Configurator Message Services Claims Analyst Identify fraud profile Define fraud segmentation rules Conduct rule impact analysis Establish case management plan Prepare rule test cases Maintain standard rule parameters Define risk assessment message flow Test risk assessment message Deploy fraud rule sets (test) Test new fraud segment rule set Deploy production rule set & parameters pass test [pass test] [pass test] [fail test] newattributes [fail test] TechnologyApplication (Solutions) InformationBusinessPerspective TechnologyApplication (Solutions) InformationBusinessPerspective Roadmap Projects = Target Architecture (logical)- Current Architecture (physical)
  •  Enterprise Data Architecture Accident Finance Activity Communication Hazard Claim Policy CaseRegulation registers granted performed by manages covers compensates earns pays generates causes earns Party & Location Licence specifies fined
  •  Enterprise Business Systems TechnologyApplication (Solutions) InformationBusinessPerspective TechnologyApplication (Solutions) InformationBusinessPerspective Roadmap Projects = Target Architecture (logical)- Current Architecture (physical)
  •  Claims Business Systems letters confirmation & incomplete notification Real time interface Batch - near real time interface Key: M DM CASE manager query recommended CASE manager M DM risk assessed notification data notification data risk assessment risk assessment claim data claim forms notification data (all claims) register claimant enquiry (employer, workplace, claimant) early time loss injury notification Batch - overnight interface tasks outcomesM DM claim LR claim status change Notification Risk Assessment CASE Management Data Warehouse Claims Administration System Accounts Payable/ Recievable System TechnologyApplication (Solutions) InformationBusinessPerspective TechnologyApplication (Solutions) InformationBusinessPerspective Roadmap Projects = Target Architecture (logical)- Current Architecture (physical)
  •  What is a Business System?  A business system is a logical grouping of people, process & data, i.e. as represented by the intersection of the Gartner business, information and technology view points  The logical level is used to illustrate ideas, methods and techniques to accomplish conceptual goals  Defined in terms of subsystems that describe course grained functions and data  Used to define, negotiate and agree scope of architecture components  Basis for recommending candidate enhance, build, buy software solutions  aka business area or TOGAF architecture building blocks … Telephone Group and identify IT initiatives
  •  Structured Approach Establish Process Vision Design Business Process approval ? [approved] Business Analysis Workshops cancel 1. Verify business objectives (BA & BP) 2. Determine measures & information needs (BA & BP) 3. Identify current process issues (BA & BP) 4. Verify project scope (BA & BP) 1. Prepare data model (BA & BP) 2. Determine data attributes (BA & BP) 3. Specify interface data (BA & BP) 4. Estimate data volumes (BA & BP) Describe Data Requirements 1. Measure cost of process issues (BA & BP) 2. Evaluate process improvements (BA & BP) 3. Determine changes to current business practice (BA & BP) 4. Establish future business changes (BA & BP) 5. Assess model flexibility (BA & BP) 1. Prepare system use case specifications (BA, & BP) 2. Draft screen prototype (BA & BP) 3. Design report layout (BA, & BP) 4. Map system interfaces (BA & IT) 5. Review specifications (BA, BM & IT) Establish Solution Options Key BM- Business Manager BA - Business Analyst BP - Business Participants (operational staff & specialists) IT - Information Technology Evaluate Process Health 1. Design process workflow (BA & BP) 2. Specify activity requirements (BA & BP) 3. Estimate activity frequencies (BA & BP) 4. Determine activity data usage (BA & BP) 5. Define non-functional requirements (BA & BP) Prepare Functional Specification Solution Design Workshops 1. Design solution proposal options (BA & IT) 2. Conduct impact analysis (BA & IT) 3. Establish design principles (BA & IT) 4. Determine technology architecture (IT) 5. Identify system functions or use cases (BA, BP & IT) 6. Determine priorities & delivery iterations (BA, BP & IT) 7. Estimate use case development effort (BA & IT) 8. Obtain business approval (BM or SC) Screen Prototyping Workshops acceptance? [cancelled] [no] [yes] Business & Technology Managers Design Handover Detailed design process... Product: Requirement Specification 40 - 300 pages Product: Solution Proposal Report 10 - 50 pages Product: Functional Specification 30-500 pages [not approved] Business Manager or Steering Committee  Business Strategy  Business Cases  Cost Model  Benefits analysis  Project initiation  Business requirements  Architecture design  Software evaluation  Functional specification  Workshop facilitation  Management presentation
  •  Contact Technology architecture & solutions are justified at a strategic and financial level by preparing a business case.