Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Nomo2 Final Product Presentation Final

1,759 views

Published on

Published in: Technology
  • Be the first to comment

Nomo2 Final Product Presentation Final

  1. 1. Database Implementationfor  NOMO Auto Group<br />teamSOLUTIONS<br />Martin Castner, Bryant Crone, Mike Holden, <br />Brianna Malcolmson, & Josh Wentz<br />1<br />December 7, 2009<br />
  2. 2. teamSOLUTIONS<br />2<br />teamSOLUTIONS<br />
  3. 3. project manager<br />Josh Wentz<br />3<br />teamSOLUTIONS<br />
  4. 4. scope of work<br />SCALABILITY<br />NOMO Auto Groups is a growing successful organization<br />Our solution will allow for the four existing location to expand even farther<br />MAXIMUM EFFICIENCY<br />The current database system needs to be updated improved to guarantee peak efficiency<br />TECHNOLOGICAL EDGE<br />Maintain a technological edge on competitors through use of a cloud computing type accessible & collaborative database<br />Problems Recap & teamSOLUTIONS…<br />teamSOLUTIONS<br />
  5. 5. database lifecycle<br />teamSOLUTIONS<br />5<br />
  6. 6. existingPROBLEMS<br />6<br />projectSOLUTIONS<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  7. 7. projectSOLUTIONS<br />CENTRALIZED<br />database housed in one location<br />each of the dealer&apos;s inventory<br />listing of all automobiles currently owned by NOMO & dealership location<br />ACCESSIBLE<br />many people can access the database at the same time<br />employees from each location can access the same database<br />REAL-TIME<br />database is automatically updated throughout each location as soon as someone inputs information<br />up to date inventory<br />up to date sales information<br />SECURE<br />keep each individual’s commission private<br />none of the salespeople know what other salespeople are making in terms of commission<br />SAFEGUARDS INPUT ERRORS<br />check in the system to maintain data integrity if employee enter a wrong amount for a car we receive<br />USER-FRIENDLY<br />streamlined & integrated: login, input, compiled<br />7<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  8. 8. personnel resources<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />8<br />
  9. 9. database administrator<br />Bryant Crone<br />9<br />teamSOLUTIONS<br />
  10. 10. existingPROBLEM<br />Spreadsheets = Limited Access<br />Four Dealerships<br />10<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  11. 11. existingPROBLEM<br />11<br />UPDATES<br />UPDATES<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  12. 12. existingPROBLEM<br />12<br />SPREADSHEET<br />A<br />SPREADSHEET<br />B<br />Compare<br />&<br />Update<br />SPREADSHEET<br />A<br />SPREADSHEET<br />B<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  13. 13. databaseSOLUTION<br />Centralized<br />Multiple User Access<br />13<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  14. 14. INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />DBMS selection<br />14<br />
  15. 15. database design<br />15<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  16. 16. 16<br />Entity-Relationship Diagram<br />
  17. 17. SQL coding<br />17<br />CREATING THE DATABASE<br />CREATE TABLE Invoice<br />( invoice_id NUMERIC PRIMARY KEY,<br />customer_id NUMERIC NOT NULL,<br />vin VARCHAR(20) NOT NULL,<br />sale_date DATE NOT NULL,<br />sale_price INTEGER NOT NULL,<br />gross INTEGER NOT NULL,<br />commission INTEGER NOT NULL,<br />employee_id VARCHAR(255) NOT NULL,<br />FOREIGN KEY (customer_id) REFERENCES Customers(customer_id),<br />FOREIGN KEY (vin) REFERENCES Inventory(vin),<br />FOREIGN KEY (employee_id) REFERENCES Employees(employee_id) );<br />COMPILING THE DATABASE<br />INSERT INTO Invoice (invoice_id, customer_id, vin, sale_date, sale_price, gross, commission, employee_id)<br />VALUES (107689, 154012, &apos;1HGFA553XJA126793&apos;, 06-05-2009, 8055, 3555, 1422, &apos;jb1390&apos;);<br />INSERT INTO Invoice (invoice_id, customer_id, vin, sale_date, sale_price, gross, commission, employee_id)<br />VALUES (206956, 154013, &apos;3KRFA733NVX128535&apos;, 06-22-2009, 6000, 1600, 640, &apos;lg3370&apos;);<br />INSERT INTO Invoice (invoice_id, customer_id, vin, sale_date, sale_price, gross, commission, employee_id)<br />VALUES (107690, 154014, &apos;5CMET196OWS475683&apos;, 07-13-2009, 18100, 5100, 2040, &apos;bt2336&apos;);<br />INSERT INTO Invoice (invoice_id, customer_id, vin, sale_date, sale_price, gross, commission, employee_id)<br />VALUES (303981, 154015, &apos;7HGHA553ASR267431&apos;, 09-25-2009, 13330, 4130, 1652, &apos;mp4243&apos;);<br />INSERT INTO Invoice (invoice_id, customer_id, vin, sale_date, sale_price, gross, commission, employee_id)<br />VALUES (405643, 154016, &apos;7IYRW553QOJ012504&apos;, 11-30-2009, 10390, 2990, 1196, &apos;tk1348&apos;);<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  18. 18. web developer<br />Martin Castner<br />18<br />teamSOLUTIONS<br />
  19. 19. web interface<br />19<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  20. 20. PHP queries<br />20<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  21. 21. live demo<br />ONLINE WEB DATABASE<br />http://php.scripts.psu.edu/mic5145/ist210/index.php<br />21<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  22. 22. security director<br />Brianna Malcolmson<br />22<br />teamSOLUTIONS<br />
  23. 23. audience analysis<br />INFORMATION NEEDS<br />Sales <br />Commission <br />Monthly Sales Reports <br />Dealership Contacts <br />Inventory<br />ASSOCIATED USERS<br />CEO<br />Manager of sales<br />General managers and operations managers <br />Sales people <br />23<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  24. 24. organizational structure<br />24<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  25. 25. data analysis<br />Nomo employees and owners require<br />Simple and fast access to <br />Relevant business information that can allow them  <br />Greater efficiency and  <br />Higher accuracy ensuring smarter business decisions<br />25<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  26. 26. security needs<br />Each employee of NOMO Auto Group needs access to different parts of the database<br />  Data needs to be protected from employees who do not need to access it<br />Data needs to be protected from outsiders trying to attack the system and alter data. <br />26<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  27. 27. USER TYPE<br />CONTACT INFO<br />COMMISSIONS<br />SALES REPORTS<br />INDIVIDUAL/ PERSONAL SALES<br />INVENTORY<br />DBA<br />Y<br />Y<br />Y<br />Y<br />Y<br />CEO/MANAGER OF SALES<br />Y<br />Y<br />Y<br />Y<br />Y<br />GENERAL MANAGER/ OPERATIONS MANAGER<br />Y<br />Y<br />Y<br />Y<br />Y<br />SALES PERSON<br />Y<br />N<br />N<br />Y<br />Y<br />USER DATA READ AND WRITE PERMISSIONS: Y/N?<br />securitySOLUTION<br />27<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  28. 28. data access & security<br />Limitations to access the data and data Security<br />Users must have account and password created by the DBA<br />Website is not accessible unless user ID and password are validated<br />Restricted Pages such as Commissions and Sales Reports are not accessible to users without permission.  This was achieved using PHP code to check the user trying to view the page then allow or deny access.<br />28<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  29. 29. business relations director<br />Mike Holden<br />29<br />teamSOLUTIONS<br />
  30. 30. business need & impact<br />Change Management issues<br />Change management issues with moving to a new system<br />Anticipated employee reactions <br />How the new database changes NOMO&apos;s current processes: <br />Inventory control <br />Tracking sales <br />Salesperson contact information<br />30<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  31. 31. organizational planning<br />We will update the system with all previous information kept in spreadsheets<br />Weekly employee training sessions<br />Mandatory for all employees<br />Each session is 1 hour<br />Employees must attend 4 sessions total before go live date<br />Anticipated &quot;go live&quot; date:<br />January 11th 2010<br />Ongoing tech support<br />31<br />INITIAL STUDY DATABASE DESIGN CODING TESTING & EVALUATION <br />
  32. 32. the X factor<br />team  SOLUTIONS<br />32<br />
  33. 33. theXfactor<br /> STRAIGHTFORWARD DESIGN<br />User-Friendly<br />Visually Appealing Interface <br />ACCESSIBILITY & COLLABORATION<br />Access the car inventory database from any web browser<br />Real-time view of summary for board to view at any time<br />ONGOING SUPPORT<br />Business Relations Director is there for you<br />Liason: Client to Company <br />Software update checking daily<br />On going tech support (24hr/day)<br />33<br />What makes us unique?<br />teamSOLUTIONS<br />
  34. 34. &quot;MySQL vs. SQL Server.&quot; Custom Software Development.<br />          Tometa Software. Web. 26 Oct. 2009. http://www.tometa<br />           software.com/mysql_vs_sqlserver.asp.&gt;<br /> <br />&quot;MySQL or SQL Server: Look beyond politics and hype when <br />          deciding which to use.&quot; TechRepublic Articles. CBS<br />          Interactive Inc., 18 Mar. 2003. Web. 26 Oct. 2009.  <br />          &lt;http://articles.techrepublic.com.com/5100-10878_11-           1054385.html&gt;.<br />references<br />34<br />teamSOLUTIONS<br />
  35. 35. QUESTIONS?<br />teamSOLUTIONS<br />Martin Castner, Bryant Crone, Mike Holden, <br />Brianna Malcolmson, & Josh Wentz<br />35<br />

×