Common scenarios in the useful application of ODF-supporting software
- This level of scenario is about operations and progressions that users engage in to accomplish their work. There may be types of documents and families of documents that apply, or the scenario may be more general than that. They can also be thought of as patterns that arise in a variety of uses of office-document software as part of working with electronic office documents.
Catalog of Application Scenarios based on Particular Patterns
- how to use and contribute to these scenarios
- on how this material is constructed and maintained
Real-World Document Cases
[tbd: Explanation of what these are and how they are tied to downloads in the OIC SVN Structure -- orcmid 2009-02-17 21:34:06
- This subpage will be a better place for the list of different archetypical presentation categories
The list below can move there and this can be a summary about it, perhaps. -- orcmid 2009-02-17 21:34:06
- Presentations that are highly customized, well polished and represent something larger than the particular individual.
- Presentations that are either oriented around informal meetings such as internal team meetings ( e.g., a simple agenda slide to team status ).
Presentations that are created on the fly and used to capture meeting minutes or brainstorming results.
Presentations that are photo-heavy and provide simple slide shows with photos as the primary content.
Presentations that are very information dense and often used in the financial services sector.
Presentations that are designed to be given to a potential customer with the goal of distinguishing the presenter/presenter’s organization from the competition.
Presentations that are generally used as kiosks ( both interactive and not ) as well as self-paced training and education.
Single-slide presentations generally used for creating certificates, posters and signs.
Spreadsheets that contain code which provides custom functions, macros (to automate tasks), or UI to make the user more efficient when working with the spreadsheet.
Spreadsheets that are information dense, usually rolling up a company’s financial situation through many formulas and relationships.
Spreadsheets that contain copious amounts of information (often from another application, external data sources, or copy/paste) and are then used to summarize the information, turning it into data.
Spreadsheets that are used to convey information from one application to another - usually in the form of CSV/TSV.
Spreadsheets that consolidate information from various data sources (or manual entry) and then clean the data through a series of macros or user interaction in order to make it more reliable for consumption by other LOB applications
Financial Statements / Balance Sheets
Spreadsheets that contain an income statement, balance sheet, and cash flow statement. Relatively simple in that they contain Text, numbers, formatting, and a few formulas.
Forms and Calculators
Spreadsheets that are used to input data that is later used for other LOB systems or for a calculator in the same workbook. These spreadsheets often have very locked down sheets, where the user can only select certain options or enter data in certain cells.
Spreadsheets that are used as a 2 dimensional layout surface (for the structure of the grid) in order to build a well laid out document.
Spreadsheets that are used like a Presentation, generally with one "slide" per sheet.
Spreadsheets that are used to track resources and work items for a project, often including a Gantt chart of the project timeline using a grid.
Stochastic Modeling / Simulation
Spreadsheets that are used to perform iterative analysis of/prediction of an event taking place in order predict the outcome of said event. These spreadsheets that contain information that models a real-life system (oil production, factory floor, financial vehicles, etc.) to which inputs can be inserted and the results analyzed in order to find efficiencies.
Spreadsheets consisting of a list (or lists) of data, usually manually entered into the spreadsheet.
Documents that contain carefully formatted content intended for publication in a magazine/journal.
Documents that are used to compile the manuscript of a book in a format ready for publication.
Documents containing several pages of basic, unformatted text, without specific formatting requirements.
Documents used as marketing materials – single page, designed for 6+ foot readability.
Documents that contain a page of label templates, which are merged with addresses and printed.
Documents used in legal proceedings – must conform to a specific layout/form, and are typically built over many revisions by many authors.
Documents containing plain, unformatted text, intended for personal communication.
Documents used to capture the results of a meeting– often informal, created ad-hoc during the meeting itself.
Documents used to formally present a small amount of information (e.g. an initiative or concept).
Documents containing multiple streams of specially laid out content (typically a fixed layout making use of 2D aspects of the page).
Notes / Lists
Documents that are created on demand to store informal information (e.g. brainstorming data).
Documents that contain an outline of a larger document, but little/none of the actual contents.
Documents containing a customer proposal, compiled from several authors and many sources (spreadsheets, presentations, etc.).
Research Papers / Reports
Documents that are highly technical and conform to a specific layout – common usage of academic features like equations/bibliography.
Short, highly structured documents intended to convey information in a single page. Formatting is used to customize the structured base.
Structured Documents / Forms
Documents that contain structured content intended to be populated from data sources (e.g. a database) or form input from the user.
I have manually corrected this page to not use obsolete wikiLink forms that were broken by the Wiki 1.6 upgrader. This has me think that the use of off-line page editing and backup on SVN is a good idea for expansion of this structure too, so long as it is housed on these OASIS fixtures. -- orcmid 2009-12-21 05:31:14
- I am using the Specification Analysis structure as a model in finding a way to house these patterns and scenarios.
- I think of these as higher-level and rather diagrammatic, in contrast to specific atomic tests.
- The nomenclature is not stable. I don't want to confuse these scenarios with testing scenarios, even if there is some similarity.
- There might be a connection to particular exercises and explorations of different products. The scenario is about typical patterns of use less than in how a particular product is directed to support the scenario.
I think of this as rather experimental for now. The organization might not work, and the level of abstraction might not work either. -- orcmid 2009-01-22 05:56:26
Indeed, the scenario should be high level ("create a box with solid black border" instead of "push F7 and click Coal on tab 'borderthemes'") -- bart.hanssens 2009-01-22 16:06:11
I was thinking even higher-level than that, although we certainly can't get lower than "create a box with solid black border" because we have nothing to say about GUI familiarity and conventions. That is going to be an interesting challenge. This is going to be fun to explore. -- orcmid 2009-02-19 04:45:58