This page holds a finished NR 643 Week 2 implementation report, setting what was specified against what the system actually does now, difference by difference, each with its reason. Searches like "nr 643 week 2 assignment example", "nr643 week 2 sample" and "nr 643 week 2 example" land here.
What a finished NR 643 Week 2 implementation report looks like
The report is a table of differences with short prose around it. Each row carries the item as specified, what exists in the live system today, the reason the two are not the same, and what the difference does to the criterion the project agreed to be judged on. Differences fall into two kinds and the report keeps them apart: things the system would not do, and things change control would not approve inside the term. The build is identified by version, environment and location, because a configuration sitting in a sandbox is not delivered. Screenshots show the live configuration rather than describing it, cropped so no real record appears. Anything a person now does by hand outside the system gets its own row, since that step leaves no trace and will be the first thing to lapse.
How a NR 643 Week 2 example is structured
The specification comes first, carried over in the wording it was approved in, since a list of differences needs something fixed to be different from. Environment and version follow, naming what is live, what is still in a build environment, and the date the two were last the same. The table occupies the middle and runs in the order the specification was written rather than in the order the work happened. Reasons are then grouped by kind, which shows at once how much of the shortfall was technical and how much was governance. Acceptance testing takes its own block: who tried the thing besides the person who built it, against which cases, and what failed on the first attempt. The workaround register follows. Outstanding items close the report, each with a change request number and the date it was raised.
Specified against existing
Each row sets one planned item beside what the live system does today, with the reason they differ and what that costs the figure the project promised.
Two kinds of difference
What the system would not do and what change control would not approve inside the term are kept in separate groups, because they carry different lessons.
Version, environment, location
The build is identified precisely enough for somebody else to open it, and anything still sitting in a sandbox is reported as unbuilt.
Tested by somebody else
A person other than the builder works through the cases, since the builder cannot see the assumptions they configured in and their own tests all pass.
The workaround register
Every step now performed by hand outside the system has a row of its own, because those leave no record and lapse first.
Where marks go in NR 643 Week 2
The heaviest loss is a report written entirely in prose, where a reader cannot separate what was configured from what was merely discussed in a meeting. Second is a difference recorded with no reason beside it, which reads as drift rather than as a decision. Third is a build tested only by the person who built it, since that person cannot see the assumptions they put in and every test they run passes. Then work still sitting in a build environment reported as delivered, which the next reader discovers and holds against the rest. Lower down: no version or date on the configuration, a screenshot carrying a real name or record number, workarounds left out, change requests mentioned without their numbers, an employer named, and future tense mixed into an account of what already exists.
Get a NR 643 Week 2 example written to your instructions
Send the Week 2 instructions from your classroom, the rubric, any reporting template, and a short description of what you built and in which system. A custom example report is written to that and returned inside 24-48h, free the first time. We do not touch practicum paperwork: hours, the log behind them and any countersignature are your own attestation of presence.
NR 643 Week 2 questions, answered
What if almost nothing was built?
Then the report is about why, and it can still score well. A term spent waiting behind a change control queue or on a vendor decision is a real account of informatics work, provided the delays are dated, attributed to a stage rather than to a mood, and the report says exactly what state the build is in and what would move it.
Does the report need screenshots?
Most sections expect some evidence that the thing exists rather than a description of it, and a cropped image of the live configuration is the cheapest form of that. Crop tightly, use a test record, and check no name, number or account is visible in a header or a side panel. Where images are not allowed, an exported configuration listing does the same job.
Should the original specification be rewritten to match what was built?
No, and doing it removes the only thing the week is marked on. The point of the report is the distance between the two documents and what caused it. A specification quietly edited afterwards produces a report with nothing to say, and the edit is usually visible anyway because the file carries its own revision history.