Professional Documents
Culture Documents
Practical 3
Practical 3
Practical 3
AIM: To classify the requirements into functional and non-functional requirements. Write at
least four functional and non-functional requirements, for any two scenarios.
c. Order Processing: - Users must be able to place orders securely. - The system should
generate order confirmations with detailed information. - Administrators should have access
to order history and processing tools.
d. Payment Integration: - The system must support secure online payments. - Users should be
able to choose from various payment methods (credit card, PayPal, etc.).
2. Non-functional Requirements:
a. Performance: - The system should load product pages within 3 seconds. - Concurrent user
support: The website must handle at least 1000 simultaneous users.
b. Security: - User data must be encrypted during transmission. - The system should implement
secure coding practices to prevent common vulnerabilities.
c. Scalability: - The system should scale to accommodate a 20% increase in users over the next
year. - Database scalability: The database should handle a 30% increase in product entries.
d. Usability: - The website should be accessible and usable on major web browsers. - Mobile
responsiveness: The interface must adapt to various screen sizes.
b. Member Management: - Librarians should be able to register new members and update
member information. - Users should have the ability to view their borrowing history. - The
system must send overdue notifications to members.
c. Checkout and Return: - Users must be able to check out books, and the system should
update availability. - The system must track and manage return dates for borrowed items.
d. Reporting: - Librarians should have access to reports on popular books, overdue books, and
member statistics.
2. Non-functional Requirements:
a. Reliability: - The system should be available 99.9% of the time. - Backup and recovery:
Regular backups must be performed, and data recovery should be possible within 24 hours.
b. Data Integrity: - The system must ensure the integrity of the book and member data. -
Transactions and updates should be atomic to prevent data corruption.
c. Response Time: - The system should respond to book search queries within 2 seconds. -
Check-out and return processes should be completed in less than 5 seconds.
d. Compliance: - The system should adhere to privacy regulations regarding user data. - The
interface should comply with accessibility standards.