• Like
  • Save
Proposed Architecture Framework
Upcoming SlideShare
Loading in...5
×
 

Proposed Architecture Framework

on

  • 761 views

 

Statistics

Views

Total Views
761
Views on SlideShare
761
Embed Views
0

Actions

Likes
1
Downloads
25
Comments
0

0 Embeds 0

No embeds

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

    Proposed Architecture Framework Proposed Architecture Framework Presentation Transcript

    • Advanced Planning Briefing Proposed Architecture Framework Office of Enterprise Development Joaquin J. Martinez de Pinillos Director Software Engineering November 17, 2009
    • Advanced Planning Briefing overview Office of Enterprise Development (OED) Software Engineering (SE) The SE team strives to apply a systematic, reliable and disciplined approach to plan, architect, design, test, and release software for VA business operations. SE follows the OI&T policy for IT strategy and enterprise architecture guidelines. SE interacts with business customers, Enterprise Infrastructure Engineering (EIE), and Operations and Maintenance Teams to meet business needs and to make the software development life cycle (SDLC) seamless. SE is comprised of three services: Application & Data Architecture Service, Standards & Compliance Service, and Testing Service.
    • Advanced Planning Briefing Line of Sight in Action Line of Business (LOB) or Business Process Modeling Center of Excellence (PMCE) Performance Reference Model (PRM)/Strategy Documents Strategy PRM Business Process Models Business BRM Information & Data Data SE Systems Engineering (SE)/Architecture and DRM Engineering Processes Applications & Services SRM SE Artifacts Technology Infrastructure TRM System Development Life Cycle (SDLC) Process IT Products IT Products IT Products IT Products
    • Advanced Planning Briefing Interface between Software Engineering (SE) & Line of Business (LOB) Challenge •Some LOB do not have business architecture capability Strategy • SE interface will help close that gap PRM LOB Business BRM Information Information & Data Data DRM Applications & Services SE SRM Technology Infrastructure TRM
    • Advanced Planning Briefing Business Architecture Artifacts System of Systems (SoS) Systems Engineering/Architecture Software and Engineering Processes module or •Provide boundary conditions and definition of black Software Service i.e. boxes module or Service i.e. lab, Software •Software Engineering Management Plan (SEMP) lab, scheduling, module or identity, etc •Heavy focus on SoS Architectures/Designs scheduling, Service i.e. identity, etc lab, • 508 Requirements/Design scheduling, • Disaster Relief (DR) Software Software identity, etc module or module or • Service Oriented Architecture (SOA) Service i.e. Service i.e. Software •Etc. lab, lab, module or scheduling, scheduling, Service i.e. identity, etc identity, etc SDLC Process lab, scheduling, •Provide processes in the development of individual identity, etc modules SOA Stack Common Services •Heavy use of Rational/Jazz Tool Suite although has some need for software engineering tool suites -Heavy use of Rational Tool Suite (with Jazz •Agile Development Methodology enhancement). Some Systems Engineering Tools •Project/Service focused requirements •Lab -Heavy use of a modeled based Systems Engineering Tools Suite and some Rational (with •Payment of benefits Jazz enhancement) Products •Etc
    • Advanced Planning Briefing Business Architecture Artifacts System of Systems Systems Engineering/Architecture and Engineering Processes Software Software module or •Artifacts of SE Process feed into module or Service i.e. various spots in SDLC Service i.e. lab, Software lab, scheduling, module or •Artifacts need be focused on SoS scheduling, identity, etc Service i.e. identity, etc lab, •Artifacts need to tie into business scheduling, architecture Software Software identity, etc module or module or Service i.e. Service i.e. Software lab, lab, module or SDLC Process scheduling, scheduling, Service i.e. Challenge identity, etc identity, etc lab, scheduling, •How do artifacts which are updated on a periodic identity, etc basis fit into a time based (project based) project SOA Stack Common Services •Sequencing artifact updates to all project schedules not possible •SE artifacts must take into account projects at different states in SDLC and be able to account for different life cycle states
    • Advanced Planning Briefing Federal Enterprise Architecture Architecture Artifacts (FEA) HeV Project Scope PRM Project Scope COOP DR Architecture Strategy BRM Business Models SOS Business Data Standards & • SOA Linkage DRM Practices • Coding Architecture • Interface Standards (SOA Shop) • Data Standards Information & Data • • Design Standards (SOA) Programming Standards SRM Services (What are they going to be) Applications & Services SW-TRM Enterprise Requirements Network Architecture TRM Technology & Infrastructure HW Standards & Architecture COOP DR Architecture
    • Advanced Planning Briefing FEA Reference Models Performance Reference Model PRM Business Reference Model BRM Data Reference Model DRM Service Component Reference Model SRM Technical Reference Model TRM (from FEA Overview Presentation by FEA PMO, February 2004)
    • Advanced Planning Briefing FEA Reference Models Cont’d PRM Standardized framework to measure the performance of major IT investments and their contribution to program performance BRM Function-driven framework for describing business operations of the Federal Government independent of the agencies that perform them DRM Model describing, at an aggregate level, the data and Information that support program and business line operations
    • Advanced Planning Briefing FEA Reference Models Cont’d SRM Business and performance-driven functional framework that classifies service components with respect to how they support business and/or performance objectives TRM Component-driven, technical framework used to identify the standards, specifications, and technologies that support and enable the delivery of service components and capabilities
    • Advanced Planning Briefing Federal Enterprise Architecture (FEA) Performance Reference Model (PRM) Strategic (Metrics) Outcomes Project Scope Measure Delivery of Business Services Business COOP DR Architecture ie, Reliability Services and Availability Business Models Business Reference Model (BRM) SOS (Business Processes) Services Service Component Reference Model (SRM) (What are they going to be) (Service Model, Application Architecture) Govern Data Reference Model (DRM) Data Architecture (Data Architecture) Enterprise Requirements HW Architecture & Technical Reference Model (TRM) HW Standards (Standards, Specifications, Technologies) SW-TRM Network Architecture
    • Advanced Planning Briefing Architecture & Artifacts FEA REFERENCE MODEL ARTIFACTS Performance Reference Project Goals and Objectives (Scope) Model Technical Sequence Plan Integrated Master Schedule PRM Reliability and Availability Requirements Reliability and Availability Implementation Plan Metrics Measurement Plans and Procedures Metrics Measurement Tools Metrics Database, Analysis Tools, and Reports Business Reference Model Business Processes Definition Document BRM (Business use cases) Business Requirements Management Process Business Requirements Business Rules Business Rules Management Plan
    • Advanced Planning Briefing Architecture & Artifacts Cont’d FEA REFERENCE MODEL ARTIFACTS Data Reference Model Data Architecture Model DRM Data Standards - Data Descriptions (Data Dictionary) - Data Context (Taxonomies) - Data Sharing (Query Points and Exchange) DRM Abstraction Model Service Component Current Architecture Diagram (As Is) Reference Model Future Architecture Diagram (To Be Model) SRM Service Model Services Definition Artifacts (see Services – Slides 9-12) Services Usage Artifacts Services Management Processes and Tools
    • Advanced Planning Briefing Architecture & Artifacts Cont’d FEA REFERENCE MODEL ARTIFACTS Technical Reference Model IT-Technical Reference Model Enterprise Requirements Repository TRM Enterprise Requirements Compliance Criteria and Review Processes Legislative Compliance Evaluation Database Security Plan Software Development Standards Software Development Environment Software Management Processes - Requirements Management and Traceability - Change Management - Deployment Management - Version Management - Defect Tracking - Issue Management - Task Management
    • Advanced Planning Briefing Architecture & Artifacts Cont’d FEA REFERENCE MODEL ARTIFACTS Technical Reference Model Test Management Process Cont’d Test Environment Hardware Architecture Model TRM Hardware Standards Network Architecture Model Network Standards Operations and Troubleshooting Procedures Inventory Management Plans and Tools (FEA puts this in SRM but seems to make more sense here)
    • Advanced Planning Briefing FEA: Strategy Federal Enterprise Architecture (FEA) Strategy Business Strategy Information & Data Applications & Services Technology & Infrastructure
    • Advanced Planning Briefing Strategy SE Strategic Plan •Work within VA strategic plan •Modernize technology based on T-21 •Meet program goals & objectives
    • Advanced Planning Briefing FEA: Business Federal Enterprise Architecture (FEA) Strategy Business Business Information & Data Applications & Services Technology & Infrastructure
    • Advanced Planning Briefing Business Models Business-Based Lexicon Document • Describes business capability • Provides framework for discussion • Illustrates lexicon in no more than 20 pages • Ties into VA strategic plan
    • Advanced Planning Briefing Business Products Business Products: Capabilities that provide business unique services • Project goals & objectives • Modeling & monitoring tool plan • Workshop definition documentation • Process models with business requirements • Process metrics & KPIs • Gap analysis • Re-use plans • Business service models • Conceptual model • Business use case narratives & diagrams • Functional flow diagrams
    • Advanced Planning Briefing FEA: Information & Data Federal Enterprise Architecture (FEA) Strategy Business Information & Data Information & Data Applications & Services Technology & Infrastructure
    • Advanced Planning Briefing Standards & Practices Standards • SOA design pattern • Coding & programming standards – The initial standards profile, addressing Java coding standards, will be published as an entry in the IT-TRM by 12/1/2009. – Additional profiles, to include all major identified technologies in use for VA development, will be published throughout 2010, – The first generation of profiles will be complete by 12/1/2010 • Interface Standards • Data Standards • Design Standards
    • Advanced Planning Briefing Standards, Specifications, Patterns • Data Strategy, Interface Design and Architecture Governance with associated Coding standards are synergistically evolved through BRM/BPM analysis Fed by co- • Service-Orientation is evolution of appropriate embedded in technology and each of these based on a business case evaluation BRM/BPM of the capabilities being analysis augmented or transformed.
    • Advanced Planning Briefing FEA: Applications & Services Federal Enterprise Architecture (FEA) Strategy Business Information & Data Applications & Applications & Services Services Technology & Infrastructure
    • Advanced Planning Briefing Service Definition Methodology Service Definition Methodology will: • Define all VistA-HealtheVet products • Categorize infrastructure products
    • Advanced Planning Briefing Infrastructure Products Infrastructure Products •Provide key features/functions required by HeV (aka “Common Services”) •Align with enterprise VA Standards, specifications, patterns, and practices wherever possible -OED SE Enterprise Architecture Review Governance will manage/oversee “gap” •Initial Web service-based core infrastructure services reference implementation built as part of VBA Ch 33 -Not every capability or “service” in HeV is/will be web-services based
    • Advanced Planning Briefing Infrastructure Products Cont’d Infrastructure Products Initial Service Reference Implementation Offerings: •Discovery •Messaging •Security •Identity Inclusive of physical implementation as well as SSPP, developer, [FEA] architecture documentation and OED SE governance process to manage evolution and extension of capabilities (initial release: 6/10)
    • Advanced Planning Briefing Service Artifacts Service Artifacts Two Categories of Service Artifacts: • Service Definition Artifacts -Used by SE to identify and categorize products • Service Usage Artifacts -Provided to projects to inform projects of services provided by products and to provide instructions for use of services
    • Advanced Planning Briefing Service Artifacts Cont’d •Additionally, documentation to support product development -List of documentation/templates required for Infrastructure products -List of documentation/templates required for business products •Documentation requirements on a project identified via project-to-product map -Documentation will be structured along product (not project) lines -A project will create/update documents for products that the project affects •Additionally, Service Definition Methodology will support development of HealtheVet to-be architecture evolution and transition products -Sequence Plan (PRM Artifact) -Master Schedule (PRM Artifact)
    • Service Definition Methodology VistA VistA-HeV Products Products V1 V1 . . . . . . Infrastructure Business Vn Vn P1 P1 HeV1 . . . . . . . .  VistA . . HeVn Pn Pn Product List  VistA-HeV Product List  Product List HeVn … HeV1  Product Categorization - Infrastructure HeV Products - Business Infrastructure ICD List (Unilateral VistA-HeV As-Is Arch Model ) Business Uni ICD List (Bi/Multi- VistA VLink KAAJEE FatKAAT P1 P2 ... PN VHeV1 ... VHeVN P1 x x lateral) Bi/ Bi/ HWSC U/I U/I Bi/ Bi/ Multi HeV1 x x Bi/ Multi Multi HeV C A HeV C A . . P2 . x Multi Multi I P I P . . . DS HeVn x x VIE VIE DS PN x HeV to VistA-HeV Product Adapt Mapping N2 Chart MPI Corp CorpCorp DB DoD CorpCorp ADR DB DB Corp DB DB Adapt Info Corp DB HeV To-Be Arch Model HDR DB Ext Infrastructure Business I/F HEC VistA User I/F . . OBS CS CS HeV HeV Portfolio1 Proj1.1 Proj1.2 Portfolio2 ... . .. .. Adapt Enterprise Proj1 Proj2 ... ProjN PortfolioN Infrastructure Services P1 x x ... HeV .. . . P2 x x x x ProjExt ProjN.n “Egg Chart” . Doc I/F Ext Ext I/F . .. Adapt Adapt Corp . I/F .. Ext Corp DB I/F Ext ADR Corp DB DoD I/F Ext FEA Corp DB I/F Info Pn x x HDR DB Model P[n+1] x x . . . Seq PN x Plan Master  Product-to-Project Mapping Schedule
    • Advanced Planning Briefing Service Definition Methodology and Supporting Artifacts ACTIVITY ARTIFACTS 1 Register HealtheVet Products VistA-HealtheVet Products List 2 Update VistA As-Is Architecture Model VistA-HealtheVet As-Is Architecture Model 3 Categorize HealtheVet Products Categorized VistA-HealtheVet Products List - Infrastructure Products Infrastructure Products - Business Products Business Products 4 Develop HealtheVet To-Be Architecture Model HealtheVet To-Be Architecture Model Service Model 5 Map HealtheVet (To-Be Architecture) Products to HealtheVet (To-Be Architecture) Products to VistA-HealtheVet (As-Is Architecture) Products VistA-HealtheVet (As-Is Architecture) Products Map 6 Identify HealtheVet Product-to-Product N-squared Chart Dependencies (Interfaces) (HealtheVet Product – to – HealtheVet Product) 7 Identify Product Usage (Interface) Documentation List of Uni-Lateral ICDs - Infrastructure Products: Uni-Lateral ICDs Uni-Lateral ICDs = Common Service Standards - Business Products: Bi-/Multi-Lateral ICDs Docs List of Bi-/Multi-Lateral ICDs 8 Develop Project-to-Product Mapping Project-to-Product Map 9 Structure Project Documentation in accordance Product Documentation List with Products Product Documentation Templates 10 Develop “HealtheVet Evolution” Artifacts Sequence Plan (PRM Artifact) - Sequence Plan Master Schedule (PRM Artifact) - Master Schedule
    • Advanced Planning Briefing Artifacts Cont’d SERVICE DEFINITION ARTIFACTS ARTIFACT STATUS VistA-HealtheVet Products List - VistA Products are already registered - VistA-HealtheVet Products List will be available when HealtheVet Products register (requires management direction to HealtheVet Projects) VistA-HealtheVet As-Is Architecture Model - Strawman exists - Can be updated when VistA-HealtheVet Products List is available Categorized VistA-HealtheVet Products List - Several Analysis Products to support categorization exist - To complete requires VistA-HealtheVet Products List and some additional analysis HealtheVet To-Be Architecture Model - Strawman exists Service Model - To complete requires VistA-HealtheVet Products List and support of project teams responsible for Infrastructure Products HealtheVet (To-Be Architecture) Products to VistA-HealtheVet - Has been started for Messaging Products (As-Is Architecture) Products Map - Will be developed in conjunction with HealtheVet To-Be Architecture Model N-squared Chart - Cannot be started until VistA-HealtheVet Products List is available - Will require analytical support from Project Teams List of Uni-Lateral ICDs - Will be identified as a consequence of development of List of Bi-/Multi-Lateral ICDs - Categorized VistA-HealtheVet Products List - N-squared Chart Project-to-Product Map - Requires VistA-HealtheVet Products List - PMO-owned Artifact
    • Advanced Planning Briefing Artifacts Cont’d SERVICE USAGE & PRODUCT DEVELOPMENT ARTIFACT STATUS ARTIFACTS Product Documentation List - Already exists for VistA Products Product Documentation Templates - May require some updating to completely support HealtheVet Products; determination will be made when HealtheVet Products comply with VistA Product Registration and Management Process Uni-Lateral ICDs - Required Uni-Lateral ICDs will be identified as a consequence of development of Categorized VistA- HealtheVet Products List - Identified Uni-Lateral ICDs will be assigned to Project Team for the Infrastructure Product for development (Messaging Team has already begun development of Messaging Uni-Lateral ICD) EVOLUTION AND TRANSITION ARTIFACTS ARTIFACT STATUS Sequence Plan (PRM Artifact) - Strawman of these Artifacts requires analysis of the Master Schedule (PRM Artifact) following Service Definition Artifacts: - Categorized VistA-HealtheVet Products List - VistA-HealtheVet As-Is Architecture Model - HealtheVet To-Be Architecture Model - Project-to-Product Map
    • Advanced Planning Briefing FEA: Technology & Infrastructure Federal Enterprise Architecture (FEA) Strategy Business Information & Data Applications & Services Technology & Technology & Infrastructure Infrastructure
    • Advanced Planning Briefing Enterprise Requirements Management Program Objectives • Central compilation and tracking of cross- cutting enterprise-level requirements • Assure allocation of enterprise-level requirements to projects • Enhance traceability from and to project-level requirements • Foster requirements engineering best practices • Align requirements management with system development methodology and processes 35
    • Advanced Planning Briefing Enterprise Requirements Management Enhancement & Maintenance • Performed on an annual cycle - completed by 9/30/09 – Centrally gather and elicit enterprise-level requirements – Conduct and participate in peer reviews and validate enterprise- level requirement submissions – Establish and maintain an enterprise-wide requirements repository – Perform change and configuration management of enterprise requirements repository contents 36
    • Advanced Planning Briefing Enterprise Requirements Management Functions and Services • Project-level services provided upon request (est. 90 day cycle assuming full commitment of ERM, SE, SME & Project resources) – Allocate enterprise-level requirements to projects – Trace enterprise-level requirements to project-level requirements – project system requirements review • Program system requirements reviews – semi-annual in October & April 37
    • Advanced Planning Briefing Technology & Infrastructure Roadmap Technology Roadmap
    • Advanced Planning Briefing Technology Roadmap
    • Advanced Planning Briefing IT-Technical Reference Model • IT-TRM identifies technologies approved or prohibited for VA system development • Forecasts technology evolution to assist project planning • Provides a technical framework to categorize standards and technologies • Uses common, standardized vocabulary, enabling inter/intra-agency collaboration and interoperability • Fosters reuse of solutions and technologies • Supports e-Gov initiative; aligns with FEA 40
    • Advanced Planning Briefing IT-Technical Reference Model (Software) Deliverable Timelines • HSD&D Extended Tool List (ETL) – Predecessor to TRM; approved and prohibited tools • TRM v1 approved by the ARB on 4/25/2007 – Populated with 25 basic technology entries • TRM v2 approved by the ARB on 9/17/2008 – Refreshed TRM v1.0 entries, added 26 new tools – Merged verbose listing of ETL entries into the TRM • TRM v3.0 approved by the ARB on 1/7/2009 – Re-Assessed/Refreshed 51 entries • TRM v3.1 completes the v3 update cycle on 5/13/2009 – v3 noted intent to refresh 15 entries in 2009 • TRM v3.2 added 14 approved, 3 prohibited tools on 8/4/2009 • TRM v4.0 will add 13 assessments; approval expected 9/16/2009 41
    • Advanced Planning Briefing Network Architecture • Strategy to Implement Fault Tolerant Delivery Solution – Redundant Paths to Highly Available Systems – Addressing the Last Mile • Flexible Construct to Respond to Business Drivers – Dynamic Quality Of Service – Scale to Meet Changing Requirements • Migration Away From De-Centralized Architecture – Regional Data Processing Centers (RDPC) High Availability Solution – Network topology from the RDPC’s all the way down to the hardware.
    • Network Architecture: RDPC—High Availability Solutions
    • Advanced Planning Briefing RDPC - High Availability Solution
    • Advanced Planning Briefing Continuity of Operations Planning (COOP) Disaster Relief (DR) Architecture Artifacts of Form, Function and Program • Artifacts of Form: – Blueprint for hardware deploy at AITC and HITC (Owner CDCO: TBD) Need resource(s) allocated to work on this – Software Data Flow Diagram – showing the software of each system, any data stores they may use, and the dataflow between them (Owner: SE First Draft Completed) – Software Deployment Diagram – showing the deployment of software to processors but ignoring the detail of how applications use the network for data communications (Owner: SE, December, 2009)
    • Advanced Planning Briefing COOP DR Architecture Cont’d Artifacts of Function: -System-specific DR plans (Owner: HeV Project Teams, Mostly Completed) -HeV overarching DR Plan - to facilitate system recovery order at HITC (Owner: SE First Draft Completed) -Database synchronization plan after recovery at HITC (Owner: MPI, PSIM, ADR, TBD) May become part of some system -specific DR Plans -Plan for recovery of messages at HITC (Owner: SE and HeV Project teams, TBD)
    • Advanced Planning Briefing COOP DR Architecture Cont’d Artifacts of Program: -Implementation Plan for Scalent and VMware software upgrades. ( Owner: EIE , TBD) -Migration Plan for applications (CDCO: TBD) -Design of the new hardware upgrades (Owner EIE, Completed) -Project Schedule ( Owner , SE/EIE/CDCO First draft Complete)
    • Advanced Planning Briefing Data Architecture Reference Model Enterprise Information Architecture – A planned approach to building an organization that encompasses business needs and IT – Allow integration and coordination across the enterprise – Requires a shift away from vertical or proprietary to horizontal approaches that cut across the organization
    • Advanced Planning Briefing Data Architecture Reference Model Cont’d Data Architecture Components •Provide a standardized approach to data and database access thru the use of: -Uniform data modeling techniques -Naming conventions -Data dictionary with fully realized metadata -Data Access - Instituting defined technology architecture -Security & auditing services that are uniform across the enterprise
    • Advanced Planning Briefing HealtheVet (HeV) Data Architecture - Definition • Repositories will be used to house re-engineered HeV data • Repositories will be stood-up on an as needed basis, following the HeV sequence plan • Analysis will need to be performed on the methodology employed for data migration • Current CDS will need to be expanded as the enterprise requirements are identified • VHIM domains will need to be translated. Translation should follow the sequence plan of HeV applications
    • Advanced Planning Briefing Data Architecture Artifacts • Implement Enterprise Data Dictionary – Re-evaluating enterprise elements tool that is currently used for the Data Architecture Repository (DAR) – complete – Performing evaluation of other tools available for DAR – 12/01/09 – Fully implement the agreed upon solution – Q1 2010
    • Advanced Planning Briefing Data Architecture Artifacts Cont’d • Establish VA Data Model – Review existing VistA model – ongoing – Review & Translate the VHIM UML domains o each domain will take approximately 4 – 8 weeks depending on the size and complexity of the domains. There are 20+ domains remaining and new domains will be discovered as the HeV sequence plan is initiated – Create a conceptual & logical data model of the HeV applications; must follow the sequence plan established for HeV.
    • HeV to-be Data Architecture Repositories Roadmap
    • Advanced Planning Briefing Hardware Architecture & Standards • HW architecture and standards from EIE • Needs to include HW architecture and standards for all programs • Needs to include deployment models for existing programs and projects • Needs to include how programs and projects design or engage EIE to design HW • The starting point for HW architecture and standards is the RDC artifacts
    • Advanced Planning Briefing Standards Storage Servers Data Center LAN WAN
    • Advanced Planning Briefing Standards VistA Imaging Storage WAN Acceleration Servers Data Center LAN Virtualization WAN Legacy VistA 56
    • Advanced Planning Briefing One on Ones
    • Advanced Planning Briefing One on Ones - Purpose • VA will be hosting 30 minute one on one sessions with industry on the VA Architecture • These sessions will be for industry to provide feedback on this presentation • Other documentation on the system architecture can be found at: http://www1.va.gov/oamm/oa/tac/
    • Advanced Planning Briefing One on Ones - Registration • Registration for one on ones will be announced on FedBizOpps • Registration for the one on ones will be handled similar to the Registration for the APBI • Time slots will be allocated on a first come first serve basis • Not a marketing opportunity • Limited to 6 attendees
    • Advanced Planning Briefing Feedback/Input for One on Ones • VA is looking for feedback/input in the following areas: – The Architecture and Architecture Framework presented