Reference no: EM132111164
Provide periodic safety reports to the Commonwealth of Pennsylvania certifying its rides have passed inspection. They must also keep a record of all safety-related incidents (such as accidents) for each ride. This information also has to be ready for "surprise" audits that can occur any time.
An incident involves both a ride and an operator. All operators and rides are included in the database whether or not they've been involved in a safety incident, and the date and shift are recorded each time an operator runs a ride at the park. A ride is described by a name and type.
An operator is described by their first and last name. When an incident occurs, its date and time are recorded along with a description of the incident.
Operators must be trained and certified on the rides they operate. An operator can be certified for multiple rides, and the certification is valid for two years from the date they complete their training.
The title of the certification indicates the ride for which they are certified. When an incident occurs, it is important that the park can produce a list of current certifications for the operator.
Inspection records are also recorded in the database.
An inspection occurs at a particular date and time, with a numeric score from 1 to 5, and notes about the outcome of the inspection.
There is only one ride per inspection, even if multiple inspections are done by the same inspector on the same day and time. The information that needs to be recorded about the inspector is their first and last name.
Create an ER Diagram with the correct The correct identification of entities and attributes.
The correct identification of relationships between your entities.
The identification of cardinality between entities.
|
Prompt the user to type in a string of characters
: Return the position of the string and print the message "found" and its position in the text onto the screen either in a Message Box or to the Console.
|
|
How exception handling can be used to solve the problem
: You don't need to be overly detailed, just make sure you could use exception handling to solve it.
|
|
Describe the relationship and discuss if the disjoint rule
: Describe the relationship and discuss if the disjoint or overlap rule would apply to your example.
|
|
Analyze the best algorithm for sorting an array
: Provide the running time and pseudocode to analyze the best algorithm for sorting an array of n very very large numbers in the range 1 through n.
|
|
The identification of cardinality between entities
: An inspection occurs at a particular date and time, with a numeric score from 1 to 5, and notes about the outcome of the inspection.
|
|
Provide the entity relationship diagram
: The hospital has many employees, for each employee we keep the ID (unique), first, and last names, job title, salary, and the office number.
|
|
Write down the network prefix of each subnetwork
: Of the 5 subnets, select the 1st one and write down the first usable address, the last usable address, and the broadcast address.
|
|
Describe how you would work around the types limitations
: Provide five specific examples of data that cannot be stored within Java's eight primitive data types.
|
|
Provide an original example of proper normalization
: Provide an original example of proper normalization and one for poor normalization. Include SQL operations that would be more/less efficient for the examples.
|