PII Production

Appearance

​Quality Requirements ​

​To ensure that the PII App meets high standards of performance, functionality, and user satisfaction, the following quality requirements are established:

​Security ​

  • ​Data Protection: The application must implement robust encryption methods for data at rest and in transit to protect sensitive information.
  • ​Authentication and Authorisation: User authentication should be managed using secure methods such as JWT tokens. Role-based access control (RBAC) should be used to ensure that only authorized users can access specific functionalities and data.
  • ​Audit Logging: The application must maintain detailed audit logs of all actions performed, especially those related to PII access and recognition, to ensure traceability and accountability.

​Performance ​

  • ​Response Time: The application should have a reasonable response time for most user interactions, with document PII recognition processes completed within a reasonable timeframe, depending on document size, complexity and Relativity One API response.
  • ​Throughput: The system should be able to handle multiple document processing tasks simultaneously without significant performance degradation.

​Reliability ​

  • ​Availability: The application should have an uptime of 99.9% in production environments.
  • ​Error Handling: The system should gracefully handle errors without crashing and provide meaningful error messages to users.

​Usability ​

  • ​User Interface: The application has an intuitive and user-friendly interface that allows users to easily upload documents, view and select PII entities, and manage documents that contain PII.
  • ​User Guidance: Clear instructions and help documentation should be provided to assist users in understanding and using the application effectively.

​Maintainability ​

  • Modular Design: The application should be designed in a modular way to allow for easy updates and improvements.
  • ​Code Quality: The codebase should follow best practices and coding standards to ensure high quality and maintainability.
  • ​Documentation: Comprehensive documentation for developers should be provided, including API documentation, architectural diagrams, and coding standards.

​Accuracy ​

  • ​PII Detection: The machine learning models used for PII detection should have a reasonable accuracy rate, minimising false positives and false negatives.
  • ​Continuous Improvement: The system should incorporate mechanisms for continuous model improvement through human-in-the-loop processes and user feedback.

​Interoperability ​

  • ​Integration: The application should seamlessly integrate with external document management systems like iManage and potentially other systems in the future.
  • ​Standard Protocols: The system should use standard protocols (e.g., RESTful APIs) to facilitate integration with other systems and services.

​Extensibility ​

  • ​Future Enhancements: The application should be designed to allow for easy addition of new features and functionalities.
  • ​Customisability: The system should provide options for customisation to meet specific user requirements and preferences.