Custom Data Extraction 8 AppServices Requirements 8 Organizational Structure 8 Data Import Requirements 8 Data Export Requirements 8 Security 8 Collections 8 Entities 9 Developer Portal Requirements 9 Branding 9 Security 9 API Console 9 API Documentation 9 Developer and Application Statistics 9 Browser Support 9 Onboarding 9 Application Onboarding 9 Developer Onboarding 9 Support 10 Operational Monitoring Requirements 10 Apigee Only Health check 10 Target Only Health check 10 Complete API Health check 10 Maintenance Expectations 10 Testing Considerations 11 Functional Testing 11 Testing Approach 11 Test Cases 11 Performance Testing 11 Testing Approach 11 Test Cases 11 Software Maintenance Considerations 12 System Maintenance 12 Training 13 Purpose This document is to capture the comprehensive set of functional and non-functional requirements. The requirements are specific to the Apigee implementation and all aspects: design, architecture, infrastructure (on-prem), and interactions of Apigee with other components. The details captured will be further refined into user stories and this document will be archived as the team executes to the prioritized user stories. Functional requirements should detail specific behaviors or functions for the solution (e.g. REST to SOAP mediation, business rules, Oauth 2.0 Authorization). Non-functional requirements specify the criteria that can be used to measure the operation of the system (e.g PCI Compliant, Supports Failover, Disaster Recovery, Performance).
Custom Data Extraction 8 AppServices Requirements 8 Organizational Structure 8 Data Import Requirements 8 Data Export Requirements 8 Security 8 Collections 8 Entities 9 Developer Portal Requirements 9 Branding 9 Security 9 API Console 9 API Documentation 9 Developer and Application Statistics 9 Browser Support 9 Onboarding 9 Application Onboarding 9 Developer Onboarding 9 Support 10 Operational Monitoring Requirements 10 Apigee Only Health check 10 Target Only Health check 10 Complete API Health check 10 Maintenance Expectations 10 Testing Considerations 11 Functional Testing 11 Testing Approach 11 Test Cases 11 Performance Testing 11 Testing Approach 11 Test Cases 11 Software Maintenance Considerations 12 System Maintenance 12 Training 13 Purpose This document is to capture the comprehensive set of functional and non-functional requirements. The requirements are specific to the Apigee implementation and all aspects: design, architecture, infrastructure (on-prem), and interactions of Apigee with other components. The details captured will be further refined into user stories and this document will be archived as the team executes to the prioritized user stories. Functional requirements should detail specific behaviors or functions for the solution (e.g. REST to SOAP mediation, business rules, Oauth 2.0 Authorization). Non-functional requirements specify the criteria that can be used to measure the operation of the system (e.g PCI Compliant, Supports Failover, Disaster Recovery, Performance).
Blueprint_Template_FuncNonFuncRequirements.docx