Introduction To Information Modeling With DITA
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Introduction To Information Modeling With DITA

on

  • 6,046 views

Presented at DocTrain East 2007 Conference by Alan Houser, Group Wellesley -- Through effective task analysis and information modeling, organizations can maximize the usability of their technical ...

Presented at DocTrain East 2007 Conference by Alan Houser, Group Wellesley -- Through effective task analysis and information modeling, organizations can maximize the usability of their technical documentation while minimizing the required development and maintenance effort. During this interactive workshop, students will learn the principles of minimalist documentation, how to perform an effective task and topic analysis, approaches to migrating legacy documentation to DITA or other information models, and methods for mapping content to pre-defined information types. We will also use software tools to assist in performing topic analysis. While this workshop will use DITA information models as examples, the workshop will provide value for anybody who needs to move to a structured authoring environment and improve the usability and maintainability of their technical documentation.

In many organizations, writers are judged by the volume of content that they produce. The larger the manual or help system, the more effective the writer. A fatter manual is considered to be a better manual.

From the users perspective, however, fatter does not mean better. There is no positive correlation between page or topic count and usability. Large documentation sets may be intimidating and are likely to present usability issues. Furthermore, higher page or topic counts mean higher maintenance, translation, and production costs.

The minimalist documentation strategy provides a way to design and deliver highly usable documentation while minimizing the amount of content that must be developed, maintained, and produced to support a product or service. The increasingly-popular DITA information architecture is based on the concepts of minimalist documentation.

During this workshop, we will learn the principles of minimalist documentation, and how minimalist documentation strategies meet both user needs and business needs. We will learn how to design minimalist documentation using the DITA information architecture. We will interactively experience the important prerequisite of task and topic analysis for creating well-designed, highly usable minimalist documentation sets.

We will also demonstrate the use of software tools to support topic analysis. In an interactive session, we will use the IBM Task Modeler to develop a task analysis for a product or service. The instructor will demonstrate how to use the IBM Task Modeler to automatically generate DITA map files and prototype DITA-based output.

Statistics

Views

Total Views
6,046
Views on SlideShare
6,006
Embed Views
40

Actions

Likes
3
Downloads
213
Comments
0

3 Embeds 40

