1 INTRODUCTIONAptify conducted requirements confirmation meetings with ISFL to validate information exchanged during the sales process, discuss previously unknown requirements, uncover gaps, and clarify questions or open problems. This document identifies gaps between the out-of-the-box Aptify functionality and the validated requirements for the ISFL Aptify implementation. This document also contains all the requirements identified for this implementation in section 8.1.1 Assumptions and ConstraintsThe following were identified as assumptions during the confirmation meetings:• ISFL has purchased Aptify 5.0 which comes bundled with eBusiness and includes the following applications: o Campaign Managemento Case Managemento Committee Managemento Clientio Expo Managemento Inventory Managemento Meeting Managemento Subscription Management Subscription Management• The value system for subscription activity is currently suspended.• LMS integration is not covered in scope at this time and its integration is addressed in a change order submitted on January 19, 2010.2 Membership Management ISFL continues its aggressive goal of rapidly increasing its membership from the current 700 to approximately 50,000 members over the next 5 – 7 years. To ensure fast membership processing, ISFL requires a process flow to streamline the membership application process, as illustrated in Figure 6: Membership Application Process. The membership application process also generates artifacts as identified in Figure 7: Membership Request Data Flow.2.1 Membership Application ProcessAll individuals or companies acquire their ISFL membership by following the membership application process. The four different types of membership of...... half of the card ......or participate. Stock Aptify functionality meets the following ISFL requirements for event management: • Ability to create and track aspects of events/meetings, including speakers, room setup, A/V requirements, food and beverage, locations, attendees, and times • Ability to track meeting attendance • Ability to create multiple meeting sessions for an event • Ability to invoke waitlist functionality whenever meetings are full • Ability to invoke registration-based pricing for attendance to the event • Ability to track current event registration counts • Ability to recognize revenue for the event at that time the event occurs 8.1 Event Confirmation A configuration must be set up to allow notifications to be sent via email or printed to event registrants. The notification must list the event, the price paid and other relevant registration details.