html5-img
1 / 20

Plan

Plan. Analyze. Systems Development Life Cycle . Design. Dirty Dirt Bikes Website SDLC. Develop. Test. Implement. Alec Lienemann Jonathan Wright Shuai Zheng. Maintain. Project Plan System Requirements. Plan. Analyze.

landen
Download Presentation

Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Plan Analyze Systems Development Life Cycle Design Dirty Dirt Bikes Website SDLC Develop Test Implement Alec Lienemann Jonathan Wright ShuaiZheng Maintain

  2. Project PlanSystem Requirements Plan Analyze • The website needs to be modular and easy to update with our latest product offers. • The website should allow customers to create an account with us so they can login, search for products, customize certain products, create wish lists, save their shopping cart, and track order progress. • Website feedback should be easy to leave and easy to read. Design Develop Test Implement Maintain

  3. Project PlanCritical Success Factors Plan Analyze • Intuitive navigation • Accessible customer service • Easy to view website feedback • Transparent order tracking • We want customers to know the progress of their order. Design Develop Test Implement Maintain

  4. Project PlanFeasibility Studies Plan Analyze • Economic Feasibility • Allows us to ascertain the profitability of an online store for our company. • Enables us to know what the overhead costs will be for supporting our website. • Schedule Feasibility • Performing the schedule feasibility study allows us to set realistic deadlines that we should meet. • This study also gives us a timeframe for when we should be completing the project as a whole as well as the likelihood of it being completed on time. Design Develop Test Implement Maintain

  5. Project Timeline / Milestones Plan Analyze • November 23, 2012 – System requirements and critical success factors determined • December 1, 2012 – Feasibility studies completed • January 20, 2013 – Preliminary website design finished • February 1, 2013 – Begin alpha testing • February 15, 2013 – Collect feedback from alpha testers • March 1, 2013 – Begin revising website based on feedback • April 5, 2013 – Website revisions complete • April 28, 2013 – Begin beta testing • May 26, 2013 – Collect feedback from beta testers • July 20, 2013 – Finish revisions from beta test feedback • August 1, 2013 – Begin work on website product catalog • September 18, 2013 – Integrate website inventory with physical store’s inventory • October 21, 2013 – Full product catalog complete • October 28, 2013 – Rigorous website testing completed • November 1, 2013 – Launch website Design Develop Test Implement Maintain

  6. Project AnalysisBusiness Requirements Plan Analyze Business requirements came from what we believed would be valuable to us as well as what we believed our customers will value. • Website navigation must be intuitive. • Customer accounts must retain order history along with all other customer provided information. • Customers must be able to easily delete stored information from their account (such as credit cards). • Order process must be secure. • Orders must be easily tracked by the customer. • Product catalog must be easily searchable and sortable. • Website feedback must be easy to provide. • Customer service must be readily accessible. Design Develop Test Implement Maintain

  7. Process DiagramLogin Plan Analyze A customer logs into the system by entering a user ID and password. If they are an existing user and their password matches they may proceed to view and purchase products. If the customer is a new user they may create an account which is then added to the user database. They will then be recognized as an existing user and will now be able to view and purchase products. Computer Customer Design Develop Test Implement Maintain

  8. Process DiagramViewing Order History Plan Analyze Computer Customer A customer attempts to login to the website. If they are a new customer they may create an account which will then be added to the user database. If an invalid login is attempted the user must try again. Once the user, new or existing, has logged in they may access their order history. This queries the order database and any existing orders are viewable by the customer. New users will have no orders to display. Design Develop Test Implement Maintain

  9. Project AnalysisBuy vs. Build Analysis Plan Analyze We decided to buy rather than build our system. Our main reason for choosing to buy was time to market. We weren’t confident we could build and program the website and underlying databases in a timely fashion or very well. Buying allows us to focus on designing the website navigation and aesthetics instead or worrying about everything under the hood. We believe this will allow for a better experience for our customers. We will still be able to edit everything the customer sees with Expression Web. Design Develop Test Implement Maintain

  10. Plan System Model - Website Analyze Logo Business Name Design Develop Home | Login | About Us | Products | Clearance Body Test Implement Privacy Policy Maintain Comments Contact Us

  11. Plan System Model – ER diagram Analyze Customer Order Design Develop Destination Payment Test Implement Maintain

  12. Plan Analyze Design Develop Test Implement System Model - Navigation Maintain

  13. Plan Website Prototype Analyze Design Develop Test Implement Maintain

  14. Plan Website Prototype Analyze This is what we chose for our prototype website. We chose this because it is fast and easy for customers to access our online store. With the help of expression web we will easily be able to make changes to help people in the future. Design Develop Test Implement Maintain

  15. Screen / Form Tested Home page Date Tested November 26, 2012 Tester Alec Lienemann Clearance link Comments link Log in Test Condition Contact Us link Clicking on the comments link will lead to the comments page which displays customer comments from the last month and lets you leave your own. The website will be able to correctly match my username and password allowing me to successfully login. Expected Results Any product in stock that is marked down from MSRP more than 20% will be listed on the clearance page. The contact us link will use mailto: to open the client’s default mail program with our company email in the ‘to’ field. Actual Results Default email program was opened with company email in the ‘to’ field. The comments page opened, displaying test comments and I was able to leave a new comment as well. All products discounted at any rate appeared on the clearance page, including items only 1% off MSRP. The website recognized my username and password and allowed me to login. Pass Fail Pass Fail Pass Fail (Circle one) Pass Fail Plan Testing Analyze Design Develop Test Implement Maintain

  16. Implementation Plan Analyze • We will use plunge implementation. Because all the selling processes is online and independent. • We will train all employees to master the way how to produce databases, how to deal with different forms of payments, how to use VBA, and how to communicate with our customers and solve their problems. • All of the training is online group training. There are theory documents and fact example offered. • When the employees complete the training, they will involve in Company Operations. They also will help other new employees to complete their training. Design Develop Test Implement Maintain

  17. Implementation Plan Analyze • User Documentation • Return customers: customers should use their user ID and Password to login. Then they can add anything they want into the shopping cart. If it is the first time you order a product, the personal information and payment methods is required. If you have order history you can choose to use the history information. • New customers: New customers need to create an account. To create an account, personal information is required, such as, name address, city, state, zip, e-mail address, phone number. • Payment methods: We accept Visa, MasterCard, Discover and American Express. Customers can use any payment methods above. • Shipping method: We only offer FedEx. There are three different forms. Free : 4-7 workdays, General(5$) : 3-4 workdays, Expedited(15-20$) : 1-2 workdays. • Orders: a confirmation E-mail will be sent to customers E-mail address, when the order has been placed. Through this e-mail customers can track their shipment, feedback, change their shipping details or return the goods. Design Develop Test Implement Maintain

  18. Maintenance Plan Analyze • To maintain the website and system. We will renew every system and websites monthly, we will copy all of the customers’ database weekly as the backups . We will also check the purchase processes once daily. When we decide to change our websites or change the systems, it must be agreed by every founders. • We have built a help desk with a great IT group. System users can contact them through the E-mail and call phone when there is an issue during their purchasing. • Once there is a new business requirement we will make changes to increase our system throw through the Adaptive maintenance. And for that we will review our website see there any thing to change weekly. • For corrective maintenance, we will repair any system defects, and also to check the system monthly, the IT group will deal with the defects, make sure there is no problems when the system is using • For perfective maintenance. We will focus on the new methods which can enhance the system and improve processing performance and usability. Once we have, we will change it in the end of that week. • For preventative maintenance system backups are created weekly in case of a failure or crash. Design Develop Test Implement Maintain

  19. Maintenance Schedule Plan Analyze • November 01, 2012-December 01, 2012 • Check system program weekly to work out system errors • Test the system weekly, find out the problems during the purchase processes • Effective beginning January 01, 2013 • Renew every system and websites monthly • Copy all of the customers’ database weekly • Test the system weekly • Update periodically Design Develop Test Implement Maintain

  20. References [Dirt Bike Time Lapse Photograph]. Retrieved November 27, 2012, from http://www.tumblr.com/tagged/dirtbike Laudon, K. and Laudon, J. (2012). Management Information Systems: Managing the Digital Firm.  New Jersey: Pearson Education The Systems Development Life Cycle Basics. (n.d.). Retrieved from http://highered.mcgraw-hill.com/sites/dl/free/0073376833/825296/AppendixD.pdf

More Related