Use case document

I need you to have detailed use case document for the following Dear, We are a company working in selling aftermarket spare parts and services for Heavy equipment. We have 14 branches all over Saudi Arabia. This is our website for more information about the company [login to view URL] We would like to make a B2B E-commerce portal with the following functions and features: · The SPC E-Commerce portal would have similar features and look and feel of Autodoc E-commerce website [login to view URL] with additional features: o Warranty Claim Submittal and Workflow (Adding Pictures) o Special Order Submittal and workflow with discount or prices approval workflow o Return invoices and Warranty Claims should have a workflow that integrates Finance department with money transfer to customer or credited to customer account in the portal. o Customer notifications- Email and SMS (on new invoice, Returned invoice, warranty stages, shipping, payment, Credit limit, overdue invoices…) § The customer should have admin page where he can input people who can get notification for each notification item: · General Manager (Email,SMS) · Finance Manager (Email, SMS) · Purchasing Manager (Email, SMS) · Purchaser (Email, SMS) · Maintenance manager (Email, SMS) o Customer can choose receiving items by: § Select preferred location in a Map § Select preferred time slots § Select to collect from certain SPC branch o A system tool should make optimization solution of where is the best places to ship items from and in how many shipments based on (Lead time, Cost, Branches inventory Min/Max “Safety Stock”) o Customer can choose between partial shipment and full shipment with lead time clear for customer for both. o Submit a credit account request and workflow (with notifications) o Customers reports like § Customer payments in certain period § Overdue invoices (Days, and Amount) § Unpaid invoices § Customer Returns in certain period § Invoices in certain period with payment status (Paid/Unpaid) § Items purchased in certain period (Item #, Description, Cost, Date, Invoice #, Branch, type (Cash/Credit), is any warranty request on the item? Yes/No, …) § Warranty Claim follow up § Order information (Received, not received, Air Way Bill #, location, Closed,…) o Setting prices/price list by customer based on one of the following options (customer pricelist has to go through approval workflow) : · Certain discount percentage on Item/Category/Subcategory · Certain GP% on Item/Category/Subcategory · Setting prices per Item or list of items o Payment options are as follow: § Credit and Debit Cards (Mada,Visa, MasterCard) § STC pay and Apple Pay § Brank Transfer (Workflow to prove transfer and release order) (notification to customer on payment status) § Payment through one of our branches (Using Mada machines or cash (workflow and notification should be implemented) § Payment through customer credit account with the company § Customer should be able to choose to pay through two payment options o Customers should be able to search for items by pasting a list of item numbers in a certain place of the portal and the portal should check on the items and cross reference database and suggest the matching available numbers. o The E-commerce website should show all Active items that SPC carries (approx.. 19000) and identify available items with Green for example and not available with yellow with a tick button on the not available on hand to Add to special Order Request/Cart o The portal should link with Oracle ERP/Microsoft Dynamics CRM in order to get data and conditions like Credit limits, Customers payments, items, invoices (online/offline), parts list, on hand …) Use Case Document Just about every project manager has the need to develop a Use Case Document, this template is provided as a starting point from which to develop your project specific Use Case Document. The Use Case Document ties the business needs of a system to the design and implementation of the system. It is an effective tool to help ensure that the system being developed meets the business requirements for the system. Since each system is unique, the Use Case Document can be either high level or very complex and detailed – depending on the system being developed and the organization within which it’s being developed. Read more: [login to view URL]