Electronic archive management system for student works.
1.2 Programming language:
Python (version 3.x).
1.3 System type:
Client-server system for working with electronic archives of student works.
1.4 Main goals and objectives:
The main goal of the development is to create software for storing, organizing, searching, editing, and analyzing student works in the form of an electronic archive.
2. Functionality description
2.1 User registration and authorization:
Users: administrative (administrator), teachers, students.
User registration through a form with login, password, and role input.
User authorization by entering login and password.
Authorization based on user role (administrator, teacher, student).
2.2 Management of student works:
Uploading works:
Students can upload their works in formats (docx, pdf, txt).
After uploading, the system automatically determines the metadata (for example, upload date, author).
Viewing works:
Teachers and administration can view works.
Students can only view their own works.
2.3 Searching and filtering works:
Search by metadata: author, work title, upload date.
Filtering by work status (processed, unprocessed).
2.4 Editing works:
Teachers can edit the status of works (for example, assign grades, comments).
The ability to provide grades and comments for student works.
2.5 Change history:
Automatic recording of changes in works (edit history), saving changes in the database.
User action logging (who uploaded the work, who edited the status).
2.6 Storage and archiving:
Works are stored in electronic form (in specified formats).
The software allows archiving works (for example, storing works of senior courses in separate archives).
3. System architecture and components
3.1 Main components:
User interface (UI):
Web interface or console interface for users (depending on requirements).
The web interface is implemented using a framework (for example, Flask or Django).
Server side (logic):
Logic for processing user requests, working with the database.
Database:
The system uses a relational database (for example, SQLite, MySQL, PostgreSQL) to store data about students, works, and their metadata.
3.2 Database components:
Users (User table): Login, password (encrypted), role (student, teacher, administrator).
Student works (Work table): Work title, author, upload date, file format, work status.
Comments and grades (Comments table): Grade, teacher's comment, link to the work.
Change history (History table): Records of status, grades, and comments changes.
4. Technical requirements
4.1 Programming languages and tools:
Python 3.x.
Flask or Django (for web development).
SQLite, MySQL or PostgreSQL (for working with databases).
HTML, CSS, JavaScript (for web interface).
4.2 Technologies:
Web framework (Flask or Django).
Database (SQLite, MySQL or PostgreSQL).
Libraries for working with files (PyPDF2, python-docx).
4.3 Security:
Use of HTTPS protocol for secure connection.
Encryption of user passwords.
Authorization and authentication using tokens or sessions.
5. User interface
5.1 Interface for students:
Registration and authorization form.
Page for uploading works.
Viewing and editing own works (if necessary).
Notification system for changes in work status.
5.2 Interface for teachers:
Viewing all student works.
The ability to add grades and comments to works.
Filtering and searching by various criteria (date, author, work status).
5.3 Interface for administrators:
User management (registration, deletion of users).
Full access to all works and the ability to change statuses.
Logging of all user actions.
