According to:

Solve the following:

Introduction [Write one or two paragraph/s describing the business for which your teams is developing an information system) Creating a fashion and clothing design system where it has the ability to accept orders from the buyers, buyers having access to multiple collections of clothes and accessories to choose from and being able to process online payments directly and contact the system management team via live chat. Problem (Describe the business problem that requires an information system] Trying to find a wide a variety of clothing collections with the ease of access for the end user where they can browse products with filtering of prices from highest to lowest and vice versa, pay directly to the vendor through the system itself (Fashion Management System) by having an integrated payment processor and being able to contact the system's team instantly. Stakeholders Categorizing Stakeholders [Who are the stakeholders of the system? Categorize them within the following 4 categories] Operational Executive Internal Staff(IT & Accounting) Fashion System manager End user(Buyer) Investor External Stakeholders Functions of interest [For each stakeholder, explain what aspect of the system are of particular interest] -IT Staff: Maintaining the system from lagging and bugs, handling the traffic that occurs from the users, programming the back end of the system and designing the front end of the system. -Accounting Staff: Handling the revenue and profit margins, performing a cost/benefit analysis to estimate the strengths and weaknesses of the system from a financial standpoint. -Fashion system manager: Managing the full system from hiring the staff, assigning them to their respective duties with a fixed schedule and budget, creating the policies and guidelines, assessing and evaluating the performance of the team and monitoring the project. -Buyer: Searching and browsing for clothes and accessories within different categories, pay for products, provide feedback and reviews and chat with customer support if any issues occur. -Investor: Funding the system to stay operational and sustainable, provide expertise and advice, and provide connections that can help accelerate the business. System Capabilities [Identify the major subsystems of the proposed information system, and for each subsystem list the main capabilities] Dashboard: ability to see an overview of the system from sales, reviews and orders.(System management side) Products: ability to upload products to the system with price, status (in or out of stock), SKU (Stock keeping unit). (System management side) Orders: ability to handle orders from completed to failed. (System management side) Reports & Analytics: ability to check the sales from top selling to least selling and analyzing the sales day by day.(System management side) Return or Refund request: ability to handle refunds or return request from clients.(System management side) Purchasing: ability to buy products with one click or adding to cart.(End User side) Payment gateway: ability to pay directly within the system.(End User side) Review: ability to give feedback for each product.(End User side) Live chat: ability to communicate instantly with customer support.(End User side) . Identifying Use Cases with User-Goal Technique [For each subsystem, list all potential users and identify the different use cases for each) Subsystem 1: .... User Use Case (add/remove rows as needed) Subsystem 2: User Use Case (add/remove rows as needed) Subsystem 3: User Use Case (add/remove rows as needed) Identifying Additional Uses Cases with Event-Decomposition [Apply the event-decomposition technique to identify additional use cases that you may have missed using the user-goal technique. Focus on temporal and state events.] Event Actor/s Use Case Event type (External/ Temporal/State) (add/remove rows as needed) Use-Case Diagrams per Subsystem (Draw a use case diagram showing all use cases of each subsystem) Use-Case Brief Description [For each use case provide a brief description] Use-Case Actor/s Brief Description a Introduction [Write one or two paragraph/s describing the business for which your teams is developing an information system) Creating a fashion and clothing design system where it has the ability to accept orders from the buyers, buyers having access to multiple collections of clothes and accessories to choose from and being able to process online payments directly and contact the system management team via live chat. Problem (Describe the business problem that requires an information system] Trying to find a wide a variety of clothing collections with the ease of access for the end user where they can browse products with filtering of prices from highest to lowest and vice versa, pay directly to the vendor through the system itself (Fashion Management System) by having an integrated payment processor and being able to contact the system's team instantly. Stakeholders Categorizing Stakeholders [Who are the stakeholders of the system? Categorize them within the following 4 categories] Operational Executive Internal Staff(IT & Accounting) Fashion System manager End user(Buyer) Investor External Stakeholders Functions of interest [For each stakeholder, explain what aspect of the system are of particular interest] -IT Staff: Maintaining the system from lagging and bugs, handling the traffic that occurs from the users, programming the back end of the system and designing the front end of the system. -Accounting Staff: Handling the revenue and profit margins, performing a cost/benefit analysis to estimate the strengths and weaknesses of the system from a financial standpoint. -Fashion system manager: Managing the full system from hiring the staff, assigning them to their respective duties with a fixed schedule and budget, creating the policies and guidelines, assessing and evaluating the performance of the team and monitoring the project. -Buyer: Searching and browsing for clothes and accessories within different categories, pay for products, provide feedback and reviews and chat with customer support if any issues occur. -Investor: Funding the system to stay operational and sustainable, provide expertise and advice, and provide connections that can help accelerate the business. System Capabilities [Identify the major subsystems of the proposed information system, and for each subsystem list the main capabilities] Dashboard: ability to see an overview of the system from sales, reviews and orders.(System management side) Products: ability to upload products to the system with price, status (in or out of stock), SKU (Stock keeping unit). (System management side) Orders: ability to handle orders from completed to failed. (System management side) Reports & Analytics: ability to check the sales from top selling to least selling and analyzing the sales day by day.(System management side) Return or Refund request: ability to handle refunds or return request from clients.(System management side) Purchasing: ability to buy products with one click or adding to cart.(End User side) Payment gateway: ability to pay directly within the system.(End User side) Review: ability to give feedback for each product.(End User side) Live chat: ability to communicate instantly with customer support.(End User side) . Identifying Use Cases with User-Goal Technique [For each subsystem, list all potential users and identify the different use cases for each) Subsystem 1: .... User Use Case (add/remove rows as needed) Subsystem 2: User Use Case (add/remove rows as needed) Subsystem 3: User Use Case (add/remove rows as needed) Identifying Additional Uses Cases with Event-Decomposition [Apply the event-decomposition technique to identify additional use cases that you may have missed using the user-goal technique. Focus on temporal and state events.] Event Actor/s Use Case Event type (External/ Temporal/State) (add/remove rows as needed) Use-Case Diagrams per Subsystem (Draw a use case diagram showing all use cases of each subsystem) Use-Case Brief Description [For each use case provide a brief description] Use-Case Actor/s Brief Description a