Update Requirements authored by mdmuradalahi's avatar mdmuradalahi
......@@ -63,12 +63,12 @@ FUNCTIONAL REQUIREMENTS:
Non-Functional Requirements
NF1: The system should display confirmation messages for successful actions (e.g., registration, login, ad creation) .
NF2: The system should include basic error handling, showing clear messages like “Invalid login details” etc.
NF3: Passwords should be hashed before storage to ensure basic security.
NF4: The user interface should have a consistent layout and color scheme across all pages
NF5: Form fields should have labels or placeholder text that disappears when typing, making forms user-friendly and easy to fill out.
NF6: All main buttons (e.g., "Submit," "Save") should be prominently colored to stand out and be easily identifiable.
•NF1: The system should display confirmation messages for successful actions (e.g., registration, login, ad creation) .
•NF2: The system should include basic error handling, showing clear messages like “Invalid login details” etc.
•NF3: Passwords should be hashed before storage to ensure basic security.
•NF4: The user interface should have a consistent layout and color scheme across all pages
•NF5: Form fields should have labels or placeholder text that disappears when typing, making forms user-friendly and easy to fill out.
•NF6: All main buttons (e.g., "Submit," "Save") should be prominently colored to stand out and be easily identifiable.
......@@ -105,12 +105,12 @@ Don’t follow these practices:
EPICS:
User Authentication and Profile Management
User Authentication and Profile Management.
Requirement Numbers: FR 1.1, FR 1.2, FR 1.3, FR 1.4, FR 1.5, FR 1.6, FR 1.7, FR 1.8, FR5.7, NF6
Advertisement Management
Advertisement Management.
Requirement Numbers: FR 1.10, FR 1.11, FR 1.12, FR 1.13, FR 1.14, FR 1.15, FR 2.1, FR 2.2, FR 2.3, FR 2.4, FR 2.5
Search and Filter Functionality
Search and Filter Functionality.
Requirement Numbers: F3.1, F3.2, F3.3, F3.4, F3.5, F3.6