SDLC: Delightful Dirtbikes

1. SDLC: Delightful Dirtbikes Katey Van Hoosier RahulDhami Emily Cornell

2. Project Plan(System Requirements) • Delightful Dirt Bikes is developing a website for its present customers and also for potential future customers. This website will be useful to customers who want to learn about our company, the services we provide, as well as the different inventory we have. Customers will also be able to purchase our different products through our website. • In order for our website to be successful it must be organized so customers can easily navigate their way around. It must also be easy for administration to make changes to the website, especially when new products become available. The goal of our website is to help expand our business so that hopefully we can put more stores throughout the country. Our website should be a useful tool for customers who may not have time to visit our store front or live in different areas of the country. • Customers who visit our website will be able to browse our different products but will have to become a member in order to buy anything. Membership is free and it is easy to sign up.

3. Project Plan(Critical Success Factors) • Our critical success factors include having a data driven website so changes can be made easily and often. We also need to have a website that is easy to navigate so customers have an enjoyable experience when they visit us. It is also important that our customers are able to contact us with any questions, comments or concerns that they may have about the website, our store, our services or our products.

4. Project Plan(Feasibility Studies) • The two feasibility studies we chose for our website are: • Economic Feasibility Study: This study is a good way for our company to see if a website is going to be more beneficial financially or if it is going to cost our company more than it would if we didn’t have a website at all. • Operational Feasibility Study: This study will help our company figure out if a website is going to help us reach our goal of expanding our company and customer base, or if these things will just remain the same after launching our website.

5. Project Plan(Timeline/Milestones) • March 1, 2013- Project plan and business requirements completed • March 5, 2013- Database model completed and shipped to programmers. • March 11, 2013- Initial prototype completed and ready for testing • March 13, 2013- Final Prototype completed • March 14, 2013- Final Prototype received from programmers • March 16, 2013- User Documentation Due • March 18, 2013- Introduce website to general public

6. Project Analysis(Business Requirements) Our business requirements consist of: • Easy navigation throughout the website • Ability for customers to place orders online and make payments online • Security for customers’ orders and payments • Easy for customers to access and manage account information • Administration must be able to make quick updates and changes to website by tracking customers’ activities and trends in an efficient way • Customers should easily be able to contact us with any questions or comments

7. Process Diagram- Customer Order

8. Process Diagram- Customer Order • When customers first get to our website they can enter as either guests or a user. Guests are able to view products, but in order to make an order customers must become members. If a customer enters as a user they will be redirected to a login page where they will have to enter their user name and password or create an account. After creating an account or logging in customers can return to viewing products. • After selecting the products they want to buy, customers proceed to payment and order confirmation and then choose their shipping options.

9. Process Diagram- Administrative Process of Orders

10. Process Diagram-Administrative Process of Orders • Administrators begin by logging into their company account. They can then view orders that have recently been received. After selecting an order they remove the product from inventory and ship it to the customer. Once this is done, administrators will return to the view orders page and continue the process. If there are no more orders to be processed the administrator exits the system.

11. Buy vs. Build • We chose to buy our website because of time constraint. We want to get our website up and running as fast as possible so we are willing to spend a little extra money to buy from a company who creates websites. Even though we are going to buy are website, we will still be able to build and customize as we move into the future.

12. Systems Model Website LOGO BUSINESS NAME Contact Us About Us Find Us Login Product Catalogue Promotions Home BODY Comments

13. ER Diagram Detailed Order Order Customer Distributor Payment Product

14. Navigation Recently Viewed Contact Us About Us Find Us Home Login Checkout Promotions Product Continue Shopping Product Catalogue Yes Abandon Cart Add to Cart Shopping Cart Privacy Policy No

15. Website Prototype

16. Website Prototype • We chose this prototype because it is simple and easy for consumers to use. They can easily see our inventory and navigate through the website. The website was designed using Expression Web, making it easy for us to go in and make changes to keep the website constantly up to date.

17. Screen / Form Tested Date Tested Tester All phone numbers appear email links open etc. Test Condition Promotional link opens and product deals appear Login to account on company site Contact Us link opens on click Product Catalogue link opens on click Link opens with all deals and links to product catalogue On click of product catalogue, the section will open Expected Results All links open to promotions, and link to product catalogue Actual Results Login was successful Product catalogue opened Phone number appear, email links don’t open Correctly. Pass Fail (Circle one) Pass Fail Pass Fail Pass Fail If username and password are entered correctly, login will occur Delightful Dirt Bikes Website November 27, 2012 Rahul Dhami

18. Implementation • Delightful Bikes is a sales company that is based on selling Dirt Bikes for a profit. Employee hiring will be based on the amount of stores we have. On a per store basis there will be an employee for repairs, 2 employees for sales, and a manager to look over all the managerial aspects of the store. Training method is based on train-the-trainer method. Where existing employees will train new hires at each store. • Trainees will be taught most of the work on the job and taught some tricks on how to increase sales for the store. As a prerequisite, trainees will be required to know basic computer skills so they can work orders online. Online training will occur to use the company computer system to increase efficiency. To be hired you also need to have a basic knowledge of dirt bikes. During training you will be taught the technical aspects of dirt bikes to better assist you during the selling process. • Repair technicians will be trained on how to proper fix dirt bikes no matter what the problem may be. The method to train repair technicians will be workshop training. Where they will be able to learn from an expert how to repair properly. They will be taught how to do it efficiently and help make the riding experience more enjoyable for customers. It will take trainees 2-3 days to be trained to start working alone and will be constantly learning more on the job. • User Documentation: Employees will be given brochure’s to hand out to customers that have our in-store deals and promotion offers. Also they will be given guides to better assist them with questions any customer may have.

19. Implementation • We will use a parallel conversion method. The reason being is that we want the systems to be up and running as soon as possible. With less operational downtime, we will cover the extra costs of implementing a brand new system.

20. Maintenance We maintain our website by running full system scans weekly and updating it monthly. Corrections on the site are made quarterly. Updates to customer information are done weekly to keep databases up to date with customer information and product details. Maintenance of our website is mainly our chief technology officer’s job, but we do keep IT personnel on staff to help with any problems our CTF cannot fix. Future maintenance will include all systems being scanned. Updates to the system will be made monthly. Bi-annually we will update the design of the website and the information based on customer queries. For adaptive maintenance, we will take steps towards keeping our ordering process for customers as efficient as possible. Also, we will make any changes that are needed to keep the website as easy to navigate as possible for both the consumers and staff. Corrective maintenance will be taken care of by the chief technology officer. For preventative maintenance, we will be taken care of by our chief technology officer. They will update software that protects both the customer and the company. Security for the customers, and efficiency and security for the company will be what the CTO will primarily focus on for preventative maintenance. For perfective maintenance, we will keep irrelevant information off our website to keep it as neat as possible. We do not want excess information on the website that does not benefit our customers.

21. Maintenance Schedule March 1st - March 18th • Weekly scans to find issues with system and repair them • Updates to the system • Systems tested weekly to make sure product database is up to date and running properly Effective April 1st • Updates to software bi-annually • Monthly updates to customer and product databases • Webpage design updated bi-annually • Orders and reviews of company checked weekly • Immediate response to questions and input made by customers • Full systems scans monthly to perform data cleansing • Monthly checks to ensure everything on the site is functioning

22. References Laudon, K., & Laudon, J. (2012). Management information systems . Upper Saddle River, New Jersey: Prentice Hall.