Plan

1. Plan Analyze Systems Development Life Cycle Design Hunting Bikes Co. Develop Test Implement Maintain

2. Plan System For Development Analyze • Website- This website is to include an online showcase which will display photos of our bikes along with each bikes specifications. • System Requirements- Our website will require links to our online parts catalog, this is an online database of repair and upgrades for our bikes as well as some universal parts that can be used on other brands of bikes. An online parts store is integrated into the online parts catalog for ease of purchase. There will be digital service manuals integrated with our service videos posted to YouTube. • Critical Success Factors • Website traffic is initially directed to the showcase. • Website allows ease of access to the apparel store online tutorials and parts catalog. • More streamlined customer feedback on products • Aesthetically pleasing layout and color schemes. Design Develop Test Implement Maintain

3. Plan Project Feasibility Assessment • Cost Benefit Analysis- This analysis will help us find what aspects are benefiting our company. It will compare this to our costs. Using this analysis will help us determine what facets of our system is worth keeping, economically speaking. In other words, are we benefitting, or are we losing. We plan on comparing income and costs through data obtained through our website. • Technical feasibility study- We will look at the costs of website, and videos for the system. We will also make a list of necessary jobs needed to maintain and operate our system. We will consider if we have the expertise to accomplish the system ourselves, or if we need to higher out to an outside company. This will by analyzed with the cost of the technical equipment and personnel to see if it is feasible to obtain. • Schedule feasibility study- In this study we will include a timeline of when parts of the system will be completed. This is included in future slides. We will see if the timeline is feasible and appropriate for our needs. Analyze Design Develop Test Implement Maintain

4. Plan MILESTONES: December 1st, 2012- Design stage completed December 8th,, 2012- Decision to build the system ourselves or higher another company December 15th, 2012- Video tutorials created December 22nd, 2012- Video tutorials uploaded January 5th, 2013- Digital Service manuals Created and uploaded January 12th, 2013- Gather data for each model for showcase January 19th, 2013- Gather data and photos for apparel store January 26th, 2013- Outline Site map February 2nd, 2013- Initial website construction initiated February 9th, 2013- Website ready for testing February 16th, 2013- Testing process completion February 23rd, 2013- Website update completed March 2nd, 2013- Feedback mechanisms enabled March 9th, 2013- Feedback mechanisms tested March 16th, 2013- Maintenance schedule planned and outlined March 23rd, 2013- Final approval by CTO March 30th, 2013- Website Launched April 6th, 2013- Regular maintenance initiated. Analyze Design Develop Test Implement Maintain

5. Plan Analysis(Gather business requirements, create process diagrams, perform a buy vs build analysis) Business Requirements: 1.) Needs to be easy for customers to access and use. 2.) Needs an online order and payment system integrated with the online parts catalog, and online signature apparel store. 3.) Needs to showcase our current Bikes. 4.) Needs to give us feedback and customer information 5.) Needs the ability to play specified tutorial videos from YouTube. 6.) Needs to include contact information for customer feedback. Involvement: CFO- Will oversee the budget for operations of the business requirements. CEO- Will oversee and approve all tasks and requirements before they are followed through. CTO- Will Follow through and direct the implementations of technology, and will do everything possible to see that the CEO and CFO’s approved plans are followed through. Analyze Design Develop Test Implement Maintain

6. Process diagram (Login Process to View Products) Plan Login Process computer Analyze Customers will enter their UserID and Password. Those who’s UserID and Password are existing will proceed to view products. Those whose UserID and Password are new will continue to confirm their new UserID and will then proceed to view products. Design Develop Test Implement Maintain

7. Plan Process diagram (Order and Confirm Process) Order and Confirm Analyze Design This is our Order and Confirmation Process. It is linked to the login in order to confirm who is ordering and confirming. After they select their products they are allowed to review their order, then confirm the order. Develop Test Implement Maintain

8. Plan Buy VS Build Analysis We chose to build our website in house. Our CTO is more than capable of overseeing the construction of the website. He has the training needed to fit our needs. This decision will allow us to have more control over the website as far as updating and modifying the content. It will allow us to personalize our website to a greater degree.We will have more control over the cost and scheduling of this process. We have more than enough time on our timeline to allow us to fix all the bugs and kinks in the process. Analyze Design Develop Test Implement Maintain

