Requirements Database Management System

Requirements Database Management System
- General
1. Describe how your solution provides the benefits of a database system for requirements management while preserving the look and feel of traditional Word/PDF documents.
2. Describe your approach to supporting an organization with 500+ existing published documents while continuing to deliver Word, Excel, and PDF outputs to clients who prefer current delivery methods.
- User Interface for Target Users
3. Describe the end-user interface and how it supports non-technical users (e.g., SME Teams, Active Members, PIP Staff) without requiring database programming knowledge.
4. Describe your system's search capabilities for locating applicable standards.
5. Describe document-linking functionality for navigating between related content.
6. Describe your platform's current accessibility compliance posture, including support for ADA, Section 508, WCAG standards, and availability of a current VPAT.
- Content Types
7. Describe how your system handles text, tables, and figures within structured content.
8. Describe your system's blob storage capability for document types not converted to database format (e.g., PDF, Excel, drawing, and other CAD files).
- Advanced Content Optimization
9. Describe how your system supports content optimization/filtering based on Location/Region and Industry as tagged variables.
10. Describe the user interface for managing metadata associated with requirements, including making requirement justification easily accessible to users.
11. Describe your system's ability to display the history of how a given requirement has changed over time.
- Derivative Work Self-Publishing/Printing
12. Describe how optimized content published or printed from your system retains PIP branding and legal notices.
13. Describe how your system communicates, in the printed/exported document, any regional or industry filtering that was applied prior to publishing.
14. Describe support for revision number (major/minor) and revision date tracking in published content.
15. Describe support for configurable watermarks in published content.
16. Describe your system's ability to publish content with or without applicable metadata.
17. Describe your system's ability to publish content in Word/PDF format consistent with an organization's style and branding guidelines.
18. Describe your system's ability to export content in alternative formats (e.g., ReqIF) to facilitate migration to other requirements management systems.
19. Describe your system's ability to automatically add an attribution statement (e.g., a footer clarifying ownership/ use) to derivative works during self-publishing/printing.
- Content Management
20. Describe your system's configurable workflow for approval of technical content during draft development, prior to formal release to the wider userbase.
21. Describe your system's ability to support comments during draft development.
22. Describe how your system tracks reaffirmation dates to indicate when reaffirmation of a requirement is due.