Literature review matrix for my stats capstone

What columns does my professor really expect in a literature review matrix?

When you open the capstone guide and see “literature review matrix,” the wording is meant to signal a very concrete spreadsheet‑style table. The grader is looking for a grid where each study you cite occupies one row, and each analytical element you need for the two‑way ANOVA lives in its own column. In practice, the matrix should contain the following headings, in this exact order:

• Citation – full APA reference (author, year, title, journal).
• Sample size (N) – total participants and, if reported, the breakdown by the two factors.
• Design – specify “2 × 2 between‑subjects,” “mixed factorial,” etc.
• Independent variables (IVs) – list both factors, their levels, and how they were coded.
• Dependent variable (DV) – the outcome you will test with ANOVA (e.g., reaction time, stress score).
• Normality test – name the test (Shapiro‑Wilk, Kolmogorov‑Smirnov) and report the statistic and p‑value.
• Result of normality check – state “Assumption met” or “Violation (p < .05).”
• ANOVA outcome – F‑value, df, p‑value, and effect size (η² or partial η²).
• Interpretation for your capstone – a one‑sentence note on how the finding supports or challenges your hypothesis.

Every cell must be filled; empty slots are a red flag that you haven’t extracted enough detail from the source. The professor will scan the matrix for consistency (same number of columns for every row) and for the presence of the normality check because that is the statistical hook of your capstone.

How do I avoid the most common formatting and R‑Studio slip‑ups?

The technical side of the matrix trips up many first‑year students because the rubric expects a precise layout that mirrors what you’ll later paste into your written review. Here are the pitfalls you should watch for:

1. Using a word‑processor table with merged cells. The grader’s spreadsheet template will reject merged rows, so keep each cell independent.
2. Leaving the “Normality test” column blank when the article only reports a visual histogram. In that case, note “Histogram only – visual check” and add a footnote that you will run a Shapiro‑Wilk on the raw data yourself.
3. Copy‑pasting R‑Studio output that includes the “>” prompt. Strip the prompt and keep only the numeric results; otherwise the matrix looks like raw console output, not a synthesis.
4. Mixing decimal separators (commas vs periods). Stick to periods for all p‑values and statistics; the rubric penalizes inconsistent formatting.
5. Failing to round consistently. The guide asks for two decimal places for F‑values and three for p‑values. Inconsistent rounding suggests sloppy data handling.

One quick way to guarantee compliance is to set up the matrix in a CSV file first, then import it into your word‑processor. That forces plain text cells and eliminates hidden formatting characters. When you run the normality test in R, use the following snippet so the output is ready to copy:

shapiro.test(yourDV)$statistic
shapiro.test(yourDV)$p.value

Copy the two numbers, round as instructed, and paste them directly into the appropriate cells. This eliminates the “extra brackets” error that many students overlook.

Keeping your matrix safe from similarity checks and academic integrity flags

Because the matrix is a compilation of other authors’ work, the similarity detector can flag it if you paste whole sentences from the original articles. The safe route is to paraphrase the methodological details while keeping the statistical numbers exact. Here’s a mini‑checklist to keep the similarity score low:

• Rewrite the description of each study in your own voice; avoid copying more than three consecutive words.
• Leave the numeric results (e.g., “F(1, 58) = 4.27, p = .043”) untouched – those are factual and cannot be rephrased.
• Quote only the authors’ exact wording if the phrasing is essential for interpretation, and surround it with quotation marks.
• Include a brief “source note” column (optional) that cites the page number; this shows you’re attributing correctly.
• Run the matrix through your institution’s plagiarism checker before submission; if the similarity index exceeds the threshold, replace any highlighted phrasing with a fresh paraphrase.

Remember, the matrix is not a narrative essay; it’s a data‑driven table. The integrity check cares about verbatim copying, not about the numbers you report. By keeping the prose minimal and the statistics exact, you satisfy both the rubric and the plagiarism software.

A week‑by‑week plan to build the matrix without panic

Think of the semester as a five‑stage sprint. Each stage has a clear checkpoint, so you never feel like you’re staring at a blank page for days.

Week 1 – Gather the core articles

Search PsycINFO for “two‑way ANOVA” AND “normality” AND “psychology.” Download five to seven papers that match your capstone topic. Save each PDF in a folder named “MatrixSources.”

Week 2 – Extract the raw numbers

Open the first article, locate the methods and results sections, and copy the sample size, design, IV/DV labels, and the Shapiro‑Wilk statistic. Fill a single row in your CSV template. Repeat for each paper; aim for at least three rows by the end of the week.

Week 3 – Run the R‑Studio checks

If any article does not report a normality test, import the raw data (or a simulated dataset) into R and run shapiro.test(). Record the output in the “Normality test” column. By now you should have a complete set of numbers for all studies.

Week 4 – Write the interpretation column

For each row, write a one‑sentence note that links the finding to your capstone hypothesis. Use language like “Supports the interaction hypothesis” or “Suggests a main‑effect only.” Keep it under 20 words.

Week 5 – Polish and submit

Import the CSV into Word, check that every column aligns, and verify rounding. Run the plagiarism checker, fix any highlighted phrasing, and then attach the matrix to your capstone draft.

