Write a two-page executive summary for your boss explaining how a relational dat
ID: 3776493 • Letter: W
Question
Write a two-page executive summary for your boss explaining how a relational data solution can be applied to a current business problem or area for improvement. Assume that your boss knows nothing about relational database theory. The goal of this summary is to obtain your boss's approval to proceed with your stated project. Do not focus on technical aspects of a database management system. Focus on how the information will be captured, manipulated, managed, and shared, and the value the database brings to the organization. Include brief examples of how other industries (both domestic and international) have successfully used relational databases to increase efficiency.
Your paper must follow all APA Style Guide requirements. All sources must be properly cited using APA guidelines. Include an APA title page and an APA References page. Thes title page and References pages are in addition to the minimum of 2 pages of body text for your executive summary. In your summary you must include an introduction section with a heading, body text topic sections as apprporiate with headings, and a conclusion section with a heading. Note that APA requires 12 point Times Roman font throughout and 1" margins.
Submissions:
1. You should submit your well-organized Word document in the WebTycho portfolio in the Short Paper area before the due date.
2. You should name your paper Yourname_shortpaper.docx.
(18-20 points)
All content is accurate. There were no factual errors.
(14-17 points)
Most of the content is accurate but there is at least one piece of information that seemed inaccurate.
(0-13 points)
The content is confusing or contains more than one factual error.
(36-40 points)
The document is detailed to enable full understanding of the technical problem and the challenges in solving it.
All required components of the paper were included
(28-35 points)
The document is almost sufficiently detailed to enable full understanding of the technical problem and challenges in solving it.
Most components of the paper were included.
(0-27 points)
The document lacked technical depth and detail.
Most required components of the paper were missing.
(18-20 points)
The paper is easy to read, analysis flows expertly
Language is sophisticated without being jargonistic.
(14-17 points)
The paper is well written but suffers from some significant grammatical inconsistencies or spelling errors.
Language is clear but lacks scholarly depth.
There are some lapses in definition and explication of terms.
Segue between points in the analysis are weak
(0-13 points)
Major problems with grammar and spelling.
Language is murky, confused and difficult to follow.
There is a paucity of definitions or context for analysis.
(18-20 points)
Naming, heading, formatting, references and page numbers were excellent throughout the document.
(14-17 points)
Some minor Naming, heading, formatting, references or page numbers were found.
(0-13 points)
Naming, heading, formatting, references and page numbers were poor or missing throughout the document.
Research Paper InstructionsWrite a two-page executive summary for your boss explaining how a relational data solution can be applied to a current business problem or area for improvement. Assume that your boss knows nothing about relational database theory. The goal of this summary is to obtain your boss's approval to proceed with your stated project. Do not focus on technical aspects of a database management system. Focus on how the information will be captured, manipulated, managed, and shared, and the value the database brings to the organization. Include brief examples of how other industries (both domestic and international) have successfully used relational databases to increase efficiency.
Your paper must follow all APA Style Guide requirements. All sources must be properly cited using APA guidelines. Include an APA title page and an APA References page. Thes title page and References pages are in addition to the minimum of 2 pages of body text for your executive summary. In your summary you must include an introduction section with a heading, body text topic sections as apprporiate with headings, and a conclusion section with a heading. Note that APA requires 12 point Times Roman font throughout and 1" margins.
Submissions:
1. You should submit your well-organized Word document in the WebTycho portfolio in the Short Paper area before the due date.
2. You should name your paper Yourname_shortpaper.docx.
Rubric Name: Writing AssignmentExplanation / Answer
Executive summary
From,
name: xxxx
software developer
ID NO:123456789
team name
To,
Name of the Boss
Dept name
Others info
Dear Sir,
Subject: Requesting for executive summary approval, to lead the company into even more success.
Hello Sir, I am here with newly executive summary to overcome current business problem or area for improvement, the plan is called relational database theory.
A relation schema can be thought of as the basic information describing a table or relation. This includes a set of column names, the data types associated with each column, and the name associated with the entire table. For example, a relation schema for the relation called Students could be expressed using the following representation: Students (sid: string, name: string, login: string, age: integer, gpa: real) There are five fields or columns, with names and types as shown above. A relational database schema is a collection of relation schemas, describing one or more relations. Domain is synonymous with data type. Attributes can be thought of as columns in a table. Therefore, an attribute domain refers to the data type associated with a column. A relation instance is a set of tuples (also known as rows or records) that each conform to the schema of the relation. The relation cardinality is the number of tuples in the relation. The relation degree is the number of fields (or columns) in the relation. The user of SQL has no idea how the data is physically represented in the machine. He or she relies entirely on the relation abstraction for querying. Physical data independence is therefore assured. Since a user can define views, logical data independence can also be achieved by using view definitions to hide changes in the conceptual schema. Examples of non-candidate keys include the following: {name}, {age}. (Note that {gpa} can not be declared as a non-candidate key from this evidence alone even though common sense tells us that clearly more than one student could have the same grade point average.) You cannot determine a key of a relation given only one instance of the relation. The fact that the instance is “legal” is immaterial. A candidate key, as defined here, is a key, not something that only might be a key.
The instance shown is just one possible “snapshot” of the relation. At other times, the same relation may have an instance (or snapshot) that contains a totally different set of tuples, and we cannot make predictions about those instances based only upon the instance that we are given. There is no reason for a foreign key constraint (FKC) on the Students, Faculty, Courses, or Rooms relations. These are the most basic relations and must be free-standing. Special care must be given to entering data into these base relations. In the Enrolled relation, sid and cid should both have FKCs placed on them. (Real students must be enrolled in real courses.) Also, since real teachers must teach real courses, both the f id and the cid fields in the Teaches relation should have FKCs. Finally, Meets In should place FKCs on both the cid and rno fields.
It would probably be wise to enforce a few other constraints on this DBMS: the length of sid, cid, and f id could be standardized; checksums could be added to these identification numbers; limits could be placed on the size of the numbers entered into the credits, capacity, and salary fields; an enumerated type should be assigned to the grade field (preventing a student from receiving a grade of G, among other things).
Suppose that we have a ternary relationship R between entity sets A, B, and C such that A has a key constraint and total participation and B has a key constraint; these are the only constraints. A has attributes a1 and a2, with a1 being the key; B and C are similar. R has no descriptive attributes. Write SQL statements that create tables corresponding to this information so as to capture as many of the constraints as possible. If you cannot capture some constraint, explain why. Answer 3.11 The following SQL statements create the corresponding relations.
Eg: CREATE TABLE A ( a1 CHAR(10), a2 CHAR(10), b1 CHAR(10), c1 CHAR(10), PRIMARY KEY (a1), UNIQUE (b1), FOREIGN KEY (b1) REFERENCES B, FOREIGN KEY (c1) REFERENCES C ) CREATE TABLE B ( b1 CHAR(10), b2 CHAR(10), PRIMARY KEY (b1) ) CREATE TABLE C ( b1 CHAR(10), c2 CHAR(10), PRIMARY KEY (c1) ) The first SQL statement folds the relationship R into table A and thereby guarantees the participation constraint.
Thanks for your time, I hope you are understood the plan and I hope I will get good feedback from your side, I am waiting for your approval.
Thanking you
Date: 01/01/0123 Signature of boss Signature of Team Leader
Place: xxxxxx
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.