Scribd
Upload
2 views

Functional and Nonfunctional Requirements-Case Studies

The document outlines functional and non-functional requirements for various applications, including an E-Commerce Application, Healthcare Management System, and Online Library Management System. Key functional requirements include product search, order placement, appointment booking, and user registration, while non-functional requirements focus on performance, security, and scalability. Additionally, it describes use cases and interactions for the Online Library Management System, detailing the roles of students and librarians.

Uploaded by

ladybugmatto
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
2 views

Functional and Nonfunctional Requirements-Case Studies

The document outlines functional and non-functional requirements for various applications, including an E-Commerce Application, Healthcare Management System, and Online Library Management System. Key functional requirements include product search, order placement, appointment booking, and user registration, while non-functional requirements focus on performance, security, and scalability. Additionally, it describes use cases and interactions for the Online Library Management System, detailing the roles of students and librarians.

Uploaded by

ladybugmatto
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 22

Functional and

Nonfunctional
Requirements
Functional and Non functional
Requirements
E-Commerce Application
• Functional Requirements:
• Product Search: Users should be able to search for products using filters (e.g.,
price, category).
• Order Placement: The app should allow users to add products to the cart and
complete the checkout process.
• Payment Integration: The app should support multiple payment methods
(credit card, PayPal, etc.).
Functional Requirements

•User Registration and Login:


•Users should be able to create an account, log in, and recover their password if forgotten.
•Product Recommendations:
•The system should suggest products based on users’ browsing history and previous purchases.
•Wishlist Management:
•Users should be able to add products to their wishlist and access it later.
•Product Reviews and Ratings:
•Customers should be able to rate and review purchased products.
•Inventory Management:
•The system should update inventory levels automatically after each purchase.
•Order History:
•Users should be able to view their past orders and their statuses.
•Notifications:
•The system should send notifications for order confirmation, shipping updates, and promotions.
•Support for Multiple Currencies:
•The app should allow users to select their preferred currency for transactions.
•Returns and Refunds:
E-Commerce Application
• Non-Functional Requirements:
• Performance: The system should process orders within 2 seconds after
payment confirmation.
• Reliability: The app should have 99.9% uptime to ensure availability during
peak shopping times.
• Scalability: The system should handle up to 500,000 concurrent users during
sales events.
Non-Functional Requirements of E-
Commerce Application
•Response Time:
•Search results and product pages should load within 2 seconds.
•Data Security:
•All sensitive user information (e.g., passwords, payment details) must be encrypted using
industry-standard protocols.
•High Availability:
•The system should have an uptime of 99.99%, ensuring minimal downtime.
•Scalability:
•The application should be able to handle up to 1 million concurrent users during sales events.
•Cross-Platform Compatibility:
•The application should function seamlessly on web browsers, Android, and iOS platforms.
•Fault Tolerance:
•In case of server failure, the system should automatically redirect traffic to backup servers.
•Localization:
•The app should support multiple languages based on the user’s geographic location.
Healthcare Management System
• Functional Requirements:
• Appointment Booking: Patients should be able to book, reschedule, or cancel
appointments with doctors.
• Prescription Management: Doctors should be able to upload and share prescriptions
with patients.
• Patient Records: The system should allow staff to access and update patient medical
history.
• Non-Functional Requirements:
• Security: All patient data must comply with healthcare privacy regulations (e.g.,
HIPAA).
• Usability: The system should have a user-friendly interface for both patients and
medical staff.
• Availability: The system must be accessible 24/7 for emergency use.
Learning Management System (LMS)
Healthcare Management System
Online Streaming Platform
Food Delivery Application
Case Study: Online Library
Management System
• Case Study Description
• An Online Library Management System is designed to provide
services for students and staff to browse, borrow, and return books
efficiently. The system includes functionalities such as user
registration, book search, borrowing, returning, and fine
management. Both library staff and registered users interact with the
system.
• Student: A user who can search, borrow, and return books.
• Librarian: A staff member responsible for managing inventory, issuing,
and returning books.
• System: The backend that handles data management, book inventory,
and user accounts.
Functionalities (Use Cases)
Use Case Diagram
• The Use Case Diagram depicts the interactions between actors and the system:
• Description of Diagram Elements
• Actors:
• Student
• Librarian
• Use Cases:
• Search Books
• Borrow Books
• Return Books
• Add Books
• Remove Books
• User Registration
• Generate Fine
• System Boundary:
• The Online Library Management System encapsulates all use cases.
Detailed Use Case Example
• Use Case Name: Borrow Books
• Actor: Student
• Preconditions:
• The user must be registered and logged into the system.
• The book must be available in the library inventory.
• Steps:
• The student searches for the desired book.
• The system checks the availability of the book.
• The student requests to borrow the book.
• The system updates the book's status as “Borrowed” and associates it with the student.
• Postconditions:
• The book status is updated, and the borrowing details are stored.

You might also like