| Course | BU 434 Business Analysis for Project Managers |
|---|---|
| Unit | Unit 8 |
| Paper type | Traceability and validation plan |
| Length | About 790 words, 5 pages |
| Format | APA 7 student paper |
| School | Herzing University |
| Program | BS in Project Management |
| Updated | September 2026 |
Free sample paper for BU 434 Unit 8
Every Requirement Back to a Need and Forward to a Check, Two Orphans Named: A Traceability and Validation Plan for a Composite Printer's Structured Quote Request
Student Name
Business, Herzing University
BU 434: Business Analysis for Project Managers
Instructor Name
May 6, 2026
Every Requirement Back to a Need and Forward to a Check, Two Orphans Named: A Traceability and Validation Plan for a Composite Printer's Structured Quote Request
What This Plan Proves
Nothing new is elicited here. This plan shows that the term's analysis of quoting at Ridgeline Press, a printer that exists only in this course, holds together. Every requirement is linked backward to the need that produced it and forward to the check that will show it was met. Any requirement that links to no need, and any need that links to no requirement, is named rather than dropped. Ramesh and Jarke (2001) found that organizations practicing traceability in depth link requirements not only to tests but to their rationale and sources, and that low-end practice, a table of requirement numbers and test numbers, loses the reason each requirement exists. The matrix below keeps the reason. It also records the one link that goes to an action instead of a requirement, because some needs are met by changing a rule rather than by building anything, and a matrix limited to software would hide them. The plan names who maintains the matrix after launch: the estimating lead, who will add a row whenever a new request is approved, so it does not stop being accurate once the project team moves on.
Two kinds of checking are planned. Verification asks whether the solution was built as the requirements say, and it happens before launch through tests. Validation asks whether the solution solves the problem the business had, and it happens after launch through the business measures. The BABOK guide distinguishes the two in the same way (International Institute of Business Analysis, 2015). A form could pass every test and still leave quotes slow, and only validation would show it.
The Traceability Matrix
The matrix links the problem statement's three measurable parts, through business and stakeholder requirements, to functional and non-functional requirements and their verification checks. Gap numbers refer to the future state analysis.
| Need (problem statement) | Business requirement | Stakeholder requirement | Solution requirement or action | Verification before launch |
|---|---|---|---|---|
| Requests arrive incomplete | BR-1 | SR-1, SR-3 | FR-1, FR-2 | Test: submit with each required field empty; submission must be refused. Test: choose Not sure; request must route to the lead |
| Requests arrive incomplete | BR-1 | SR-1 | NFR-1, NFR-2 | Usability test, five customers; phone width test |
| Quotes wait for clarifying answers | BR-2 | SR-2, SR-3 | FR-5 | Test: send question; customer and rep both receive it; reply attaches |
| Quotes wait for clarifying answers | BR-2 | SR-3 | FR-4 | Test: every submitted field appears in the estimating record |
| Quotes wait for clarifying answers | BR-2 | SR-2 | FR-7 | Test: request status changes appear on rep list within one minute |
| Jobs priced on guessed details | BR-3 | SR-3 | FR-2; G11 policy | Test as above; policy issued in writing |
| Details lost when retyped | BR-3 | SR-4, SR-5 | FR-6 | Test: accepted quote produces a ticket with identical values |
| All | All | All | NFR-3, NFR-4, NFR-5 | Load sample; monitor; accessibility audit |
Orphans at Either End
Tracing backward found two requirements with no business need behind them. FR-8, optional draft file upload, traces to prepress's stakeholder need to see files early, but to none of the three business requirements. It survived because it is cheap and prepress asked for it. It is kept as a could-have, labeled in the matrix as serving a stakeholder need only, so no one later claims it helps the business measures. NFR-6, keeping request records three years with staff-only access, traces to no stakeholder requirement at all; it came from the chief financial officer in a hallway conversation about record keeping. Rather than drop it, the analyst has asked the chief financial officer to state the need in writing so that it can be traced properly.
Tracing forward found one need with no solution requirement. The interviews showed that reps forward incomplete requests because they are judged on response speed. No functional requirement can fix that; it is gap G9, a renegotiation owned by the vice president of sales. It is listed in the matrix as an action rather than a requirement so that it is tracked like one. If G9 is not decided before launch, the plan predicts reps will choose Not sure on every field, and FR-1 will pass its tests while BR-1 fails validation.
The proposed FR-9, an acceptance link in the quote email, traces to SR-4 and awaits the sponsor's approval. Until approved, it sits in the matrix marked as proposed.
Validation After Launch
Validation uses the three business measures, each with a baseline, a data source that already exists or will exist on launch day, and a decision rule set now.
| Measure | Baseline | Target | Source | Checked |
|---|---|---|---|---|
| Share of requests complete on arrival | 41% (sample of 120, late 2025) | 85% by six months | Form records: requests not marked Needs advice | Monthly |
| Median days from request to quote | 2.6 | 1.0 by six months | Timestamps in the estimating record | Monthly |
| Jobs repriced because a detail was guessed | 17 in 2025 | 3 or fewer in first full year | Prepress change log, cause code added | Quarterly |
The decision rules are agreed in advance. If completeness is below 70 percent at three months, the analyst reviews which fields are most often marked Not sure and whether G9 was implemented. If median time is above 1.5 days at three months, the timestamps are split into queue time and clarification time to show which part of the process is still slow. If guessed repricings continue, the analyst checks whether the estimators' spreadsheet is still in use. Wiegers and Beatty (2013) advise defining how success will be measured before a system goes live, since measures chosen afterward tend to be the ones that look good; these were chosen in the problem definition and have not been changed since.
One addition to current records is needed: prepress must add a cause code to each change log entry so guessed-detail repricings can be counted without reading every note. The prepress manager has agreed to start in June, before launch, so the first quarter's figures have a like-for-like comparison. Ridgeline Press, its staff and every measure in this plan are composites written for this course.
References
International Institute of Business Analysis. (2015). A guide to the business analysis body of knowledge (BABOK guide) (Version 3). IIBA.
Ramesh, B., & Jarke, M. (2001). Toward reference models for requirements traceability. IEEE Transactions on Software Engineering, 27(1), 58-93. https://doi.org/10.1109/32.895989
Wiegers, K., & Beatty, J. (2013). Software requirements (3rd ed.). Microsoft Press.
BU 434 Unit 8 instructions, in plain terms
The final BU 434 unit asks students to show that their requirements are complete and connected, and to plan how the solution will be checked. Common requirements are a traceability matrix linking business needs, stakeholder requirements, solution requirements and tests; identification of requirements that do not trace in either direction; an explanation of verification and validation; and a validation plan with measures, baselines and targets. Many instructors expect the student to explain what will be done about unlinked items rather than delete them. Measures should be chosen before launch. The deliverable is typically a matrix and validation table supported by a few pages of APA 7 explanation, drawing directly on the requirements written in earlier units.
How the BU 434 Unit 8 example is put together
The plan opens by stating that nothing new is gathered and explaining why the matrix keeps each requirement's reason as well as its test. It then distinguishes verification from validation. The traceability matrix runs from problem statement to verification check in eight rows, including one action rather than a requirement. An orphans section names two backward orphans and one forward orphan and says what will happen to each, plus a proposed requirement awaiting approval. A validation table sets baseline, target, source and timing for each business measure. The final section states decision rules for missed targets and a change to prepress records needed before launch so the first quarter can be compared fairly.
Where the points sit in the BU 434 Unit 8 rubric
Herzing's traceability rubric typically scores the matrix, the handling of orphans, the distinction between verification and validation, the validation plan and presentation. The matrix earns full credit when links run both backward to needs and forward to tests. Orphan handling is judged on whether unlinked items are named and resolved rather than dropped. The distinction criterion rewards a clear explanation of building the thing right versus building the right thing. The validation plan scores highest with baselines, targets, data sources and decision rules defined before launch. Instructors also credit plans that assign ongoing ownership of the matrix, since traceability that stops at launch cannot support later changes.
Common BU 434 Unit 8 mistakes, and how to avoid them
Traceability plans commonly lose points by presenting a matrix of requirement numbers against test numbers with no link to the business need. Another frequent problem is quietly deleting requirements that do not trace, instead of naming them. Students often confuse verification and validation, or plan only testing before launch and no business measurement after it. Some validation plans list targets without baselines, making improvement impossible to show. Others choose measures after launch, when the temptation to pick flattering ones is strongest. Needs met by policy rather than software are often left out of the matrix entirely. Finally, a plan with no owner after launch leaves the matrix out of date within months.
Get a BU 434 Unit 8 example written to your instructions
Send the Unit 8 instructions and the rubric from your BU 434 classroom, together with the numbered requirement set your section has been working with. We write a custom example whose matrix links both directions, names a real verification method per row, counts coverage and reports the orphans. First custom sample free; turnaround is 24 to 48 hours.
More BU 434 papers and project management samples
- BU 434 Unit 1: Stakeholder identification and analysis
- BU 434 Unit 2: Elicitation plan
- BU 434 Unit 3: Problem definition
- BU 434 Unit 4: Current state process model
- BU 434 Unit 5: Requirements document
- BU 434 Unit 6: Prioritization exercise
- BU 434 Unit 7: Future state and gap analysis
- BU 345 Unit 8: Project closeout file
- BU 396 Unit 8: Risk report to sponsor
- BU 433 Unit 8: Hybrid or scaling analysis
- BU 436 Unit 8: Integrated global project plan
BU 434 Unit 8 questions, answered
What is the difference between validation and verification here?
Verification asks whether a requirement was met as written, and its answer comes from a test, an inspection or a demonstration. Validation asks the earlier question: is this the right requirement set for the problem, and would the people affected agree. One is checked against the document, the other against the need. Rubrics for this unit frequently award points for keeping them apart.
What do I do about requirements that will not link?
Report them. An unlinked requirement is a finding and the plan should name it, say which direction the link is missing, and recommend an action: remove it, find the origin, or take it to the sponsor. Inventing a plausible link to keep the matrix full is common, and a grader who checks two rows will notice. The gap is worth more than the padding.
Could I adapt the traceability template we use at work?
Not the template itself and not its contents. Tools and formats a company built, along with the requirements documents, elicitation notes and interview recordings feeding them, are that company's material and a graded file circulates outside it. Column headings from your course reading will serve, and building the matrix from your own numbered set is what the unit is checking anyway.
Where can I find a free BU 434 Unit 8 sample paper?
The complete BU 434 Unit 8 traceability and validation plan appears above at no charge, with the matrix, the named orphans, the validation table and margin notes. For your own requirements set, email the prompt and a custom plan is prepared free, usually within 48 hours.
What is the difference between verification and validation in BU 434 Unit 8?
Verification checks the solution was built as the requirements say, through tests before launch. Validation checks it solved the business problem, through measures after launch. The sample plans both and explains why a form can pass every test and still fail validation.