Viewing history of changes of subjects

[vestr-at-work]

As a clerk, I need to access the history of subject changes within the system. This feature is crucial because subjects may undergo revisions, and it's important for us to track these changes over time. This will ensure that students are learning the most current curriculum aligned with academic standards.

[danekjiri]

REQUIREMENT DESCRIPTION:

The subject module of the university student information system must allow authorized users to view the history of changes made to subjects, ensuring transparency and accountability in curriculum management.

FUNCTIONAL REQUIREMENTS:

• The system shall provide authorized clerks with the capability to access and review the history of changes made to subjects within the system.
• The history log should include details such as additions, deletions, and modifications to subject information.
• Clerks should be able to search and filter the change history based on specific criteria (e.g., date range, type of change).
• When viewing the subject change history, the system should display comprehensive details about each modification, including the user who made the change, timestamp, and specific elements affected (e.g., subject title, description). Audit Trail and Versioning:
• The system must maintain an audit trail of all subject changes, ensuring data integrity and accountability.
• Previous versions of subject details should be accessible, allowing users to revert to earlier versions if necessary.

NON-FUNCTIONAL REQUIREMENTS:

• The system should handle the retrieval of subject change history efficiently, even as the database grows over time.
• Response times for accessing the change history should remain optimal, even under high concurrent usage.
• Access to the subject change history should be restricted to authorized users (e.g., clerks, administrators) through secure authentication mechanisms.
• Changes to subject information should be logged securely to prevent unauthorized modifications.
• The user interface for viewing subject change history should be intuitive and easy to navigate, supporting clear presentation of change details.
• Search and filtering options should be user-friendly, allowing clerks to quickly locate specific changes within the history log.

[danekjiri]

USE CASE

Starting Situation:

An authorized clerk accesses the subject module of the university's student information system with the intention of reviewing the history of changes made to subjects.

Normal

1. Clerk logs into the system using their authorized credentials.
2. Clerk navigates to the "Subject Change History" section within the system.
3. System retrieves and displays a list of subject modifications chronologically.
4. Clerk utilizes search and filter functionalities to narrow down the displayed history based on specific criteria (e.g., date range, type of change).
5. System presents detailed information for each modification, including:
   • Type of change (addition, deletion, modification)
   • User who made the change
   • Timestamp of the change
   • Specific elements affected (e.g., subject title, description)
6. Clerk can select a specific modification to view further details or retrieve changes.

What Can Go Wrong

• Clerk attempts to access the subject change history without proper authorization. In this case, the system denies access and prompts the clerk to log in with valid credentials.
• The system experiences technical issues retrieving the change history due to database constraints or server downtime. The clerk is informed to try again later.

System State on Completion

• Clerk successfully reviews the subject change history, gaining insights into past modifications made within the system.
• System maintains an audit trail of all subject changes, ensuring data integrity and accountability.
• Previous versions of subject details remain accessible, allowing authorized users to revert to earlier versions if required.