Bookstore App Summary (Unified Process Perspective)

Unified Process Artifacts Overview

1. Use Case Model

The Bookstore App use case model identifies primary interactions, capturing the functional requirements of the system:

• Actors:

  • Customer: End-user purchasing books.
  • Admin: Responsible for managing inventory and system data.
  • Payment Gateway: Third-party service for processing payments.

• Primary Use Cases:

  • Browse Books: Customers browse available books by categories, search criteria, or recommendations.
  • View Book Details: Displays detailed information for a selected book.
  • Add to Cart: Customers can add books to their virtual shopping cart.
  • Checkout: Customers finalize their purchases and proceed with payment.
  • Manage Inventory (Admin): Admins add, update, or remove books from the inventory.
  • Process Payments: Interacts with a payment gateway to complete transactions.

2. Design Model

The design model includes architectural decisions:

• Backend: RESTful APIs or GraphQL for communication.
• Database: SQL or NoSQL for inventory and transaction data.
• Frontend: Responsive UI for diverse devices.

3. Implementation Artifacts

• Code Modules: Divided into user-facing components, service APIs, and utility functions.
• Test Scripts: Ensure use case functionalities are robust and bug-free.

4. Deployment Model

• Hosted on a cloud-based infrastructure like AWS or Azure.
• Integrated with a CI/CD pipeline for regular updates.

Use Cases in Detail

| Use Case | Actor(s) | Description | |---------------------------|--------------------|-----------------------------------------------------------------------------------------------------| | Browse Books | Customer | Enables users to explore the catalog by category or search for specific titles. | | View Book Details | Customer | Shows book-specific information, including description, reviews, and price. | | Add to Cart | Customer | Adds selected books to the user’s cart for checkout. | | Checkout | Customer, Payment Gateway | Completes purchase by interacting with a payment processor. | | Manage Inventory | Admin | Allows admin users to update or modify available book data. | | Process Payments | Payment Gateway | Verifies payment details and processes transactions securely. |

Traceability Matrix

| Requirement ID | Use Case | Design Component | Test Case(s) | |---------------------|----------------------|-----------------------------|------------------------------------------------| | FR-001 | Browse Books | BookService, BookController| Test_BrowseBooks(), Test_SearchBooks() | | FR-002 | View Book Details | BookDetailComponent | Test_ViewBookDetails() | | FR-003 | Add to Cart | CartService, CartController| Test_AddToCart(), Test_ViewCart() | | FR-004 | Checkout | PaymentService | Test_CheckoutFlow(), Test_PaymentProcessing() | | FR-005 | Manage Inventory | AdminPanel, InventoryService| Test_InventoryCRUD(), Test_AuthPermissions() | | FR-006 | Process Payments | PaymentGatewayAPI | Test_PaymentGatewayIntegration() |

Conclusion

The Bookstore App, designed using Unified Process assets, provides a robust foundation for efficient bookstore management. Its clear traceability from requirements to testing ensures that all functional aspects are covered and verifiable, facilitating smooth development and maintenance cycles.