data analysis Writing Assignment Help

ON A MICROSOFT WORD DOCUMENT – ONE PAGE – WRITE ABOUT THE COMPANY’S BACKGROUD IN 1-2 PARAGRAPHS (HISTORY, HEADQUARTERS, PRODUCT LINES, LINE OF BUSINESS, COMPETITIORS)

THEN FOCUS ON MARKETING MIX – SIMPLE BULLETS WILL HELP!

UPLOAD ONE PAGE WORD DOC –

Hiplantro – La Teresita, Colombia, PDF Instructions
Product: Tea
Challenge: New market expansion plan. The company is already attracting clients from multiple countries and is ready to expand into new markets. It is seeking help with developing a market expansion strategy, including identification of new promising markets, optimal market entry mode, cost-effective product promotion and marketing, and staffing decisions.

Week 4 Homework

“Data Visualzation a Practical Introduction”

Do the Exercises in Section 3.8 for the chapter “Make a Plot” https://socviz.co/makeplot.html#makeplot

Start by playing around with the gapminder data a little more. You can try each of these explorations with geom_point() and then with geom_smooth(), or both together.

• What happens when you put the geom_smooth() function before geom_point() instead of after it? What does this tell you about how the plot is drawn? Think about how this might be useful when drawing plots.
• Change the mappings in the aes() function so that you plot Life Expectancy against population (pop) rather than per capita GDP. What does that look like? What does it tell you about the unit of observation in the dataset?
• Try some alternative scale mappings. Besides scale_x_log10() you can try scale_x_sqrt() and scale_x_reverse(). There are corresponding functions for y-axis transformations. Just write yinstead of x. Experiment with them to see what sort of effect they have on the plot, and whether they make any sense to use.
• What happens if you map color to year instead of continent? Is the result what you expected? Think about what class of object year is. Remember you can get a quick look at the top of the data, which includes some shorthand information on the class of each variable, by typing gapminder.
• Instead of mapping color = year, what happens if you try color = factor(year)?

Format for Individual Cases (2 Page MAX – Single Spaced)

Individual case analyses are equivalent to preparing an executive summary of the problem. The following format is REQUIRED:

I.Title Page

II. Recommendation – Short Version

A solution must be recommended and supported by rational arguments.It is important to be able to articulate why a certain solution is recommended and to be able to defend it.There is usually not one correct solution to these case problems. But, there are incorrect solutions. For example, solutions that violate economic principles, or are inconsistent with financial theory, or are based on inconsistent assumptions, or violate ethical or legal standards are not acceptable solutions.Solutions not supported by data are not acceptable solutions.

III.Statement Problem – Do not repeat case – just state the problem to be solved.

[3 Sentences at most]- For this case, lack of cash flow b/c excise taxes

This statement should briefly outline the problem presented in the case. Case details do not need to be repeated.The student should assume that the instructor has read the case. It is analogous to writing a report for a supervisor.

IV.Analysis of Problem – Whats the problem? –> Sales forecast reasonable, running out of cash, problem with A/R & A/P, Etc.

This statement should briefly outline the problem presented in the case. Case details do not need to be repeated.The student should assume that the instructor has read the case. It is analogous to writing a report for a supervisor. DO NOT OUTLINE PROCEDURES.

5. Alternative Solutions- (Exhibit 3 (TM), Exhibit 4 (OM), and Exhibit (Custom)).

This section of the case analysis is where alternative solutions are explored. Pros and cons of different solutions should be presented. Application of theoretical models will be done in this section. Quantitative analysis should be done in exhibits and tables and referenced in this section.

Exhibits/Tables/Charts – Attached. Must be labeled and organized with the paper. For example, Exhibit 1 has to be the first exhibit discussed in the paper. You would never start with Exhibit 4 for example.

We want you to practice a business summary style – writing in a clear, structured manner, but not in paragraph form. If you feel you must write in a paragraph, then address the question at hand in bullets or tables (as appropriate) and then summarize your points in an executive summary-type paragraph. In general, you are attempting to efficiently and effectively make your arguments for a particular solution, describe the associated implementation tasks (“to dos”), identify the benefits and costs of the undertaking, and then drive your point home with additional considerations (risk management).

In this course we will use the term “metadata” (literally: “data about data”) in different ways, but from a DBMS design standpoint metadata describes each database data element and (when used by designers properly) helps ensure every data element’s integrity. Metadata is essential for the quality and integrity of a database and should be found in a document referred to as a “data dictionary” (documentation of data elements in the database).

• Metadata for data elements include:

• a business definition of the data element; what it means in usage within the organization.
• the field type (e.g. text, numeric, data, currency, memo, etc.)
• the number of characters allowed in that field (e.g. data of birth = 8)
• special format requirements (e.g. for US phone number: (617) 373-7288)
• valid values that define and restrict the options for data entry (e.g. for “gender” allowing a response of only “M” or “F”)
• business rules (e.g. the amount of sales tax to enter into a field depending upon the state in the US or the province in Canada where the sale took place)
• ownership for data entry (i.e., what business unit is responsible for input/capture)

At a minimum, a definition and any formatting or input constraints should be provided in any metadata documentation. Not all data elements require all of the aforementioned components of a metadata attributes. For example, the data element “customer last name” requires a business definition, but does not require a fixed number of characters or a format – whereas the “creation date” of an insurance policy initiation would require all three. Metadata adds rigor to the collection of data within a database and helps ensure that the business process and its enabling information system collect the highest quality of data. Later in the course we will discuss the value of metadata in facilitating data/system integration efforts.