{"id":946,"date":"2014-09-06T14:01:02","date_gmt":"2014-09-06T14:01:02","guid":{"rendered":"http:\/\/www.w3computing.com\/systemsanalysis\/?p=946"},"modified":"2017-08-22T17:23:26","modified_gmt":"2017-08-22T17:23:26","slug":"guidelines-printed-report-design","status":"publish","type":"post","link":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/","title":{"rendered":"Guidelines for Printed Report Design"},"content":{"rendered":"

Figure shown below is an output report that is intended for divisional managers of a food wholesaler that supplies a number of franchise grocery stores. We will focus on different aspects of the report as we cover the tools, conventions, and functional and stylistic design attributes of printed output reports.<\/p>\n

Report Design Conventions<\/h2>\n

Conventions to follow when designing a form include the type of data (alphabetic, special, or numeric) that will appear in each position, showing the size of the form being prepared, and showing the way to indicate a continuation of data on consecutive layout forms. Most form design software that analysts now use features standard conventions for designing forms onscreen. In addition, it features familiar drag-and-drop interfaces that allow you to select attributes such as an address block with a mouse click and then drop it on the screen where you want to position it on your form. You will be using WYSIWYG (what you see is what you get) so it makes the design of forms a very visual exercise.<\/p>\n

\"A<\/a>
A printed output report for divisional managers of a food wholesaler.<\/figcaption><\/figure>\n

Constant information is information that remains the same whenever the report is printed. The title of the report and all the column headings are written as constant information. Variable information is information that can vary each time the report is printed out. In our example, the sales figures in thousands of dollars will change; hence, they are indicated as variable information.<\/p>\n

Paper Quality, Type, and Size<\/h2>\n

Output can be printed on innumerable kinds of paper. The overriding constraint is usually cost. One example is the use of security paper for checks and check envelopes, as well as for documents that must bear official, inalterable seals or holograms, such as passports.<\/p>\n

Preprinted forms can easily convey a distinctive corporate image through the use of corporate colors, logos, and other design elements. Using innovative shapes, colors, and layouts is also a dramatic way of drawing users\u2019 attention to the report contained on the preprinted form.<\/p>\n

Design Considerations<\/h2>\n

In designing the printed report, the systems analyst works with users to incorporate both functional and stylistic or aesthetic considerations so that the report supplies the user with necessary information in a readable and pleasing format. Because function and form reinforce each other, one should not be emphasized at the expense of the other.<\/p>\n

Functional Attributes The functional attributes of a printed report include (1) the heading or title of the report, (2) the page number, (3) the date of preparation, (4) the column headings, (5) the grouping of related data items together, and (6) the use of control breaks. Each of these serves a distinctive purpose for the user.<\/p>\n

There are several stylistic or aesthetic considerations for the systems analyst to observe when designing a printed report. If printed output is unappealing and difficult to read, it will not be used effectively or may not be used at all. The upshot is uninformed decision makers and a waste of organizational resources.<\/p>\n

Printed reports should be well organized, reflecting the way that the eye sees. In this culture, that means that the report should read from top to bottom and left to right. Related data items should be grouped together. The aesthetics of Web site and Web page design are covered in an upcoming section of this chapter.<\/p>\n","protected":false},"excerpt":{"rendered":"

Figure shown below is an output report that is intended for divisional managers of a food wholesaler that supplies a number of franchise grocery stores. We will focus on different aspects of the report as we cover the tools, conventions, and functional and stylistic design attributes of printed output reports. Report Design Conventions Conventions to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[14],"tags":[],"class_list":["post-946","post","type-post","status-publish","format-standard","category-designing-effective-output","entry","has-post-thumbnail"],"yoast_head":"\nGuidelines for Printed Report Design<\/title>\n<meta name=\"description\" content=\"Conventions to follow when designing a form include the type of data (alphabetic, special, or numeric) that will appear in each position, showing the size of the\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Guidelines for Printed Report Design\" \/>\n<meta property=\"og:description\" content=\"Conventions to follow when designing a form include the type of data (alphabetic, special, or numeric) that will appear in each position, showing the size of the\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/w3computing\" \/>\n<meta property=\"article:published_time\" content=\"2014-09-06T14:01:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2017-08-22T17:23:26+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/www.w3computing.com\/systemsanalysis\/wp-content\/uploads\/2014\/09\/11.6-printed-output-report-300x169.jpg\" \/>\n<meta name=\"author\" content=\"w3computing.com\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"w3computing.com\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"TechArticle\",\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/\"},\"author\":{\"name\":\"w3computing.com\",\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/#\\\/schema\\\/person\\\/8395166dc0b94b38a3aeb88dafbd63ce\"},\"headline\":\"Guidelines for Printed Report Design\",\"datePublished\":\"2014-09-06T14:01:02+00:00\",\"dateModified\":\"2017-08-22T17:23:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/\"},\"wordCount\":563,\"image\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/wp-content\\\/uploads\\\/2014\\\/09\\\/11.6-printed-output-report-300x169.jpg\",\"articleSection\":[\"Designing Effective Output\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/\",\"url\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/\",\"name\":\"Guidelines for Printed Report Design\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/wp-content\\\/uploads\\\/2014\\\/09\\\/11.6-printed-output-report-300x169.jpg\",\"datePublished\":\"2014-09-06T14:01:02+00:00\",\"dateModified\":\"2017-08-22T17:23:26+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/#\\\/schema\\\/person\\\/8395166dc0b94b38a3aeb88dafbd63ce\"},\"description\":\"Conventions to follow when designing a form include the type of data (alphabetic, special, or numeric) that will appear in each position, showing the size of the\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/#primaryimage\",\"url\":\"http:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/wp-content\\\/uploads\\\/2014\\\/09\\\/11.6-printed-output-report-300x169.jpg\",\"contentUrl\":\"http:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/wp-content\\\/uploads\\\/2014\\\/09\\\/11.6-printed-output-report-300x169.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/guidelines-printed-report-design\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Systems Analysis\",\"item\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Designing Effective Output\",\"item\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/designing-effective-output\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Guidelines for Printed Report Design\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/#website\",\"url\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/\",\"name\":\"\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.w3computing.com\\\/systemsanalysis\\\/#\\\/schema\\\/person\\\/8395166dc0b94b38a3aeb88dafbd63ce\",\"name\":\"w3computing.com\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Guidelines for Printed Report Design","description":"Conventions to follow when designing a form include the type of data (alphabetic, special, or numeric) that will appear in each position, showing the size of the","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/","og_locale":"en_US","og_type":"article","og_title":"Guidelines for Printed Report Design","og_description":"Conventions to follow when designing a form include the type of data (alphabetic, special, or numeric) that will appear in each position, showing the size of the","og_url":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/","article_publisher":"https:\/\/www.facebook.com\/w3computing","article_published_time":"2014-09-06T14:01:02+00:00","article_modified_time":"2017-08-22T17:23:26+00:00","og_image":[{"url":"http:\/\/www.w3computing.com\/systemsanalysis\/wp-content\/uploads\/2014\/09\/11.6-printed-output-report-300x169.jpg","type":"","width":"","height":""}],"author":"w3computing.com","twitter_misc":{"Written by":"w3computing.com","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"TechArticle","@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/#article","isPartOf":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/"},"author":{"name":"w3computing.com","@id":"https:\/\/www.w3computing.com\/systemsanalysis\/#\/schema\/person\/8395166dc0b94b38a3aeb88dafbd63ce"},"headline":"Guidelines for Printed Report Design","datePublished":"2014-09-06T14:01:02+00:00","dateModified":"2017-08-22T17:23:26+00:00","mainEntityOfPage":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/"},"wordCount":563,"image":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/#primaryimage"},"thumbnailUrl":"http:\/\/www.w3computing.com\/systemsanalysis\/wp-content\/uploads\/2014\/09\/11.6-printed-output-report-300x169.jpg","articleSection":["Designing Effective Output"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/","url":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/","name":"Guidelines for Printed Report Design","isPartOf":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/#primaryimage"},"image":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/#primaryimage"},"thumbnailUrl":"http:\/\/www.w3computing.com\/systemsanalysis\/wp-content\/uploads\/2014\/09\/11.6-printed-output-report-300x169.jpg","datePublished":"2014-09-06T14:01:02+00:00","dateModified":"2017-08-22T17:23:26+00:00","author":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/#\/schema\/person\/8395166dc0b94b38a3aeb88dafbd63ce"},"description":"Conventions to follow when designing a form include the type of data (alphabetic, special, or numeric) that will appear in each position, showing the size of the","breadcrumb":{"@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/#primaryimage","url":"http:\/\/www.w3computing.com\/systemsanalysis\/wp-content\/uploads\/2014\/09\/11.6-printed-output-report-300x169.jpg","contentUrl":"http:\/\/www.w3computing.com\/systemsanalysis\/wp-content\/uploads\/2014\/09\/11.6-printed-output-report-300x169.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/www.w3computing.com\/systemsanalysis\/guidelines-printed-report-design\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Systems Analysis","item":"https:\/\/www.w3computing.com\/systemsanalysis\/"},{"@type":"ListItem","position":2,"name":"Designing Effective Output","item":"https:\/\/www.w3computing.com\/systemsanalysis\/designing-effective-output\/"},{"@type":"ListItem","position":3,"name":"Guidelines for Printed Report Design"}]},{"@type":"WebSite","@id":"https:\/\/www.w3computing.com\/systemsanalysis\/#website","url":"https:\/\/www.w3computing.com\/systemsanalysis\/","name":"","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.w3computing.com\/systemsanalysis\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.w3computing.com\/systemsanalysis\/#\/schema\/person\/8395166dc0b94b38a3aeb88dafbd63ce","name":"w3computing.com"}]}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4NNeA-fg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/posts\/946","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/comments?post=946"}],"version-history":[{"count":0,"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/posts\/946\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/media?parent=946"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/categories?post=946"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3computing.com\/systemsanalysis\/wp-json\/wp\/v2\/tags?post=946"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}