1 / 0

Plan

Systems Development Life Cycle . Plan. Analyze. Design. Develop. Test. Implement. Jackpotss Dirt Bikes Taylor Olson Koby Selfridge Collin Shelton. Maintain. Plan. Project Plan – System Plan.

yehudi
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. Systems Development Life Cycle Plan Analyze Design Develop Test Implement JackpotssDirt Bikes Taylor Olson Koby Selfridge Collin Shelton Maintain
  2. Plan Project Plan – System Plan The system we are developing is a website which will allow us to conduct sales of both goods and services for our dirt bike company. With this system, we will be able to process orders and provide some of the online services available through our company. We will also use this system along with other social networks to keep an open line of communication with our customers. We are planning to use our system as an online community for our customers to talk about products and services within the business. (We can then use this as indirect feedback as well.) System requirements – To create and run this system, we are going to need: Website (including, products, services, as well as personal “profiles” which allow the website to be tailored to each individual customer based on previous purchases and activities). Social Networks (Facebook, Twitter, LinkedIn, Flickr, YouTube, etc.) Payment System (PayPal – certified, protected, and trusted). Analyze Design Develop Test Implement Maintain
  3. Plan Project Plan – Critical Success Factors Allow for purchase of goods/services. Allow for delivery of certain available online services. Data-driven website. Community for customers. Communication to owners. Analyze Design Develop Test Implement Maintain
  4. Plan Project Plan – Feasibility Studies Financial Feasibility Study: This study will show if we can come up with the financial support needed to start and run the system. Market Feasibility Study: This study will show if the system will be useful in the market we are trying to enter with the company. We chose these two studies because they seemed to be the most relevant to show us if the implementation of this system would be feasible and beneficial to the start of our new company. Analyze Design Develop Test Implement Maintain
  5. Plan Project Plan – Milestones October 6, 2013 – Underlying Database System of Products/Services is Created and completed. October 12, 2013 – Database System to Store Customer Information is created. October 30, 2013 – Accounts on Social Networks for the Company are created and completed. November 3, 2013– Business Account on PayPal is created. All necessary links between PayPal and bank are established. November 18, 2013 – Functional Website constructed. November 25, 2013 – Appealing Design completed and applied. December 13, 2013 – Maintenance Schedule created. December 15, 2013 – Appropriate testing applied. December 18, 2013 – Website open to public for business. Analyze Design Develop Test Implement Maintain
  6. Plan Analysis – Business Requirements Easy to use/navigate system on all aspects, including: Login Checkout Maintenance Sales Etc. Trusted online payment system PayPal Develop and generate reports on customer activity. Individual Customers All Customers Easy manageability for individual customers. Analyze Design Develop Test Implement Maintain
  7. Plan Analysis – Process Diagram – Customer Login Analyze Design To log into the system, the member will begin by choosing the proper option depending on if they are a new or existing user. If they are an existing user, they will enter in their UserId and Password. The system will then retrieve that information from the Member database and verify the credentials are correct. If they are correct, they can then proceed to viewing/ordering products. If they are a new user, they will create a new account in our member database, then they will proceed to viewing/ordering products. Develop Test Implement Maintain
  8. Plan Analysis – Process Diagram – Customer Order Analyze The customer order process simply adds to the customer login process. After the customer logs in, they will be sent to a product overview. In the product overview they can select the product(s) that they wish to order. Once they have selected everything they are interested in, they will be sent to a page which will show an overview of everything they have selected to order, then it will ask for shipping and payment information. Finally, they will be sent to a page that will confirm their order and provide them with a printable receipt. From their they can log out, or continue shopping, which will send them back to the product overview. Design Develop Test Implement Maintain
  9. Plan Analysis Phase – Buy vs. build Buy Pros: It is easy and ready to go without much preparation for us. We can have a functional system in a much shorter amount of time. Cons: Significantly more cost than building it ourselves, which would cut into some of the other budgets of the company. Build Pros: We have the ability to modify and adjust the system to our liking. We can also have our own maintenance schedule. Building would also be significantly cheaper in the long run. Cons: It would take a lot more time to build a system we are comfortable with and is functional the way we like it. We chose build because we felt like it would be the better choice since we had more flexibility with that option. Analyze Design Develop Test Implement Maintain
  10. Plan Design – system model - website Analyze Login Design Jackpotss Dirt Bikes Logo Develop Test About Us Dirt Bikes Accessories Services Events Contact Us Implement Privacy Policy Maintain Feedback
  11. Purchases User ID Password Plan Design – system model – er diagrams - members Analyze Name Design Address Develop Test Phone Implement Maintain Email
  12. Plan Design – system model – er diagrams - products Analyze Quantity Sold Quantity Product ID Design Make Develop Test Implement Model Color Year Maintain
  13. Plan Design – system model – Navigation Analyze Design Develop Test Implement Maintain
  14. Plan Develop - prototype Analyze Design Develop Test Implement Maintain **DISCLAIMER: http://www.jackpotssdirtbikes.com is not owned by the people in this group. It is an “example” of what the domain could be.
  15. Plan Develop - prototype We chose this type of design as our prototype because we felt that it would be the most appealing to our target market. We have a target market of late teens through twenties. We chose more young-male style fonts and an action picture of a dirt bike. We felt that this would help make our products appealing to our customers. We also chose a design with bigger buttons/words with less clutter because we felt like it would help our users navigate easier through our system. Analyze Design Develop Test Implement Maintain
  16. Screen / Form Tested Jackpotss Dirt Bikes Date Tested December 15, 2013 Tester Taylor Olson, Koby Selfridge, Collin Shelton All items available for Order Logout Test Condition Navigation Ability to create a new Account Expected Results Expected that all items Have the ability to be orderd Expected to follow the Navigation map provided In the design phase. Account is created And information is stored For future login Expected to be brought Back to home page With the option to login Account was created And information was Stored and used for a Future login. 3 items failed to complete The process of being Ordered. Failed to log out and Would simply return To home page. Wouldn’t Log out unless cache Was cleared in browser. Actual Results Navigation accurately Followed map. Pass Fail Pass Fail Pass Fail Pass Fail (Circle one) Plan Test - schedule Analyze Design Develop Test Implement Maintain
  17. Plan implementation Training for our system will not be very extensive. At the time of implementation, the company will have roughly 3 employees. The training will consist of one group training session with the CTO to discuss the capabilities and functions of the system. Any future training for future employees will consist of a simple sit-down meeting with the CTO and the employee. Any questions should be able to be answered by the CTO since this is an in-house system and was developed as such. User documentation will be provided on an as-needed basis. The system is designed to be very user friendly, and since it was built in-house, any questions or problems can be addressed in-house. Analyze Design Develop Test Implement Maintain
  18. Plan Maintenance - types Adaptive Maintenance: adaptive maintenance will be handled by all employees. Changes will be made as seen fit to provide the best experience for both the users as well as the employees. Any constructive feedback given from the customers will also be considered and applied here. Corrective Maintenance: Corrective maintenance will be taken in effect monthly (unless urgent situations arise), and will be handled by the CTO. Perfective Maintenance: Perfective maintenance will be a part of the adaptive maintenance. Feedback from users and employees will be taken into consideration to make the best possible experience. This will be applied as feedback is provided. Preventative Maintenance: The CTO will monitor the system and take note of any problems that persist during the monthly maintenance checks, then handle them as needed. Analyze Design Develop Test Implement Maintain
  19. Plan Maintenance - schedule Initial Tests Applied: December 15, 2013 December 15, 2013 – June 15, 2014 (First 6 months) Weekly tests of the entire system will be performed. Bi-weekly surveys of employees experience taken and changes applied. Monthly surveys of customerexperience (opt-in). June 15, 2014 – Future Semi-annual tests of entire system will be performed. Semi-annual surveys of employee experience taken and changes applied. Annual surveys of customer experience. Software upgrades semi-annually (as needed). Bi-annual filter of databases (abandoned accounts, etc.) Analyze Design Develop Test Implement Maintain
  20. References (2012). Motocross Picture. Retrieved from Trans World: http://motocross.transworld.net/files/2008/10/08/kainoa2.jpg Laudon, K. C., & Laudon, J. P. (2012). Management Information Systems. Pearson. Stalnaker, J. L. (2012). SDLC Project. Retrieved November 27, 2012 from IMGT 2400: http://www.uwyo.edu/imgt2400/fall2012/ sdlcprojectfall2012.htm
More Related