YOU ARE DOWNLOADING DOCUMENT

Please tick the box to continue:

Transcript
Page 1: Nomo1 Database Proposal Final

Database Design Proposal

for  NOMO Auto Group

teamSOLUTIONSMartin Castner, Bryant Crone, Mike Holden,

Brianna Malcolmson, & Josh Wentz

1October 26, 2009

Page 2: Nomo1 Database Proposal Final

teamSOLUTIONS

TEAM ROLE BACKGROUND

Josh Wentz Project Manager Architectural Engineering

Bryant Crone Database Administrator

IST

Martin Castner Web Developer IST

Brianna Malcolmson

Security Director

Security Risk Analysis

Mike Holden Business Relations Director

Health & Policy Administration

2teamSOLUTIONS

Page 3: Nomo1 Database Proposal Final

project manager

Josh Wentz

3

Page 4: Nomo1 Database Proposal Final

existingPROBLEMS DE-CENTRALIZED

each of the dealer’s inventory information is contained within their own location and is not centrally located for distribution

using an Excel spreadsheet at each dealership INACCESSIBLE 

if one person has the spreadsheet open and is entering data, others can’t get access to it people will save personal copies of the spreadsheet for their own use

STATIC go and actually find the car to double check spending too much time and money making phone calls and faxing inventory sheets between

dealerships Not all of the salespeople update the spreadsheets at each location in a timely manner update the main spreadsheet at the end of each month

INSECURE every employee should not be able to access certain information

SUSCEPTIBLE TO INPUT ERRORS forgetting to go back and enter data into it or entering incorrectly = inaccurate data

COMPLICATED dealership doesn’t really have anyone who specializes in the spreadsheets who can show us

how to efficiently work with them

4teamSOLUTIONSANALYZE DESIGN DOCUMENT DEVELOP

Page 5: Nomo1 Database Proposal Final

5

existingPROBLEMS

teamSOLUTIONSANALYZE DESIGN DOCUMENT DEVELOP

projectSOLUTIONS

DE-CENTRALIZED

CENTRALIZED

INACCESSIBLE ACCESSIBLE

STATIC REAL-TIME

INSECURE SECURE

COMPLICATED USER-FRIENDLY

Page 6: Nomo1 Database Proposal Final

projectSOLUTIONS CENTRALIZED

database housed in one location each of the dealer's inventory listing of all automobiles currently owned by NOMO & dealership location

ACCESSIBLE many people can access the database at the same time employees from each location can access the same database

REAL-TIME database is automatically updated throughout each location as soon as someone inputs

information up to date inventory up to date sales information

SECURE keep each individual’s commission private none of the salespeople know what other salespeople are making in terms of

commission SAFEGUARDS INPUT ERRORS

check in the system to maintain data integrity if employee enter a wrong amount for a car we receive

USER-FRIENDLY streamlined & integrated: login, input, compiled 6teamSOLUTIONS

ANALYZE DESIGN DOCUMENT DEVELOP

Page 7: Nomo1 Database Proposal Final

projectSOLUTIONS

CHOICES

7teamSOLUTIONS

DATABASE OPTIONS Analysis

MySQL free, industry standard

IBM’s DB2 UDB Enterprise Edition v7.1 or greater

expensive

Oracle’s Oracle11 database

expensiveDATABASE SERVER OPTIONS

Analysis

Sun Enterprise 450 server expensive

IBM RS/6000 M80 expensive

Dell PowerEdge 2500 cheapestANALYZE DESIGN DOCUMENT DEVELOP

Page 8: Nomo1 Database Proposal Final

database administrator

Bryant Crone

8

Page 9: Nomo1 Database Proposal Final

databaseSOLUTIONS

NEW DATABASEStructure How it relates to original spreadsheetWill directly relate to company needs

9teamSOLUTIONSANALYZE DESIGN DOCUMENT DEVELOP

Page 10: Nomo1 Database Proposal Final

10

Entity-Relationship Diagram

Page 11: Nomo1 Database Proposal Final

web developer

Martin Castner

11

Page 12: Nomo1 Database Proposal Final

webSOLUTIONS

LOGIN PROCESS

WEB INTERFACEAnyone, anywhere, from any computer with

security access can view the database through a web browser

SECURITY

Mock-Up Examples…

12teamSOLUTIONSANALYZE DESIGN DOCUMENT DEVELOP

Page 13: Nomo1 Database Proposal Final

