ISO25010

Sub-characteristic

Metrics

Functionality

· Functional completeness: Coverage of user management functions compared to requirements (e.g., CRUD operations, password reset).

· Functional correctness: Percentage of test cases passed related to user management functions.

· Feature coverage: Percentage of user management features implemented compared to total requirements.

Role granularity: Number of distinct user roles or profiles supported.

Reliability

· Error rate: Number of failed user operations (like login failures) over a specific period.

· Availability: System uptime and availability for user management tasks.

· Session reliability: Percentage of user sessions without interruptions or unexpected logouts.

· Password reset success rate: Percentage of successful password resets compared to total reset requests.

Usability

· User onboarding time: Time taken for a new user to set up and understand the system.

· -Intuitiveness: Survey-based metric on how easy users find the system to manage their profile and settings.

· Dashboard clarity: User feedback or rating on the clarity and usefulness of user management dashboards.

· Navigation efficiency: Average number of clicks or actions to perform common user management tasks.

Efficiency

· Response time: Time taken to process user management tasks like user creation or role assignment.

· System resource utilization: Resources (like CPU, memory) used during intensive user operations.

· Batch processing time: Time taken to process batch user operations (e.g., bulk user creation or deletion).

· Session initialization time: Average time taken to initialize a user session upon login.

Security

· Authentication security: Strength and type of encryption and hashing used.

· Role misassignment rate: Incidents where users receive incorrect roles or permissions.

· Multi-factor authentication (MFA) usage: Percentage of users enrolled in MFA.

· Password policy strength: An index or score based on the rigour of the password policy (e.g., length, complexity requirements).

Maintainability

· Code modularity: Ease of isolating and modifying parts of the user management component.

· Code complexity: Metrics such as cyclomatic complexity or lines of code for the user management module.

· API versioning frequency: How often user management-related APIs undergo version changes.

· Database schema stability: Frequency of changes to the user-related database schema.

Portability

· Integration ease: How straightforward it is to integrate the user management module with other systems.

· Database independence: The ability of the user management system to operate across different database platforms.

· Cross-platform support: Number of platforms (e.g., mobile, web, desktop) supported by user management functions.

· Integration flexibility: Ease and number of integrations with third-party systems (like SSO providers).

Interoperability

· SSO (Single Sign-On) support: Number of SSO protocols supported (e.g., SAML, OIDC).

· Directory services integration: Ability to integrate with directory services like LDAP or Active Directory.

Auditability

· Change logs availability: Presence and completeness of logs capturing user profile changes.

· Access logs retention: Duration for which user access logs are retained and easily retrievable.