Riordan Business-to-Business Web Site

Use Case Scenarios Analysis

In deciding which way to take Riordan Manufacturing’s business-to-business web site use case studies were performed and the top two scenarios were chosen for further analysis. Both scenarios present a way for Riordan to improve raw material ordering through different means. In order to decide which path to take the two scenarios will be discussed in greater detail including a brief synopsis on the technological role involving systems analysis and design, database design, programming, networking, and the web.

Use Case 1
As described before, in use case scenario 1, a Riordan employee would log into a business-to-business web site and place an order with one of our partnered vendors as Figure 1 depicts. The employee logs into the secure website, chooses a vendor from a list, selects from the common list of products purchased from the vendor, chooses a quantity and enters a required by date, the vendor receives notification of an order, verifies credit status or requests credit card information, fills the order, generates an invoice, and ships the order to our warehouse. Use Case 2
In use case scenario 2, as shown in Figure 2, the approach to replenishing key inventory levels resides with the vendor. Triggers in the database alert the vendor via email that the level is at its threshold and then the supplier logs into the secure business-to-business web site, issues an order to ship replenishment supplies to Riordan, verifies credit status, ships the order and sends an invoice. Technological Role
 Systems analysis and design – In order to provide the best solution for a business-to-business web site careful analysis of current systems and how to integrate the new B2B solution will need to be completed regardless of which system is implemented. When formulating a business plan, incorporating user-centric methodologies, with smaller steps in the software development life cycle, a more iterative approach will be taken to recognize and correct problems quicker and more efficiently.
 Database design – A new relational database will need to be created that will link to the MRP inventory database as well as the accounting database with vendor information. When inventory levels are at their minimum on-hands levels a reorder trigger is reached and the proper employee is alerted to submit the order for replenishing stock and the order is placed as described in Figure 1. Normalizing the database and creating the links to existing tables in other systems will be necessary to ensure “data dependencies make sense” (Chapple, Database Normalization Basics, para. 3).

If scenario two is chosen, a client app will be developed for the selected partnering vendors for ease in verifying inventory levels and submitting invoicing. A link will be needed between the MRP and the new database in order to trigger an emailed notification to the appropriate vendor and a link to accounting will be established so that the vendors can upload invoices directly. The business-to-business solution would include notification to accounting when a new invoice is submitted.

Entry forms and reports will be created for regardless of which use case Riordan decides to go with in order to make data entry easiest (like adding new materials or changing vendors) as well as to run necessary reports whether for weekly inventory checks, monthly order analysis, or annual costs.

 Networking – The company network will need to be analyzed and revamped in order to be able to view inventory levels, run reports or execute SQL scripts at any Riordan Manufacturing location quickly and with the least amount of failure. Riordan Manufacturing is already in the process of having the company network updated, and this is even more important when working without outside vendors. Security is the first consideration when allowing another company access to even a smaller portion of the corporation network. Proper authorization will need to be implemented as well as having a recovery plan in place.

 The Web – The Web plays a vital role in facilitating the business-to-business web site, without it, Riordan Manufacturing and its select vendors cannot communicate via an information system. If use case scenario two is chosen there are two ways that Riordan can allow communication from its chosen vendors. The vendor can either have VPN client software that they initiate before attempting to connect to the ordering portion of Riordan’s MRP system. The VPN would terminate after the vendor logs off. The other method that would be more desirable in a partnership is to have a site-to-site VPN connection, which would be faster and more reliable (Rodriquez, 2008, para. 3). If the company decides to go with the first scenario then no VPN connection is necessary unless required by the vendor.