9. Plan System Model- Website Analyze Logo Business Name Design Develop Login Full Bike Showcase Apparel Catalog Parts Catalog Video Tutorials Contact Us Home Body (Partial Showcase slides) Test Implement Privacy Policy Maintain Comments Contact Us

10. Plan System Model – ER diagram Analyze Design Develop Test Implement Maintain

11. Plan System Model– Navigation Analyze Login home Design Video Tutorials YouTube Check Out Develop Parts Catalog Shopping Cart Test Apparel Catalog Continue Shopping Implement Showcase Abandon Cart!! Contact Maintain

12. Plan Develop Website Prototype Analyze Design Develop Test Implement We chose this as our prototype because this version will provide easy access to all facets of our website for your customers. The partial showcase also previews our custom-made bikes in an appealing way that will draw customers in from the get-go. The design also is eye-catching while maintaining a professional mein. Maintain

13. Screen / Form Tested Full Bikes Showcase Date Tested February 10th, 2013 Tester Lucas Grant CTO Link from Homepage We expect the link on the homepage to direct us to the full showcase. Link back to homepage The link on the showcase to the home would go to home. Test Condition Product description Scrolling between products Expected Results The browser will move smoothly from one product to the next. The scrolling function directed us to the homepage The link directed us exactly to the showcase page The link on the showcase did take us home. Actual Results The scrolling failed, so product descriptions did not appear. Pass Fail Pass Fail Pass Fail (Circle one) Pass Fail Plan Testing –(write the test conditions and perform the system testing) Analyze Design Develop Test • Information about each • product displayed with • the correct graphic. Implement Maintain

14. Plan Implementation We will use a plunge implementation method, since we have no previous online presence. The necessary training for employees will begin after the final approval by the CTO on March 24th and before the website launch on March 30th. There will be minimum employees involved with the web site. The HR department will respond to feedback. Part orders will be taken from the site by the manufacturing department. These employees will be trained over a three-day period. A supplemental training manual will be provided. The customers who use the website will be documented with a userID and password. New users will be required to create a userID in order to place an order. Customer shipping and payment information will be stored with the user IDs. The customers can get help using the website through the contact us feature. Analyze Design Develop Test Implement Maintain

15. Plan Maintenance We will use corrective maintenance to fix problems customers report, problems detected through weekly tests, and problems that are discovered by the manufacturing department. This method will collect data from all users of the website to ensure proper function. Perfective maintenance will be used to enhance the system to ensure proper function and appearance. This will maintain clear viewing of the showcase and catalogs using updated web browsers. Preventative maintenance measures will gather information about future problems from the users as well as predicted issues. It will ensure the web site can handle necessary traffic volumes while maintaining secure access. As the company develops we will need to adapt the website to include new functions. Adaptive maintenance will be used to apply these changes to the web site as they occur and ensure proper functionality. Analyze Design Develop Test Implement Maintain

16. Plan • Maintenance Schedule • During the first month • Daily system tests • Weekly IT meetings • Extra attention to feedback • During rest of the first year • Weekly system tests • Monthly IT meetings • Weekly responses to feedback • Preventative maintenance training begins • During the rest of website’s life • Monthly system tests • Quarterly IT meetings • Weekly responses to feedback • Preventative and perfective maintenance implemented Analyze Design Develop Test Implement Maintain

17. References Camo Solutions. (2012). Camo Patterns. Retrieved November 27, 2012 from www.camo-solutions.com Laudon, K. & Laudon, J. (2012). Management Information Systems: Managing the Digital Firm. New Jersey: Pearson Education. Microsoft Word. (2010). Clip Art. Popfeedback. (2012). Popfeedback. Retrieved November 6, 2012 from www.popfeedback.com Shoutlet. (2012). Shoutlet. Retrieved November 6, 2012 from www.shoutlet.com Vidmap. (2012). Vidmap. Retrieved November 6, 2012 from www.vidmap.de Youtube. (2012). Youtube. Retrieved November 6, 2012 from www.youtube.com