Phase by phase, DBAX 9103's fifth deliverable sets out an analysis as run: inputs and outputs, every decision with its rejected options, and whether data had been seen first. Searches like "dbax 9103 week 5 assignment example", "dbax9103 week 5 sample" and "dbax 9103 week 5 example" land here.
What a finished DBAX 9103 Week 5 analysis walkthrough looks like
The walkthrough runs four or five pages under the six phases Braun and Clarke describe: familiarization, coding, generating initial themes, reviewing them, defining and naming them, and writing up. Each phase opens with what went in and what came out, in counts where counts help, such as the number of codes after the first pass. Decision points sit inside the phases as short indented entries with three parts: the choice made, the alternatives considered, and the reason. One entry records merging two candidate themes about supplier risk after the review phase showed they drew on the same passages. Another records keeping a pattern raised by only a few managers as a theme, with the argument that prevalence was never the criterion. A final page separates the decisions made before any transcript was read from those made during analysis.
How a DBAX 9103 Week 5 example is structured
Phases structure the document because they structured the work, and a reader expects to find each decision where it was taken. Within every phase the order is fixed: input, operations, output, decisions. That consistency lets a reader compare phases and notice where the analysis changed shape, which is usually between initial themes and their review. Decision entries appear where each decision arose, not gathered at the end, so the account cannot present a tidy analysis with its choices appended as an afterthought. Each entry states whether it was made before or after the relevant data were examined. A separate section lists the tools used, the analysis software and the codebook versions, with dates. The walkthrough ends where results begin: it names the final themes and stops, leaving what they say to the following week.
Input, operation, output
Each phase states what it received, what was done, and what it produced. The coding phase received familiarization notes and transcripts and produced a first set of codes, listed in the appendix with their dates.
Decisions where they were taken
Decision entries sit inside the phase that forced them. Placing the merge of the two supplier-risk themes in the review phase, where it happened, keeps the sequence honest.
Options rejected
Each decision names what else was possible. Keeping the two risk themes separate was considered and rejected because both drew on identical passages; the entry says so in two sentences.
Before or after seeing the data
Entries are marked as fixed in advance or made during analysis. The choice of reflexive thematic analysis was fixed in the proposal; the decision to treat a minority pattern as a theme came after coding.
Stopping at the themes
The walkthrough closes by naming the final themes and their defining features. What each theme says about supplier consolidation waits for the results section, where it is reported with its evidence.
Where marks go in DBAX 9103 Week 5
Walkthroughs are graded on the decisions, not the phases. Naming Braun and Clarke's six phases and describing each in textbook terms shows the author read the method; recording what happened inside each phase, with choices and their alternatives, shows the method was applied. The merged-theme entry is the kind graders look for, since it records a judgment that shaped the results and gives the reason. Timing earns real credit, because a decision made after seeing which passages supported a theme differs from one fixed in advance, and doctoral readers want to know which is which. Prevalence claims are checked: counting mentions as evidence of importance contradicts the reflexive approach, and a walkthrough doing so draws comment. Stopping before findings is marked as well, and walkthroughs that start interpreting their themes lose that share.
Get a DBAX 9103 Week 5 example written to your instructions
Upload the Week 5 prompt and rubric and name the analysis your study uses, qualitative or statistical. A phase-by-phase walkthrough with dated decision entries follows inside 24-48h, and there is no charge for the first. Your transcripts and codebook stay where they are; the decisions described were made for an interview set that exists only in the sample.
DBAX 9103 Week 5 questions, answered
Does a quantitative walkthrough work the same way?
The shape is the same, with different decisions. Exclusion rules, variable transformations, the handling of outliers and the choice of covariates are the forks in a regression or group comparison. Gelman and Loken called this the garden of forking paths, arguing that choices contingent on the data inflate apparent evidence even when nobody is fishing. Recording each fork, and when it was taken, is the walkthrough's defense.
How much detail does each decision entry need?
Enough for a reader to dispute it on the page. The choice, the alternatives and the reason usually fit in three or four sentences. Longer entries tend to argue for the decision, which belongs elsewhere; shorter ones tend to omit the alternatives, which are what make the entry useful. Under a tight page limit, the phase descriptions shrink before any entry is cut.
Is it acceptable to change the analysis plan during analysis?
Yes, when the change is recorded and explained. Qualitative analysis in particular is expected to adapt as understanding develops. What a reader needs is the plan, the change, the reason and the moment it happened. An analysis that changed without trace looks, on the page, exactly like one shaped to reach a preferred result, and the walkthrough exists to prevent that confusion.