Robert Pierce
About the author:
No description available of Robert Pierce...
Publications by Robert Pierce (bibliography)
» 2008 «
Pierce, Robert (2008): Using customer input to drive change in user assistance. In: DOC08 2008. pp. 23-30. Available online
If designing and developing optimal products, services, and information requires clarity and audience awareness, then developing ways to acquire customer input is a critical piece in the best development workflow solutions [43]. Seeking direct input from customers and learning how they use a product are the most effective methods for generating ideas for enhancements and innovations to the technical content that supports a product, as well as to the product itself [21]. Taking the steps to create opportunities for customer feedback enables direct customer input and establishes the proactive best practice of demonstrating to the customer that they are a top priority in the product development focus [34]. While there may not be a fixed agenda for an optimal customer meeting, there may, in fact, be a set of topics for discussion that comprise a set of best practices for gaining customer input for the user assistance [45]. Customer input helps provide requests for change and thus aids in managing change, raising the importance of a change and requirements management system [34, 52]. A change and requirements management system is even more critical in the context of application lifecycle management and globally distributed development [27, 49, 50, 55]. Managing relationships with customers leads to a two-way path for collaboration, both for helping customers solve their problems and for a company to enhance its products and overall success [26, 28].
Copyrights may apply
Pierce, Robert, Mehlenbacher, Brad, Costa, Carlos J., Albers, Michael J. and Protopsaltis, Aristidis (2008): Panel design of communication: new steps. In: DOC08 2008. pp. 183-184. Available online
SIGDOC comes from a technical writing tradition, where literature and rhetoric play an important role. Communication is now giving a broader focus, especially as influences come from graphical design, web design, digital sound or digital multimedia. In Lisbon, we expect to discuss this focus of SIGDOC. This is an important transition that is being done, without loosing its identity. In fact, from the revision process the heterogeneity of view point was identified. This is the result of including more participants from multimedia, computer science and graphical design. For the second time, SIGDOC will take place outside the American continent. For the first time it takes places in a non-English speaking country. It is the ideal place to discuss an important issue either for the technical documentation, either for software engineering or for design of communication communities: translation, internationalization, localization, and globalization. Bologna process is transforming and making an authentic revolution in the European university panorama. This may be faced either as a threat or as an opportunity. In this context, the discussion about a curriculum in design of communication is an important step that may be undertaken by the SIGDOC. It is a step that may contribute to its affirmation either in academia or in practitioner context.
Copyrights may apply
» 2007 «
Pierce, Robert, Protopsaltis, Aristidis, Mehlenbacher, Brad and Zachry, Mark (2007): What is design of communication?. In: Proceedings of the 25th annual ACM international conference on Design of communication 2007, El Paso, Texas, USA. p. 181. Available online
What is the Design of Communication? In this panel, four SIGDOC members from different areas come together to discuss the interdisciplinary area of DOC.
Copyrights may apply
» 2005 «
Pierce, Robert (2005): Leveraging technology affinity: applying a common set of tools and practices to information development. In: ACM 23rd International Conference on Computer Documentation 2005. pp. 123-130. Available online
The six best practices of software development can be applied to the development of each component of a finished product or project. Each organization within an enterprise can design and implement a process that encompasses these best practices. And there are software development tools that enable each best practice. This paper describes the six best practices, the tools that enable them, and demonstrates how they can be applied to information development, as well as other all components of software development. This paper also provides an example that illustrates how documentation groups or organizations can benefit by following these best practices to ensure success for information development projects.
Copyrights may apply
» 2002 «
Pierce, Robert and Tilley, Scott (2002): Automatically connecting documentation to code with rose. In: ACM 20th International Conference on Computer Documentation 2002. pp. 157-163. Available online
One of the most common problems with program documentation is keeping it synchronized with the source code it purports to explain. One solution to this problem is to automate the documentation process using reverse engineering technology. Reverse engineering is an emerging branch of software engineering that focuses on recreating high-level information (such as program documentation) from low-level artifacts (such as source code). This paper describes an automated approach to maintaining the connection between documentation and code by leveraging the reverse engineering capabilities built-in to Rational Rose. The approach produces application programming interface documentation for component object model-based (COM) dynamic link libraries (DLLs), C++ source code, and Java archive files. The documentation is always accurate and up-to-date. A primary advantage of the approach is its reliance on an industry-standard tool, thereby addressing one of the main concerns with facilitating wide-spread tool adoption: commercial-level support of deployed products.
Copyrights may apply
SHOW THIS LIST ON YOUR HOMEPAGE
What do YOU think?
Give us your opinion! Do you have any comments/additions
that you would like other visitors to see?
You say:
Mar 21st, 2010
Changes to this page (author)
22 Feb 2010: Enabled abstracts to be shown on Robert Pierce's author page.07 Apr 2009: Author was edited 07 Apr 2009: Author was edited
12 May 2008: Author was edited
22 Jun 2007: Author was edited
22 Jun 2007: Author was added to the bibliography