Following this timeline means you never have more than a few tasks per week, and the final matrix will look polished and complete.

What does a finished matrix look like, and how can I tell I’ve succeeded?

A completed matrix reads like a concise research log. The rows flow from older foundational studies at the top to the most recent articles at the bottom, showing the evolution of evidence. The following table illustrates a minimal but fully compliant example with three studies:

Success signs:

• Every row contains a complete set of entries; no “N/A” placeholders.
• All numeric values are rounded as the rubric demands (two decimals for F, three for p).
• The “Interpretation” column directly ties each study back to your capstone research question.
• The matrix fits on one or two pages, with clear column headings and no merged cells.

If you can point to this table and say, “I can trace each number back to its source and I’ve checked normality for every study,” you’ve met the professor’s expectations and you’re ready to move on to the narrative literature review.

Which formatting quirks most often send a matrix back for revision?

When you hand in the matrix, graders scan the page for a handful of visual cues. If any of these are off, the whole thing lands in the “needs work” pile, even if the content is solid.

First, column headings must match the rubric verbatim. The guide lists “Study Citation,” “Sample Size (N),” “Design,” “Factors,” “DV,” “Normality Test,” “Result (Pass/Fail),” “ANOVA Outcome,” and “Interpretation.” Swapping “Design” for “Study Type” or abbreviating “DV” to “Outcome” will be flagged.

Second, numeric formatting is strict. The rubric asks for:

• F‑values rounded to two decimal places (e.g., F = 3.45).
• p‑values with three decimals unless they are < .001, in which case write “p < .001.”
• Effect‑size η² to two decimals.

If you write “5.123” or “p=.027” the grader marks it wrong. A quick format() call in RStudio (formatC(F, format = "f", digits = 2)) guarantees consistency.

Third, alignment matters. All numeric cells should be right‑aligned; text cells left‑aligned. This isn’t just aesthetic—reviewers use the alignment to verify that each entry belongs to the correct column at a glance.

Fourth, avoid merged cells or multi‑line headings. The matrix should be a plain grid that can be copied into Word or Google Docs without breaking the layout. If you need extra space for a long citation, use a smaller font rather than merging columns.

Finally, watch the page limit. Most professors want the matrix on a single double‑spaced page (or one‑and‑a‑half if you’re using 12‑pt Times New Roman). If you spill onto a third page, you’ll lose points for “excessive length.”

For example, a sophomore biology major tried to squeeze a 12‑row matrix onto a half‑page by shrinking the font to 9 pt and merging the “Normality Test” and “Result” columns. The professor returned it with a note: “Readability compromised; reformat to meet 12‑pt, separate columns.” After re‑creating the grid with the correct headings and font size, the same student earned full marks.

What’s a realistic week‑by‑week plan to finish the matrix without panic?

Break the task into bite‑size chunks that line up with your class schedule. Below is a six‑day sprint that fits into a typical first‑year semester workload.

1. Day 1 – Gather sources (2 hours). Search your library for the five most recent articles that use a two‑way ANOVA on a psychological outcome. Export the citations to a reference manager; you’ll copy the APA style reference directly into the “Study Citation” column.
2. Day 2 – Extract design details (3 hours). Skim each article’s methods section. Fill “Sample Size,” “Design,” “Factors,” and “DV” columns. If a paper reports a mixed‑design, note “mixed factorial” exactly as the rubric expects.
3. Day 3 – Run normality checks (4 hours). Open the dataset (or simulated data if the raw data aren’t provided). In RStudio, run shapiro.test() for each group, record the statistic and p‑value, and decide “Pass” or “Fail.” Copy the output into the matrix, rounding as described above.
4. Day 4 – Pull ANOVA results (2 hours). Locate the F, df, p, and η² values in the results section. Use the same rounding rules; paste them into the “ANOVA Outcome” column.
5. Day 5 – Write concise interpretations (3 hours). For each row, craft a one‑sentence link to your capstone question: “Because the interaction is significant, stress influences cortisol differently for males versus females, supporting hypothesis X.” Keep it under 25 words.
6. Day 6 – Polish and verify (2 hours). Run a final check:
   • All headings match the rubric.
   • Numbers are rounded correctly.
   • Alignment is uniform.
   • Page count ≤ 2.
   Export the table as a PDF to lock the formatting, then upload.

Following this schedule means you’ll have a clean matrix ready by the end of the week, leaving ample time for the narrative review that follows.

How can I double‑check my matrix before I hit submit?

A quick self‑audit saves you from costly resubmissions. Use the checklist below while the matrix is still open on your screen.

• Column headings exactly match the rubric wording.
• Every numeric entry follows the rounding rules (F = 2 dp, p = 3 dp, η² = 2 dp).
• All “Result” cells read either “Pass” or “Fail” – no “Yes/No” or “N/A.”
• Interpretation sentences reference the specific hypothesis or research question.
• Font is 12‑pt Times New Roman, line spacing 1.5, margins 1 in.
• Table fits within one (or at most two) pages without scrolling.
• Exported PDF displays the same alignment as the original file.

If any item is red, fix it before you upload. A clean matrix not only meets the rubric but also shows the professor that you can follow detailed instructions—an essential skill for any capstone.