This page holds a finished NR 640B Week 7 project boundary memo: one idea sized to the term, the exclusions named, and the conditions the site would have to meet. Searches like "nr 640b week 7 assignment example", "nr640b week 7 sample" and "nr 640b week 7 example" land here.
What a finished NR 640B Week 7 project boundary memo looks like
A memo, not a proposal, and the difference shows on the page. It is one or two pages under short headings, addressed to somebody at the site rather than to the classroom, and written in the flat register people use internally. The idea appears in a single sentence early, stated as what would exist at the end and for whom. Then come the limits: what the term will not touch, which systems stay as they are, which approvals the idea would need and has not sought, and the point at which it would pass out of a student's hands and into the department's. Feasibility is argued from the site's own constraints, the build slots, the freeze periods, the people already committed elsewhere, and not from enthusiasm.
How a NR 640B Week 7 example is structured
Memos here follow the shape their readers expect. A purpose line opens, one sentence saying what the memo decides. Background follows in a short paragraph, drawn from the earlier weeks rather than restated at length, since the reader works at the site and knows it. The bounded idea comes next, written as a deliverable with a named beneficiary and a rough size. Exclusions get their own heading and their own space, each with the reason it sits outside: too long, needs an approval nobody has, belongs to a team the writer never met. Conditions follow, naming what the site would have to provide before the idea could start: an hour of an analyst's time, a test environment, a decision from one manager. A closing paragraph hands the question back to the supervising specialist and asks for one specific decision rather than general agreement.
The idea in one sentence
What would exist at the end and who would use it. The example states this early and resists expanding it anywhere later in the memo.
What sits outside
Each exclusion with the reason it is excluded: too long, needs an approval nobody has, or belongs to a team the writer never met.
Constraints that belong to the site
Build slots, freeze periods before an upgrade, and the time of people already committed elsewhere. These decide feasibility, and a memo ignoring them convinces nobody.
Conditions, not promises
The memo lists what would have to be freed up for the idea to begin and then leaves the decision with the person who can make it, rather than assuming agreement.
Addressed to a reader at the site
The register is internal and flat. A memo written to impress the classroom instead of to inform the specialist reads wrong to anybody who has worked in one.
Where marks go in NR 640B Week 7
The memo that marks worst measures the work against the writer's calendar instead of the site's. Eight weeks is not the constraint that decides anything here; a build slot, a freeze before a major upgrade, and one analyst's committed time are, and a memo that never mentions them has not asked anybody. Empty exclusion lists cost marks too, since a boundary with nothing outside it is a boundary nobody tested. Ideas that duplicate something recorded in Week 5 lose points twice, once for the duplication and once for not reading the department's own list. Then there is the memo written as persuasion, arguing value at length for a reader who only needs to know what is being asked of them.
Get a NR 640B Week 7 example written to your instructions
Attach the Week 7 instructions, the rubric rows, and two or three sentences about the idea you are circling. The example comes back as a memo you can read against your own site, free the first time and inside 24-48h, with the exclusions and conditions laid out in full.
NR 640B Week 7 questions, answered
How small does the idea have to be?
Small enough that somebody without authority could finish it in the weeks remaining, using time a person at the site has already agreed to give. A one-page comparison of two order entry screens, a draft field list, a short handout for a change already scheduled: the finished memos in this course look modest and hold up in the room.
Does NR 642 expect this same memo?
No. This one ends with a question for your supervisor, and the concluding course starts after somebody has answered it. NR 642 expects a problem you intend to finish, a person with standing who will back it, and a record of where things stand before anything changes. Work carried straight across from here usually reads as underdeveloped there.
What if my supervisor rejects the idea?
Then the memo did its job, and most sections mark it that way. A boundary tested against a real constraint and returned is evidence that the writer understood the site. The revision goes into the Week 8 paper with the reason attached, and faculty consistently prefer that to an idea nobody at the site ever looked at.