Log in

No account? Create an account


...Why do I want to burst into a chorus of "Weasley is our King"?

« previous entry |
Sep. 14th, 2006 | 12:00 pm
location: NBCC SJ
mood: headache-y
music: On the Verge
posted by: null_variable in cptnotes

Notes à la K80

Outputs (again, chapters 13 & 14 in the brown book, chapters 11 & 12 in the red book)

- Serve the intended purpose
- Provide information for those who need it
- Fit the user recipient
- Deliver the proper quantity of information
- Use appropriate media
- Provide timely information

(As drawn from board)
(That’s to say, the customer is the king/#1/shit)


These systems outputs generally take paper form (but not necessarily).

Paper is the default media, but you should not ignore some of the alternatives.

Purpose of outputs
-deliver information
-get action
-store information

Generally speaking, outputs fall into three sorts of categories.

Let’s assume that our systems outputs are on the screen. Generally you have a header, a system title, possibly the name of who it’s going to, any qualifiers (ie range of data), date and time...

The most frequent type of systems output on paper or otherwise is a detailed report. If you consider the data from which the reports are derived, chances are you’ll have a data file with any number of entries. Typically, on a detailed output, you get one detail line for every entry in the data file. Chances are, the data file will be indexed by physical location. So it’s a one-to-one relationship from the data file to the detailed report.

You can introduce qualifiers detailed reports so there are exceptions ... for example, flagging obsolete information, etc.

Summaries / totals
- Totals of different sub-categories, etc


There’s a traditional illustration of these in the brown text book on page 559 (where it’s at the very rough design stage).

Detailed outputs are generally multi-page/-screen, so be sure to take that into account.

Brown text, page 554-555, also has examples of detailed reports.

Reports going to clients are generally referred to as presentation quality. The ones designed for inside of the organization can be draft quality.

Page 557 (damned brown book) contains charts, which are a viable, often times feasible, form that a systems output can take, in place of or in addition to the traditional systems output text/numbers.

For our purposes, charts really get cut down to three different categories:

(1) Line Charts -> good for representing singular or compound trends. TIME is normally on the X axis.

(2) Bar Charts -> can be vertical, horizontal, singular, compound...they show relationships.

(3) Pie Charts -> useful for showing a composition or categories of something of the whole – a breakdown.


Comments {4}


From: gwenlister
Date: Sep. 14th, 2006 03:43 pm (UTC)


Nice pictures, Katy. Miss me yet? LOL

Reply | Thread

Kaytlyn Elizabeth Anne

From: null_variable
Date: Sep. 14th, 2006 04:03 pm (UTC)

Thankee :) The first one is almost EXACTLY what Patstone had on the board, lol.

The only part I really miss you is when Peter does a bunch of diagrams and then talks really fast on purpose to vex me.

Reply | Parent | Thread


From: gwenlister
Date: Sep. 14th, 2006 04:10 pm (UTC)

Oh, thats it eh? Just the diagrams? Jerk. I should get someone to write "is a loser" beside your name somewhere.... ;)

Reply | Parent | Thread

Kaytlyn Elizabeth Anne

From: null_variable
Date: Sep. 14th, 2006 04:17 pm (UTC)

Oh, and, umm...the insults.

"Chris, Lesley's copying my work!"
"Chris, Kaytlyn's being a whore!"
[crickets chirp]

You should see - we lined the toy soldiers up along the window facing the firsties *smirks*

Reply | Parent | Thread