Skip to main content

IT-Checklists.com - The eBook-Shop with Checklists and Templates for Professionals
logo
Skip main navigation
Template Operations ManualData Migration ChecklistNonfunctional RequirementsApplication Interface ChecklistRelease ChecklistApplication Health checkArchiving RequirementsDatabase OLA / SLADBA Job DescriptionDatabase Health Check

Application SupportData MigrationSystem DokumentationProject ManagementQuality AssuranceCompliance and StandardsDatabase AdministrationStartup PhaseAchieving Operational ReadinessStabilized Operations

Interface-Checklist for Application Integration

Table of Contents


About this Template 5
Preface 6
Ooops, did'nt think about that .... 6
Scope 6
Purpose 7
Audience 8
Introduction 9
Part 1: Introduction 10
Overview 10
General Information 10
   Organizational 10
   Constraints 11
Constraints due to the source- and destination application 11
   (No) Time Synchronization 12
   Legal Constraints 12
   Other Constraints 13
General Analysis / Impact Analysis 14
   Impact of the Interface on the Interfacing Applications 14
   Impact Analysis of Interface related Operational Problems 15
Part 2 - List of Requirements 16
Requirement 1: Dependency / Availability 16
Requirement 2: Intervall Type , Transaction Control 18
Requirement 3: Physical location of the interfacing systems 19
Interface Architecture 20
   Requirement 4: Interface Architecture (I) - 1:1, 1:n, n:m, direct / hub-spoke based 20
   Requirement 5: Interface Architecture (II) 20
   Requirement 6: Interface Features (I) - Content Based Routing 20
   Requirement 7: Interface Features (II) Data Transformation 20
Issue 8: Reliability and Integrity, Recoverability 21
   Requirements 21
   Specifications 21
Requirement 9: Performance and Scalability 22
Security 23
   Requirement 10: Authentication, Authorization, Confidentiality, Integrity,
       Auditing and Nonrepudiation 23
   Requirement 11: The interface must be able to work a firewalls with following settings: 23
   Requirement 12-1: The interface must work across a VPN 24
   Requirement 12-2: MLS (Multi Level Security) operating systems. 24
Requirement 13: Software - Dependencies 24
Globalization 25
   Requirement 14: international Character Sets 25
   Requirement 15-1: Working Days / Holidays (functional) 25
   Requirement 15-2: Working Days / Holidays (functional) 25
   Requirement 15-3: Time Zones 26
Requirement 16: Archiving (functional requirement) 27
   16-1) Archiving of stored data 27
   16-2) Archiving has impact on destination system 27
   16-3) Archiving of all information sent across the interface .....(audit trail) 28
Configuration 29
   Requirement 17: Configuration (functional) 29
   Requirement 18-1: Configuration (technical) 29
   Requirement 18-2: Configuration (technical) 29
   Requirement 18-3: Configuration (technical) 29
Requirement 19: Reconciliation (functional / operational) 30
Requirement 20: Password change (operational) 31
Specification 21: Responsibility / Handover Point 31
Specification 22: Interface Monitoring 31
Other..... 31
   The usage of Hardware-addresses (e.g. MAC-Address, UNIX-HostID) 31
Testing of Interfaces 32
   Design Review 32
   Test environments 32
      Cloning related requirements (3 requirements) 33
   Hands-On Testing 35
   Documentation Review 36
Production Release 36
   Initial Data Transfer 36