Information a recurring decision needs, set against information on hand, is what every Week 9 systems memo in DDBA 4990 measures before proposing the smallest fix. Searches like "ddba 4990 week 9 assignment example", "ddba4990 week 9 sample" and "ddba 4990 week 9 example" land here.
What a finished DDBA 4990 Week 9 systems memo looks like
A two-page memo whose core is a table of three columns. The example decision is whether a wholesale florist extends trade credit to a new restaurant account. Column one lists what that decision requires: the account's payment history elsewhere, its order volume, the florist's current exposure to slow payers, and the margin on the expected orders. Column two records what the firm actually holds today, which turns out to be the order volume and little else, kept in a spreadsheet one clerk maintains. Column three names the gap for each row. A paragraph frames the table with Galbraith's information-processing view, in which uncertainty is the difference between information a task needs and information already held. The recommendation proposes one added report and one credit check, each costed.
How a DDBA 4990 Week 9 example is structured
The decision is fixed before any technology appears, since a systems memo that opens with software has chosen a tool before knowing the job. The table then does the analytic work, and its rows are chosen by asking what a skeptical owner would need to see before approving the credit line. Galbraith supplies the definition that turns the table into an argument: each gap is a measured piece of uncertainty. Simon's bounded rationality appears in one sentence to explain why the clerk currently decides on instinct, since people choose with the information at hand and stop when an option seems good enough. System is defined early as people, procedure and records together, not software alone. The recommendation targets the largest gap first and prices each change, so the memo ends on something an owner could approve.
The decision, stated narrowly
Extend trade credit to a new restaurant account, yes or no, and at what limit. A decision this specific has a finite list of inputs, which a phrase like improving credit management would never supply.
Required, held, missing
Three columns, four rows. Payment history, order volume, current exposure and expected margin are required; only volume is held; the other three are gaps. The table is the memo's evidence, and each row can be checked.
Uncertainty as a measured gap
Galbraith's definition lets the memo treat each missing row as a quantity rather than a complaint. The florist does not lack information in general; it lacks three specific items for one recurring choice.
System means more than software
People, procedure and records are named as the system's parts in the opening paragraph. The clerk's spreadsheet counts, and so does the habit of asking a sales rep what a new account seems like.
The smallest fix, priced
A monthly aging report and a trade reference check on every new account, with the clerk's added hours estimated. The memo prices both and shows they close the two largest gaps before anything larger is considered.
Where marks go in DDBA 4990 Week 9
Graders open with the requirements column, and it weighs most, because every other column depends on it. A list naming vague needs, better data or more visibility, gives the gap column nothing to measure. Graders check that the held column describes what the firm really has, including where it lives and who maintains it. The analytic credit sits with the gaps and with Galbraith's framing, which earns marks only when each gap is stated as information missing for this decision. Simon is optional and is credited when used to explain current behavior rather than cited in passing. The recommendation is judged on proportion: proposing an enterprise system to close two gaps a report and a phone call would close suggests the decision was never the subject.
Get a DDBA 4990 Week 9 example written to your instructions
Name the recurring choice your prompt specifies, or one your own organization makes every month, and pass it on with the Week 9 prompt and rubric. The three-column table, the Galbraith framing and a priced recommendation reach you in 24 to 48 hours, and your first sample is free. Software is mentioned only if a gap actually calls for it.
DDBA 4990 Week 9 questions, answered
Does a systems memo have to recommend new software?
No, and many strong memos do not. The course treats a system as people, procedures and records together, so a new report, a changed approval step or a shared checklist can close a gap as well as a purchase can. Recommend software only when the gap requires it, and say which requirement in the table it meets.
How specific should the decision be?
Specific enough that its information needs can be listed completely. Whether to extend credit to one account is workable; how to improve financial decisions is not. A good test is whether two people could agree on what the decision's inputs are. If the list keeps growing, the decision is still too broad, and narrowing it belongs to the task itself.
Which sources suit this memo?
One or two from the decision-making literature, used to frame the analysis, and the firm's own records or the scenario for the facts. Galbraith and Simon are standard anchors in management readings. An information systems textbook can support a definition. Vendor material describing what a product can do is weak evidence and should be labeled as such if it appears.