* 1 Use Cases (Prioritised) o 1.1 Custom Stencils / Priority: HIGH o 1.2 Workflow for a CMS / Priority: HIGH o 1.3 Illustrating an article/presentation / Priority: HIGH o 1.4 Extending an Existing Flowchart / Priority: HIGH o 1.5 Sitemap of OpenUsability / Priority: MEDIUM o 1.6 Map of Related Institutions / Priority: LOW
This list of prioritised Use Cases was developed in accordance with the results from the User Survey and with the KOffice development plans.
Use Cases prioritised "High" should work in Kivio 2.0.
I want to create different flowcharts for my thesis on database migration with special stencils and icons. I partly created them in Karbon, partly they are PNGs (e.g. company/community logos).
All this requires:
* An easy way to insert images. * An easy way to insert SVG objects. * An easy way to import SVG objects and images and make them available as stencils (as I often reuse them).
I am department head in a medium-sized publishing company. The management has introduced a new aprovement process for articles in my department, and I want to visualise the workflow in a diagram. The diagram is then published in the intranet, so everybody can access it.
I'm quite experienced working with computers, but my knowledge regarding graphics application is low. I use them maybe twice a month.
My company does not provide any infrastructure for creating internal diagrams, that means I got to find my own way.
I want to define the workflows in a CMS:
* An author produces an article and sends it to a publishing company. * The editor at the publishing company assigns a reviewer to the received article. Note that he doesn't check the article; he just picks a reviewer. * The reviewer approves it for publication or declines the approval if the article contains errors. If he declines the article, it is sent back to the author for improvement. * Each of the elements in this workflow has an id, a title and a role.
Also, the application should be flexible enough to change the following aspects easily:
* There is need for a second approval by a different reviewer. The author passes his article to both reviewers. If one reviewer declines an article, it is not approved. The article is approved if both reviewers accept it. * The author want to pass the article directly to the reviewer, after it is written. Therefore the editor becomes obsolete, and the author's article is passed directly to the reviewer. * When there was a need in the second task to have a second reviewer to check the article, this is performed after the first review. If the first reviewer accepts the article, he passes it to the second reviewer. If the second reviewer accepts it, it is approved, otherwise sent back to the author.
All this requires:
* A very easy handling of arranging and rearranging connectors. o Easily create horizontal and vertical lines instead of angular, but also angular if required. o Allow to bend connectors. o Allow to remove points in a connector to make a line straight again. o Allow to remove parts of the line. o Provide adequate visual mouse pointer feedback (e.g. difference between grabbing a point and the whole line, difference between add and remove elements,...)
Writing an article about this new cool solution and to illustrate it I need a cool looking flowchart.
* Gradients * Alpha blending * Different background colors * Easy way to get matching colors * Richtext support * An easy way to align everything properly on the page. * An easy way to center them and provide good proportions (border versus distance between them).
I work in a company, and my colleague has made a flowchart for several company processes.
My task is to extend the flowchart by some more processes. Also, my colleague used the wrong stencils and I need to exchange all templates in the flowchart.
I need to
* add another path from the root which is similar to the existing ones and added as a parallell path. * it has several sub paths. * the size of the original flowchart will double or triple. * exchange the stencils.
All this will require:
* An easy way to copy existing paths and to insert them with the connectors at the proper position ("mirroring" an existing path). * Possibly add complete paths / workflows which are predefined by the company. * In the latter case, the company should be able to offer predefined workflows (templates) in Kivio's stencil sets, not only when creating a new graph. * I need to be able to exchange the stencil of a whole selection of objects. * I need to be able to undo the action of copying a complete workflows (group of objects) at once. * Again, I need to have a flexible working area regarding size and I need appropriate print mechanisms.
I want to create a sitemap of the future OpenUsability.
* Six main sections (Collaboration, Knowledgebase, OpenUsability, Help, User Panel, Search) * Each section holds several subsection, each of them possibly having more subsections. * I want to use colours to easily understand which parts are related. * I want to visualise cross-links between different parts. * I want to add comments to several parts or pages. * I want two views of the sitemap, one with comments and crosslinks, one without.
All this requires:
* A lot of space as it is a complex structure. * Easy way to extend the size of my work panel at any border, possibly an unlimited work area? * When I print, it has to scale down to DIN A 4. * When I print, it has to split the sitemap onto several DIN A 4 pages. * A title for each object (big). * Comments for an object or group of objects (small). * Different background, foreground, line colours. * An easy way to equally space objects and object groups. * Flexible and non-intrusive lines as crosslinks (transparent?) * Layers to show/hide certain parts of the sitemap. * When I print or export the sitemap, invisible layers are not shown.
For OpenUsability, I need to make a graph containing the institutions related with it (universities, other OSS Usability efforts, sponsors, ...).
* A map showing the institutions and their relations. * Links to the institutions' homepages. * To export it in a format that allows to click on links (PDF, imagemap, ..)
All this requires:
* Options to include links (web/file). * Export format that allows to click on links (PDF, imagemap,..)