4-2 Final Project Milestone Two - Software Analysis and Use Cases.docx - Running head Software Analysis and Use Cases \u2013 Jerryvic Autos 4-2 Final

4-2 Final Project Milestone Two - Software Analysis and Use Cases.docx

This preview shows page 1 - 5 out of 12 pages.

Running head: Software Analysis and Use Cases– Jerryvic Autos4-2 Final Project Milestone Two: Software Analysis and Use CasesJerryvic AutosIT-632 Software Design & ModelingSouthern New Hampshire University
Background image
Software Analysis and Use Cases2Software Analysis & Use CasesActor AnalysisThe software analysis of the automobile dealership Inventory Management software system will contain the implementation of actors and UML use case scenarios. This is made more realistic through the use of UML use case diagrams. According to Larman (2005), use cases are text stories, widely used to discover and record requirements. They influence many aspects of a project including Object Oriented Analysis and Design, and will be input to many subsequent artifacts in the case studies. The actors that are associated with this analysis are as follows: customers, employees, and suppliers.The customers are always the end users of products and services who in this business scenario, want to purchase a vehicle, parts or services for their existing vehicle. It is required that even from the comfort of their homes or offices, they are able to view on online via their smart devicesand PCs, the inventory, check the available options, make their choice and eventually carry out an online purchase and schedule a delivery of the product; they could also, if desired, schedule a date and time to visit the auto dealership to carry out an in-person inspection and test-drive the vehicle before finalizing the purchase. The employees denote all the staff who works at Jerryvic Autos. These will include the Sales Managers, customer service, warehouse, parts and services, along with supervisors (Larman, 2005). The suppliers are also actors in this scenario who supply the dealership’s Inventory stock, thereby enabling them to fulfill customers’ orders. They also provide tracking information for such orders placed either by the customer or the auto dealership.
Background image
Software Analysis and Use Cases3UML Use Case Diagram In fitting together the interactions of the actors with the system, some of the following UML use cases are displayed in the diagram below: Inventory Stock, Inventory details, Orders, Purchases, Customer Login Info, Confirmation, Newly Ordered Supplies and Tracking. Documented Use Case ScenariosUse case scenarios or view is a functional requirements view, which is an input to develop the software architecture. Each use case describes the sequence of interactions between one or more actors (external users) and the system (Gomaa, 2011).
Background image
Software Analysis and Use Cases4Inventory Stock Use Case NameInventory StockActorsCustomers, Employees Description of the FunctionalityCustomers can view and request for a specific product from the stock. Employees get notified of said product and sees if the item is in stock or at the suppliers warehouse.
Background image
Image of page 5

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture