Plan Design Analyze Develop Test Implement Maintain Systems Development Life Cycle Lazy Bean Tabitha Briscoe Dustin Frank Nicole Murphy

Plan Design Analyze Develop Test Implement Maintain Project Plan Critical Success Factor: Profits and Customer Service Who: Users: customers; Controllers: owners What: Allows for products and information to be posted and viewed online. When: Prior to grand opening of physical store so that future customers are aware of store progress System Overview: The product will be designed, manufactured, ordered, recorded into inventory, and then posted to the website for customer order. Customer will access the website, view product list, and order products from website using PayPal or another form of payment that will allow customers to pay with credit. The order information will be provided to the owners who will then gather product and ship it to the customer. An verification and confirmation number will be sent after product is shipped. Information about the business and events will be collected and organized by owners and then posted to the website. It will then be viewed by our customers that enter the website. Project Feasibility: Financial Feasibility: Initial cost of hiring someone to set up the website and website photographs for the website. A cost-benefit analysis will be performed to see if the profits from the online sales will cover the costs of the accounting system. Technical Feasibility: Due to outsourcing the system the technical feasibility of incorporating the website is probable because the professional will have the skills to incorporate the system into a business plan. Timeline: Jan 1 – Cost-Benefit Analysis calculations take place Jan 5 – Website creator/designer researched and hired Jan 8 – Professional photos taken and sent to designer Jan 10 – Website prototype testing Jan 15 – Website completed and website training and access begins Jan 20 – Website is officially running and the store opens

Plan Design Analyze Develop Test Implement Maintain Analysis Business Requirements This system will be able to allow the owner to connect to its products, supplier, and keep track of inventory as it moves through the business. The system will keep track of inventory as it is bought and sold within an inventory database, allowing the owner to buy more when necessary. This system will also permit the owner to connect to its customers by allowing customers to place orders, and buy products from the company. The business requirements will be prioritized by, first, connecting to the customers and allowing them to make purchases from the company. Second, will be connecting to the database making it easier to keep track of inventory as it is bought and sold. Finally, connecting to the supplier and ordering the inventory.

Purchase Inventory Orders Product Send Product Use Case Owner purchases inventory from supplier and posts to website Customer views website and places order for products Order is viewed by owner and payment processed Customer’s order is then processed and the product is shipped

Submit Order Order Lazy Bean Inventory Receive Order Order Information Plan Design Analyze Develop Test Implement Maintain Inventory Database After logging in, the owner can submit an order from predetermined order information to the inventory supplier. The supplier ships the order and owner receives the new product(s). The inventory is posted to the website and updated within the inventory database. The database will reflect low inventory allowing the owner to submit a new order with the supplier when necessary. Activity Diagram Supplier Contact Inventory *LOGIN Post Inventory to website Owner Computer

Ordering Inventory Plan Design Analyze Develop Test Implement Maintain Order Once the customer order is entered, the inventory database is updated. Once the inventory database is updated the customer makes their payment. After the payment has been received for the order, the customer will receive an invoice. Use Case / Activity Diagram Make Payment Inventory Database Order Entered Customer Invoice Sent CustomerComputer

Sending Product Plan Design Analyze Develop Test Implement Maintain Once the order is placed it will be processed via the inventory database. After the order is processed the inventory will be shipped to the customer. Once shipped, the customer will be given a shipping confirmation. Use Case / Activity Diagram Process Order Inventory Database Customer Order Received CustomerComputer Ship Order Owner Send Customer Shipping Confirmation Order Database

Plan Design Analyze Develop Test Implement Maintain Analysis Buy vs. Build For all products to be listed on the website, as well as the design and build of the system itself, we will be buying as opposed to building. It would be too costly to purchase the necessary equipment needed to make the products we want to sell. For example, the costs of buying a screen printing machine and housing it for t-shirt production would outweigh the cost of ordering from a supplier. For the development of the program and website, we will hire a professional. The quality of the site will be better than anything we could build ourselves and the payment processes more professional.

Plan Design Analyze Develop Test Implement Maintain Design System Model - website

Plan Design Analyze Develop Test Implement Maintain System Model – ER diagram Customers may have many or no order information, but orders need one or more customers. Inventory and order information change each other directly Inventory, orders, and supplier orders/information have one to many relations with financial data Products can have one to many relationships on inventory, but inventory does not affect product information DATABASES: Product Information Supplier Info Inventory Financial Data Order Information Customer Data

