function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
patric.jenniferpatric.jennifer 

Database design question. Help me please, this report writing is my life?

You are the Project Manager of a team of database designers working for a Facilities Management IT Company who will produce a database application for USA Travel. At the moment the department uses standard ER diagrams and normalisation techniques when designing any database systems. The Head of Department wants to invest in some tools to aid with database design and to consider using more advanced design techniques. The Head is also concerned about the security of the application.

Write a report for your Head of Department that discusses:
• The advantages and disadvantages of using advanced techniques such as the Enhanced Entity Relationship (EER) model compared to the traditional approach of using standard ER diagrams and normalisation.
• Evaluates the Oracle Data Modeler and Designer tools. 
This section should discuss the tools and how they aide the development of a database system. Discuss what advantages and disadvantages such tools have.
• Reviews what database specific security issues could affect a database application.
This section should give an overview of what problems could affect a database and what steps can be taken to prevent them.
Include examples where appropriate, which should be based on the USA Travel scenario as far as possible
sfdcfoxsfdcfox
While we would love to help you, this hardly seems like relevant salesforce.com-specific questioning. Salesforce.com does not expose EER to the developer directly (that is, there are basically no references to super/sub-objects, etc). Furthermore, no external salesforce.com developer would have any direct use for Oracle Data Modeler or Designer tools, despite the fact that salesforce.com is powered by an Oracle database. From a salesforce.com perspective, the answers would look like this:

* We use a standard ERD-style relationship. Contacts are related to accounts, for example, as are opportunities. All relationships use foreign keys, and we have one-to-many and many-to-many relationships. Each object is generally discrete, with very little polymorphism (and when there is, it is all magically handled by the application layer without any effort on our part).

* We don't have a need for Oracle Data Modeler or Designer tools. All of our user interface is point-and-click, with very little effort needed on our part. The Schema builder allows us to quickly build objects and entire applications with almost no effort.

* Salesforce.com provides multiple layers of security, including physical database security, internal and external intrusion detection systems, encrypted session keys, unusual login activity (ala security tokens and two-factor authentication), IP address restrictions, time restrictions, possible delegated authentication against secondary authenication sources, secure pages, cross-site scripting protection, session hijacking protection, session IP address locking, record level security, field level security, user permissions and profiles, audit trails for all system transactions, login trail audits, encrypted text fields, dedicated point-to-point connections for system control from central office, and more. A user can't see a single piece of data that the administrator has not granted them access to, cannot modify any record they do not have permission to modify, and cannot erase their tracks or delete records they don't have permission to delete. And, the administrator simply has to point-and-click to gather most of this data and configure a user's permission, but even administrators cannot act without being recorded; every change they make to the system is placed in an audit trail. Salesforce.com may not be the most secure application in the world, but it is certainly close.