Nomo1 Database Proposal Final


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • WHAT WE KNOWinstructional designer, Stan Tocchet, to interview Byron Nelson, CEO of NOMO Auto Group
  • WHAT WE KNOWinstructional designer, Stan Tocchet, to interview Byron Nelson, CEO of NOMO Auto Group
  • Nomo1 Database Proposal Final

    1. 1. Database Design Proposalfor  NOMO Auto Group<br />teamSOLUTIONS<br />Martin Castner, Bryant Crone, Mike Holden, <br />Brianna Malcolmson, & Josh Wentz<br />1<br />October 26, 2009<br />
    2. 2. teamSOLUTIONS<br />2<br />teamSOLUTIONS<br />
    3. 3. project manager<br />Josh Wentz<br />3<br />
    4. 4. existingPROBLEMS<br />DE-CENTRALIZED<br />each of the dealer’s inventory information is contained within their own location and is not centrally located for distribution<br />using an Excel spreadsheet at each dealership<br />INACCESSIBLE <br />if one person has the spreadsheet open and is entering data, others can’t get access to it<br />people will save personal copies of the spreadsheet for their own use<br />STATIC<br />go and actually find the car to double check<br />spending too much time and money making phone calls and faxing inventory sheets between dealerships<br />Not all of the salespeople update the spreadsheets at each location in a timely manner<br />update the main spreadsheet at the end of each month<br />INSECURE<br />every employee should not be able to access certain information<br />SUSCEPTIBLE TO INPUT ERRORS<br />forgetting to go back and enter data into it or entering incorrectly = inaccurate data<br />COMPLICATED<br />dealership doesn’t really have anyone who specializes in the spreadsheets who can show us how to efficiently work with them<br />4<br />ANALYZEDESIGN DOCUMENT DEVELOP<br />teamSOLUTIONS<br />
    5. 5. existingPROBLEMS<br />5<br />projectSOLUTIONS<br />ANALYZEDESIGN DOCUMENT DEVELOP<br />teamSOLUTIONS<br />
    6. 6. 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 />6<br />ANALYZEDESIGN DOCUMENT DEVELOP<br />teamSOLUTIONS<br />
    7. 7. projectSOLUTIONS<br />CHOICES<br />7<br />ANALYZEDESIGN DOCUMENT DEVELOP<br />teamSOLUTIONS<br />
    8. 8. database administrator<br />Bryant Crone<br />8<br />
    9. 9. databaseSOLUTIONS<br />NEW DATABASE<br />Structure <br />How it relates to original spreadsheet<br />Will directly relate to company needs<br />9<br />ANALYZEDESIGN DOCUMENT DEVELOP<br />teamSOLUTIONS<br />
    10. 10. 10<br />Entity-Relationship Diagram<br />
    11. 11. web developer<br />Martin Castner<br />11<br />
    12. 12. webSOLUTIONS<br />LOGIN PROCESS<br />WEB INTERFACE<br />Anyone, anywhere, from any computer with security access can view the database through a web browser<br />SECURITY<br />Mock-Up Examples…<br />12<br />ANALYZEDESIGN DOCUMENT DEVELOP<br />teamSOLUTIONS<br />
    13. 13. Sortable<br />Columns<br />Simple<br />Search<br />13<br />teamSOLUTIONS<br />
    14. 14. Simpler<br />Data Entry<br />14<br />teamSOLUTIONS<br />
    15. 15. Customizable<br />Reports<br />15<br />teamSOLUTIONS<br />
    16. 16. security director<br />Brianna Malcolmson<br />16<br />
    17. 17. <ul><li>YOUR NEEDS
    18. 18. Each employee of NOMO Auto Group needs access to different parts of the database.
    19. 19. Data needs to be protected from employees who do not need to access it.
    20. 20. Data needs to be protected from outsiders trying to attack the system and alter data.
    21. 21. Secrecy, Integrity, Availability…</li></ul>securitySOLUTION<br />17<br />teamSOLUTIONS<br />
    22. 22. <ul><li>Secrecy, Integrity and Availability can all be achieved by creating a individual account system and using Discretionary Access Control to determine who has access to what data.
    23. 23. Each employee is assigned a user account name and password.
    24. 24. To access the database they will need to enter their user-name and password.
    25. 25. Permissions assigned to each user group
    26. 26. DBA assigns and updates permissions exclusively</li></ul>securitySOLUTION<br />18<br />teamSOLUTIONS<br />
    27. 27. USER TYPE<br />CONTACT INFO<br />GROSS SALES, COMMISSIONS<br />ALL SALES<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 PERMISSIONS: Y/N?<br />securitySOLUTION<br />19<br />teamSOLUTIONS<br />
    28. 28. USER TYPE<br />CONTACT INFO<br />GROSS SALES, COMMISSIONS<br />ALL SALES<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 />N<br />N<br />Y<br />GENERAL MANAGER/ OPERATIONS MANAGER<br />Y<br />N<br />N<br />N<br />Y<br />SALES PERSON<br />Y<br />N<br />N<br />Y<br />N<br />USER DATA WRITE PERMISSIONS: Y/N?<br />securitySOLUTION<br />20<br />teamSOLUTIONS<br />
    29. 29. ADDITIONAL PROTECTION<br /> <br /><ul><li>When employee is signed into data base, password re-entry will be required to view restricted data.
    30. 30. After five minutes of inactivity, the system will log the user out automatically.
    31. 31. Both are controls to prevent unauthorized access in the case of a user forgetting to log out after use.
    32. 32. If a user forgets their password they must request a new one by answering their secret question 
    33. 33. Passwords are encrypted and stored in the database.</li></ul>securitySOLUTION<br />21<br />teamSOLUTIONS<br />
    34. 34. business relations director<br />Mike Holden<br />22<br />
    35. 35. businessSOLUTION<br />Business Relations Director<br />potential business impacts <br />Company to client liason<br />Business Relations Director <br />Company to client liason<br />How will the database impact NOMO&apos;s business process?<br />Improve management issues<br />Streamline current processes<br />Improve Inventory control<br />Track sales precision<br />Accessible salesperson contact information <br />Other Business Process Benefits<br />Will provide training to NOMO employees once the system is implemented<br />23<br />teamSOLUTIONS<br />
    36. 36. the X factor<br />team  SOLUTIONS<br />24<br />
    37. 37. theXfactor<br /> DESIGN<br />User-Friendly Design<br />Visually Appealing Interface <br />ACCESS<br />Automatic compilation of sales report<br />Real-time view of summary for board to view at any time<br />SUPPORT<br />Business Relations Director is there for you<br />Liason: Client to Company <br />Security vulnerability scanning on a monthly basis <br />Software update checking daily<br />On going tech support (24hr/day)<br />25<br />What makes us unique?<br />teamSOLUTIONS<br />
    38. 38. &quot;MySQL vs. SQL Server.&quot; Custom Software Development.<br />          Tometa Software. Web. 26 Oct. 2009. http://www.tometa<br /> ;<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;           1054385.html&gt;.<br />bibliography<br />26<br />teamSOLUTIONS<br />
    39. 39. QUESTIONS?<br />teamSOLUTIONS<br />Martin Castner, Bryant Crone, Mike Holden, <br />Brianna Malcolmson, & Josh Wentz<br />27<br />