Plan Design Analyze Develop Test Implement Maintain System Model– Navigation

Plan Design Analyze Test Implement Maintain Develop Website Prototype We chose this as our website prototype to show our customers the interior space and atmosphere of the Lazy Bean coffee shop. This design is easy to navigate, giving potential customers access to information such as the company’s contact information, as well as who we are and when the coffee shop is open. Most importantly, this design allows customers to purchase products that are sold online. Develop

Plan Design Analyze Develop Test Implement Maintain Testing To determine how many orders can be handled at once… Screen / Form Tested Date Tested Unit Testing January 10, 2015 Tester Administrator Test ConditionExpected ResultsActual Results(Circle one) The website can handle 1-5 orders at a single time. The website should successfully process the orders. The website successfully processed the orders Pass Fail The website can handle 5-10 orders at a single time. The website should successfully process the orders. The website successfully processed the orders Pass Fail The website can handle orders at a single time. The website should successfully process the orders. The website successfully processed the orders Pass Fail The website can handle orders at a single time. The website should successfully process the orders. The website failed to process the orders Pass Fail

Plan Design Analyze Develop Test Implement Maintain Testing To ensure website is synched with inventory database… Screen / Form Tested Date Tested System Testing January 11, 2015 Tester Administrator Test ConditionExpected ResultsActual Results(Circle one) When one product is purchased, one less product is available in the inventory database. One less product should be available in the inventory database One less product was available in the inventory database Pass Fail When five products are purchased, five less products are available in the inventory database Five less products should be available in the inventory database Five less products were available in the inventory database. Pass Fail When 10 products are purchased, ten less products are available in the inventory database 10 less products should be available in the inventory database 10 less products were available in the inventory database Pass Fail When 20 products are purchased, 20 less products are available in the inventory database 20 less products should be available in the inventory database 20 less products were vailable in the inventory database Pass Fail

Plan Design Analyze Develop Test Implement Maintain Testing To ensure browser capability… Screen / Form Tested Date Tested User Acceptance Testing January 10, 2015 Tester Administrator Test ConditionExpected ResultsActual Results(Circle one) Google ChromeServer responded wellPass Fail Internet ExplorerServer responded Slowly but with Success. Pass Fail FirefoxServer responded wellPass Fail MobileFailServer responded wellPass Fail Successfully be able to place order on this browser Successfully be able to place order on this browser Successfully be able to place order on this browser

Plan Design Analyze Develop Test Implement Maintain Implementation On January 15, 2015, the system will be implemented after testing is finished and the administrators are trained. We will use the train-the-trainer type training to train our employees. In using this type of training, we will have a few system experts, manager and owners, to learn the system and then train all other employees. The training will include simple things such as how to make adjustments to information listed on the site. It will also incorporate more advanced information such as adjusting inventory, prices, payment methods, and products. We will use the phased conversion implementation method. This will allow us to train our employees in phases so that they are not overwhelmed. They will begin by learning the basics and eventually overtime be able to fully understand and manipulate the entire system. Once we have prepared key employees to use the system, we will be able to release the site 100% to the public. There will be an electronic manual and the contact information for the website creators will be available for any problem outside of what was covered in training. During this time we will be preparing for the store to open and implementing marketing strategies to drive people to the site. i.e. coupons, deals, information, etc.

Plan Design Analyze Develop Test Implement Maintain Maintenance We will use a preventative maintenance system to find errors before they become a problem for our customers. The system will constantly be monitored and tested by the owners and IT specialists when necessary. As changes in the business arrive, implementations will be made to the system. For example, when product prices change this will be updated in the system and on the website. As the business grows, we may need to upgrade the system for a larger user base. Maintenance schedule: January – Daily February – 4-6 days/week March – 3-5 days/week April – 1 time per week Beginning in April, the system will be thoroughly checked by owners every Monday morning as long as the system has no further problems. Modifications can be made to this schedule due to changes in the system or system errors. Order page on website will include the contact information for one of the owners in the case of any technical errors.

References Bautzen, P., & Phillips, A. (2011). Appendix D: The Systems Development Life Cycle Basics. In P. Baltzan, & A. Phillips, M: Information Systems (pp. D1-18). New York: McGraw-Hill. Doherty, M. J. (2014). About Informatory Inc. - eBookSharing. Retrieved May 2014, from Introduction to Information Management: Haag, S., & Cummings, M. (2013). Management Information Systems for the Information Age. New York: McGraw-Hill.