SortableColumnsSimple

Search

13teamSOLUTIONS

Page 14: Nomo1 Database Proposal Final

SimplerData Entry

14teamSOLUTIONS

Page 15: Nomo1 Database Proposal Final

CustomizableReports

15teamSOLUTIONS

Page 16: Nomo1 Database Proposal Final

security director

Brianna Malcolmson

16

Page 17: Nomo1 Database Proposal Final

• YOUR NEEDSo Each employee of NOMO Auto Group

needs access to different parts of the database.

o Data needs to be protected from employees who do not need to access it.

o Data needs to be protected from outsiders trying to attack the system and alter data.

• Secrecy, Integrity, Availability…

securitySOLUTION

17teamSOLUTIONS

Page 18: Nomo1 Database Proposal Final

• 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.o Each employee is assigned a user account name and

password.o To access the database they will need to enter their

user-name and password.o Permissions assigned to each user groupo DBA assigns and updates permissions exclusively

securitySOLUTION

18teamSOLUTIONS

Page 19: Nomo1 Database Proposal Final

USER TYPE CONTACT INFOGROSS SALES, COMMISSIONS

ALL SALESINDIVIDUAL/ PERSONAL

SALESINVENTORY

DBA Y Y Y Y Y

CEO/MANAGER OF SALES

Y Y Y Y Y

GENERAL MANAGER/

OPERATIONS MANAGER

Y Y Y Y Y

SALES PERSON Y N N Y Y

USER DATA READ PERMISSIONS: Y/N?

securitySOLUTION

19teamSOLUTIONS

Page 20: Nomo1 Database Proposal Final

USER TYPECONTACT

INFOGROSS SALES, COMMISSIONS

ALL SALESINDIVIDUAL/ PERSONAL

SALESINVENTORY

DBA Y Y Y Y Y

CEO/MANAGER OF SALES

Y Y N N Y

GENERAL MANAGER/

OPERATIONS MANAGER

Y N N N Y

SALES PERSON Y N N Y N

USER DATA WRITE PERMISSIONS: Y/N?

securitySOLUTION

20teamSOLUTIONS

Page 21: Nomo1 Database Proposal Final

ADDITIONAL PROTECTION • When employee is signed into data base,

password re-entry will be required to view restricted data.

• After five minutes of inactivity, the system will log the user out automatically.o Both are controls to prevent unauthorized

access in the case of a user forgetting to log out after use.

• If a user forgets their password they must request a new one by answering their secret question o Passwords are encrypted and stored in the

database.

securitySOLUTION

21teamSOLUTIONS

Page 22: Nomo1 Database Proposal Final

business relations director

Mike Holden

22

Page 23: Nomo1 Database Proposal Final

businessSOLUTION

Business Relations Directorpotential business impacts Company to client liason

Business Relations Director Company to client liasonHow will the database impact NOMO's business process?Improve management issuesStreamline current processesImprove Inventory controlTrack sales precisionAccessible salesperson contact information Other Business Process Benefits

Will provide training to NOMO employees once the system is implemented

23teamSOLUTIONS

Page 24: Nomo1 Database Proposal Final

the X factor

team SOLUTIONS

24

Page 25: Nomo1 Database Proposal Final

theXfactor

 DESIGNUser-Friendly DesignVisually Appealing Interface

ACCESSAutomatic compilation of sales reportReal-time view of summary for board to view at any time

SUPPORTBusiness Relations Director is there for you

• Liason: Client to Company Security vulnerability scanning on a monthly basis Software update checking dailyOn going tech support (24hr/day)

25

What makes us unique?

teamSOLUTIONS

Page 26: Nomo1 Database Proposal Final

"MySQL vs. SQL Server." Custom Software Development.          Tometa Software. Web. 26 Oct. 2009. http://www.tometa           software.com/mysql_vs_sqlserver.asp.> "MySQL or SQL Server: Look beyond politics and hype when           deciding which to use." TechRepublic Articles. CBS          Interactive Inc., 18 Mar. 2003. Web. 26 Oct. 2009.            <http://articles.techrepublic.com.com/5100-10878_11-           1054385.html>.

bibliography

26teamSOLUTIONS

Page 27: Nomo1 Database Proposal Final

QUESTIONS?

teamSOLUTIONS Martin Castner, Bryant Crone, Mike Holden,

Brianna Malcolmson, & Josh Wentz

27