List of Functional Requirements for UFIMS Platform:

• 1. Design and implementation of the 3-tier system architecture:
  • a. Data Layer (data access layer, object-relational mapping)
  • b. Business Layer (business objects domain, business transactions)
  • c. Asp.Net Web Application – GUI Front End
• 2. Single integrated database
• 3. The framework of the application accommodates the needs of the gradually growing in size business functionality. New dynamic libraries are fairly easily added or removed from the application through the declarative XML configuration files.
• 4. The layout of the GUI, to some extent, is also configurable via XML configuration files.
• 5. The framework of the application groups related business functionality by the business module libraries.
• 6. All operation names and system messages are configurable via XML configuration files.
• 7. Background processing sub-system
• 8. Security sub-system
• 9. Scanning sub-system
• 10. Printing sub-system
• 11. Sending e-Mails
• 12. Transaction history keeps track of almost all changes to the primary UFIMS data objects (e.g., employer, member, local, etc)
• 13. Alerts generation and management
• 14. User comments component
• 15. Dashboard object counters (sometimes referred to as “dashboard alerts”)
• 16. Integration with the 3d party USPS sub-system
• 17. Cross-browser GUI appearance
• 18. Wide usage of the server and client side user input validation
• 19. Electronic documents archive
• 20. Ad-Hoc Letters
• 21. Document generation based on configurable document templates
• 22. Embedded in HTML Word processor, which allows editing documents before printing/e-mailing and also allows editing document templates.
• 23. Advanced DHTML GUI
• 24. System logging component
• 25. Data caching
• 26. Navigation history, which allows user going back to the previous operation