http://www.doctrain.com 22
http://www.slideshare.net 16
file:// 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Introduction To Information Modeling With DITA Presentation Transcript

  • 1.
    • Introduction to information modeling with DITA
    Alan Houser Principal Consultant and Trainer Tel: 412.363.3481 [email_address] www.groupwellesley.com Group Wellesley, Inc.
  • 2. What you will learn
    • Overview of DITA architecture
    • Overview and structure of DITA information types
    • Purpose and structure DITA map files
    • Information modeling from a DITA perspective
    • Techniques for rapid prototyping DITA deliverables
  • 3. What’s different about technical publishing today?
    • Time-to-market pressures
    • Increasing activity in international markets
    • Increasing needs/opportunities for information reuse
    • Multiple products, multiple audiences, multiple deliverables
    • Increasing needs/opportunities for content management
  • 4. What’s different for our documentation departments?
    • Judging documentation departments and technical communicators:
    • Old way: Volume of output
    • Word count, page count, topic count
    • "A fat manual is a good manual."
    • Encourage writers to document "everything."
  • 5. But...
    • Content must be:
    • Created
    • Updated
    • Managed
    • Localized
    • Published
    • This translates to $$$ that can be saved.
  • 6. A different approach
    • Provide task-oriented documentation.
    • Provide navigation and accessibility mechanisms.
    • Minimize amount of content provided to support your product or service.
    • Maximize usability.
  • 7. Overview of DITA design
    • Roots of DITA: minimalist approach
  • 8. How to get there
    • Document tasks that users must accomplish.
    • Document concepts that provide background for accomplishing tasks.
    • Provide reference information that users need to accomplish tasks.
    • Provide navigation and structure to support users in finding information.
  • 9. DITA in Context
    • Developed by IBM corporation as a successor/replacement for IBMIDDoc (a "book-centric" information model).
    • Donated by IBM to OASIS (Organization for the Advancement of Structured Information Standards).
    • DITA 1.0 finalized by DITA Technical Committee February 2005, formally approved by OASIS June 2005.
    • DITA 1.1 formally approved 1 August 2007.
  • 10. What is DITA?
    • Darwin Information Typing Architecture
    • An architecture that supports authoring, managing, and publishing topic-oriented content.
    • Why DITA?
    • Companies are looking for publishing solutions that facilitate information re-use, reduce time-to-market, improve management and maintainability, and provide the capability to deliver highly usable technical content.
  • 11. DITA architecture
    • Topics – typed, reusable units of information
    • Specialization mechanism to create new topic types
    • Maps define topic collections
    • Content reuse at topic and fragment level
    • Metadata-based content filtering
  • 12.
    • Basic DITA information unit
    • Should be stand-alone, usable out of context
    • No formal restriction on topic length
    • Generic "topic" type
    • Specialized topic types: task, concept, reference
    DITA Topic
  • 13. Structure of a DITA Topic <topic> <title/> <titlealts/> <shortdesc/> <prolog/> <body/> <related-links/> </topic>
  • 14. Structure of a DITA Concept Type <concept> <title/> <titlealts/> <shortdesc/> <prolog/> <conbody/> <related-links/> </concept>
  • 15. Structure of a DITA Reference Type <reference> <title/> <titlealts/> <shortdesc/> <prolog/> <refbody/> <related-links/> </reference>
  • 16. Structure of a DITA Task <task> <title/> <titlealts/> <shortdesc/> <prolog/> <taskbody/> <related-links/> </task>
  • 17. Structure of a DITA Task (continued) <taskbody> <prereq/> <context/> <steps> <step><cmd> </cmd></step> <step><cmd> </cmd></step> … </steps> <result/> <example/> <postreq/> </taskbody>
  • 18.
    • Generate set of tasks
    Workshop Exercise
  • 19.
    • Define topic sequences, hierarchies, groups
    • Define topic sets and structure for publishing
    • Define topic sets for project management and authoring responsibility
    • Define navigation structures
    • Augment and override topic-level metadata
    DITA Maps
  • 20.
    • <map title = &quot;Using your Acme Cell Phone&quot;>
    • <topicref href=&quot;answer_call.xml&quot;/>
    • <topicref href=&quot;attach_battery.xml&quot;/>
    • <topicref href=&quot;change_case.xml&quot;/>
    • <topicref href=&quot;charge_battery.xml&quot;/>
    • </map>
    A basic DITA map file
  • 21. Expressing topic hierarchies
    • <topicref> elements can be nested to express topic hierarchies in navigation and output:
    • <topicref href = &quot;maintaining_battery&quot;>
    • <topicref href = &quot;charge_battery.xml&quot;/>
    • <topicref href = &quot;attach_battery.xml&quot;/>
    • <topicref href = &quot;detach_battery.xml&quot;/>
    • <topicref href = &quot;replace_battery.xml&quot;/>
    • </topicref>
  • 22. Expressing headings within a map
    • Use <topichead> to provide title for a group of <topicref> elements. Title is rendered in output.
    • <topichead navtitle=&quot;Maintaining your battery&quot;>
    • <topicref href=&quot;attach_battery.xml&quot;/>
    • <topicref href=&quot;charge_battery.xml&quot;/>
    • <topicref href=&quot;detach_battery.xml&quot;/>
    • <topicref href=&quot;replace_battery.xml&quot;/>
    • </topichead>
  • 23. Overriding topic headings within a map
    • Use navtitle attribute to override topic titles for navigation. Must also set locktitle attribute to &quot;yes&quot;.
    • <topichead navtitle=&quot;Battery&quot;>
    • <topicref href=&quot;charge_battery.xml&quot; navtitle=&quot;Charge&quot; locktitle=&quot;yes&quot;/>
    • <topicref href=&quot;attach_battery.xml&quot; navtitle=&quot;Attach&quot; locktitle=&quot;yes&quot;/>
    • <topicref href=&quot;detach_battery.xml&quot; navtitle=&quot;Detach&quot; locktitle=&quot;yes&quot;/>
    • </topichead>
  • 24. Overriding topic-level metadata
    • DITA 1.0 provides 4 attributes to support topic filtering: audience , platform , product , otherprops . These are typically set in the topic file, but can be set or overridden in the map file.
    • <topic audience=&quot;administrator&quot;> … </topic>
    • <topicref href=&quot;troubleshooting.xml&quot; audience=&quot;user&quot; />
    • DITA 1.1 allows you to specialize the props attribute to provide your own attribute &quot;labels&quot;.
  • 25. Expressing related topics
    • Use <reltable> element to express and maintain related topics outside the topic bodies.
    • Expresses table structure through <relrow> and <relcell> elements.
    • Typically a two or three-column table (can be single column).
    • By default, topics in separate cells in row are expressed as related links. Topics within a cell are not unless explicitly labelled.
  • 26. Expressing related topics <reltable> <relrow> <relcell collection-type = &quot;family&quot;> <topicref href = &quot;charge_battery.xml&quot;/> <topicref href = &quot;attach_battery.xml&quot;/> <topicref href = &quot;detach_battery.xml&quot;/> <topicref href = &quot;replace_battery.xml&quot;/> </relcell> </relrow> </reltable>
  • 27. Controlling content for print/PDF output
    • Include or exclude topics from print or PDF output using &quot;print&quot; attribute.
    • <topicref href=&quot;preface.xml&quot; print=&quot;printonly&quot; />
    • <topicref href=&quot;using_help.xml&quot; print=&quot;no&quot; />
    • Exclude topics from toc using &quot;toc&quot; attribute.
    • <topicref href=&quot;copyright.xml&quot; toc=&quot;no&quot; />
  • 28. Sounds like a good idea. Let’s go!
    • Conventional approach to DITA migration
    • Analyze legacy documents
    • &quot;Chunk&quot; legacy content
    • Assign topic types
    • Rewrite content as necessary
    • Convert content to markup
    • Organize using DITA map files
  • 29. A better approach
    • Task-based approach
    • Perform task analysis
    • Determine supporting concept and reference topics
    • Create organizing structure: sequences, hierarchies, groups
    • Pull topics from legacy documentation as needed
    • Write to fill the holes
    • Throw the rest (of your legacy content) away
  • 30. Task analysis methodologies
    • GOMS (Goals, Operators, Methods, Selection) and similar methodologies (Card, Moran, Newell)
    • Card sorting
    • Post-it notes
    • Mind-mapping applications
  • 31. IBM Task Modeler
    • A GUI-based tool for performing task analysis and generating DITA maps.
  • 32. Workshop Exercise
    • Using the IBM Task Modeler with DITA
    • Task analysis – record with IBM Task Modeler
    • Create DITA map and stub files
    • Run through DITA Open Toolkit
    • Generate rapid-prototype help system!
  • 33. Resources
    • DITA Architecture Specification and Language Reference
    • http://www.oasis-open.org/committees/ tc_home.php?wg_abbrev=dita
    • DITA Open Toolkit
    • http://sourceforge.net/projects/dita-ot/
    • IBM Task Modeler
    • http://www.alphaworks.ibm.com/tech/taskmodeler
  • 34. Resources (continued)
    • OASIS DITA Web resources http://dita.xml.org
    • Minimalism Beyond the Nurnberg Funnel , edited by John Carroll, MIT Press, 1998
  • 35. Contact Us!
    • We hope you enjoyed this workshop. Please feel free to contact us:
    • Alan Houser [email_address] Group Wellesley, Inc. 933 Wellesley Road Pittsburgh, PA 15206 USA 412-363-3481 www.groupwellesley.com