Everyone knows that it is important to test software so that you find any bugs before it goes out to customers. The majority of organisations that develop software have people who spend at least some of the time doing testing their software. Many may also do ‘user acceptance’ testing to check that the software meets [...]
Posts Tagged ‘writing’
Why user documentation should be tested and how to do it
Posted in standards, usability, writing, tagged documentation, help, standards, testing, usability, user assistance, wg2, writing on May 31, 2012 | Leave a Comment »
Developing user documentation in an agile environment: An International Standard
Posted in standards, writing, tagged agile, documentation, standards, writing on September 23, 2011 | Leave a Comment »
UPDATE: The standard is now available: http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=43074 This week I gave a presentation with this title to the Technical Communication UK 2011 Conference. I’ve attached the slides that I used in the conference here: TCUK11_Agile, although they won’t really mean much to anyone! The majority of the presentations I’ve done in the past do rely on Power [...]
Working group 2 standards adopted by IEEE
Posted in standards, tagged documentation, sc7 wg2, standards, testing, usability, writing on January 28, 2011 | 1 Comment »
This week two of the standards produced by working group 2, software and systems documentation, have been formally adopted by the IEEE and released as IEEE standards. The two standards are 26514 (Requirements for Designers and Developers of User Documentation) and my standard 26513 (Requirements for Testers and Reviewers of User Documentation). Best to visit [...]
Press release on my standard on testing and reviewing user documentation
Posted in standards, usability, writing, tagged documentation, standards, testing, usability, writing on May 8, 2010 | Leave a Comment »
I’ve just found this press release about my published international standard: IS0 26513 Systems and software engineering – Requirements for testers and reviewers of user documentation. It’s good to see press releases about standards to help our users find standards relevant to their business. The article also mentions the other standards that we are currently developing in [...]
Why ‘find and replace’ doesn’t work for documentation
Posted in usability, work, writing, tagged usability, writing on February 7, 2008 | Leave a Comment »
I’ve been having a discussion today about a ‘behavior’ with some writers that annoys me. Situations often crop up with our documentation where a term or other phrase within the docs needs to be replaced with a different term or phrase. This usually occurs because of an update – something in the software changed name [...]
GUI elements and terminology
Posted in usability, work, writing, tagged documentation, eclipse, GUI, interfaces, terminology, tooling, usability, work, writing on February 5, 2008 | 2 Comments »
One thing I find that makes writing difficult is the confusing mass of terminology around GUI interface elements such as buttons, menus, pages, windows, tabs and so on. Many of the tools that I work with have standard elements that have standard names. For example in the Eclipse platform the main ones are workbench windows, perspectives, editors and [...]



