ITElectv4 Midterm Reviewer

• is the process of joining software and hardware modules into one

  cohesive infrastructure, enabling all pieces to work as a whole.

  System Integration
• Most Common Types of System Integration

  • Legacy System Integration
  • Enterprise Application Integration
  • Third-Party System Integration
  • Business-to-business Integration
• integration of modern applications into existing outdated systems

  Legacy System Inegration
• unification of different subsystems inside one business environment

  Enterprise Application Integration
• expanding functionality of the existing system

  Third-Party System Integration
• connecting systems of two or more organizations

  Business-to-business Integration
• 4 Ways to Connect Systems

  • API
  • Middleware
  • Webhooks
  • EDI
• It provide the most common and straightforward way to connect two systems. Sitting between applications and web services, they enable the transmission of data and functionality in a standardized format.

  API
• It is the hidden software layer that glues together distributed systems,

  applications, services, and devices.

  Middleware
• also known as "HTTP callbacks" are real-time messages, sent by one

  system to another when a certain event happens.

  Webhooks
• is the exchange of business information in a standard electronic format, that replaces paper documents.

  EDI
• 3 Approaches to System Integration

  • Point-to-point Model
  • Hub-and-Spoke Model
  • ESB (Enterprise Service Bus) Model
• is the architectural pattern in which every system is directly connected to all other systems and apps it needs to work in tandem and share information with.

  Point-to-point model
• is a more advanced type of integration architecture tha addresses the issues of point-to-point and helps to avoid the star/spaghetti mess. The connections between all subsystems are handled by a central hub, so they don’t communicate with each other directly.

  Hub-and-spoke model
• involves the creation of a separate specialized subsystem — an enterprise service bus — that serves as a common user interface layer connecting other subsystems.

  ESB
• Key Steps to System Integration

  1. Planning and feasibility analysis
  2. Architecture modeling
  3. Implementation
  4. Maintenance
• the assessment of systems to be integrated and mapping out a realistic strategy.

  Planning and feasibility analysis
• detailed blueprints of how systems will communicate with other comprehensive systems.

  Architecture Modeling
• The new integrated system is thoroughly tested to make sure that all modules seamlessly interact with one another without losing any data during transmission.

  Implementation
• Scheduling performance diagnostics to make sure that all modules function flawlessly and no errors occur is advised.

  Maintenance
• Its purpose is to define a comprehensive solution based on principles, concepts, and properties that are logically related to and consistent with each other.

  System Architecture
• is a major part of every company's IT landscape, that simplifies the integration of numerous IT components and enables to trace and process data flow objects between applications within IT architecture while providing and using interfaces.

  Information Architecture
• is a science of organizing and structuring content of the websites, web and mobile applications, and social media software.

  Information Architecture
• He is considered to be a founder of the IA field.

  Richard Saul Waurman
• 8 Principles of Information Architecture

  • Object
  • Choices
  • Disclosure
  • Exemplary
  • Front Doors
  • Multiple Classifications
  • Focused Navigation
  • Growth
• Content should be treated as a living, breathing thing. It has lifecycles, behaviors, and attributes.

  Principle of Objects
• Less is more. Keep the number of choices to a minimum.

  Principle of Choices
• Show a preview of information that will help users understand what kind of information is hidden if they dig deeper.

  Principle of Disclosure
• Show examples of content when describing the content of the categories.

  Principle of Exemplars
• Assume that at least 50% of users will use a different entry point than the home page.

  Principle of Exemplars
• Offer users several different classification schemes to browse the site’s content.

  Principle of Multiple Classifications
• Keep navigation simple andnever mix different things.

  Principle of Focused Navigation
• Assume that the content on the website will grow. Make sure the website is scalable.

  Principle of Growth
• Best Practices for Information Architecture

  • Don’t Design Based on Your Own Preferences
  • Research User Needs
  • Have a Clear Purpose
  • Use Personas
  • Keep Site Goals in Mind
  • Be Consistent
• takes into account the “style” andapproach of the solution.

  Application Architecture
• deals with what operating systems,hardware, platform, and network facilities will be used.

  Technical Architecture
• addresses issues of which data structures will be used, which access methods will be employed, and how data is coordinated throughout the system.

  Data Architecture
• is a discipline that applies architecture principles that defines the structure and operation of organizations which standardize and organize IT infrastructure and manages conflicting approaches to align with business goals and success.

  Enterprise Architecture
• Benefits of Enterprise Architecture

  • Improved decision-making
  • Minimization of employee turnover
  • Elimination of inefficient and redundant processes
  • Can help simplify finance teams
  • Optimization of the use of organizational assets
• It is defined as the processes, procedures, decisions, and activities to ensure that an organization can continue to function through an

  operational interruption.

  Business Continuity