• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Pneuma Solutions

Accessible Cloud Technologies

  • EnglishEnglish
    • DeutschDeutsch
    • EspañolEspañol
    • FrançaisFrançais
    • ItalianoItaliano
    • PortuguêsPortuguês
    • SvenskaSvenska
  • Home
  • Login to Pneuma Solutions Services
    • Remote Incident Manager
    • Scribe for Documents
    • Scribe for Meetings
    • Sero
  • About
  • Products
    • All Products
    • Remote Incident Manager (RIM)
    • Scribe
    • Scribe For Meetings
    • Scribe for Meetings Self-Advocacy Kit
    • Scribe California Services
    • DocuScan Plus
    • Sero
  • FAQs
    • FAQ – Remote Incident Manager (RIM)
    • FAQ – Scribe
    • FAQ – Scribe For Meetings
    • FAQ – DocuScan Plus
    • FAQ – Sign-Up and Account Information
    • FAQ – Sales and Support
    • FAQ – System Access
    • FAQ – Sero
  • Jobs
  • Blog
  • Contact
    • Contact Form
    • Subscribe to Our Email List
    • Terms of Use Agreement
    • Privacy Policy
Home > Pneuma Solutions Blog > Crowdsourcing as a software development tool

Crowdsourcing as a software development tool

Pneuma Solutions Team • December 7, 2010

With the recent release of DocuScan Plus, the product development team would like to share with the community what we believe to be a new and exciting method of developing assistive technology. We feel that this tool is especially useful when developing assistive technology because of the unique challenges involved with creating this type of software. Assistive technology, unlike some other types of software, must be simultaneously easy enough for brand new computer user’s to use, yet powerful enough to satisfy the needs of those with long term experience as well. In addition, developing a product that is so essential to so many people means that great care must be taken in every step of the design process.

How software is traditionally developed

The traditional method of software development is for a design team to generate specifications for a software product. After mapping as much of the product out as possible, including features, UI (which stands for user interface and defines how a user interacts with the software,) the overall capabilities of the software, pipe dreams, Et cetera, the design team hands these requirements off to the programmers. From this point forward, the programmers write the code using these specifications to construct the product. Once the programmers have completed their initial work, the product enters the “Alpha test phase“, during which the product design team tests the software. If needed, they ask the programmers to make changes. Once Alpha testing is complete, potential end users are invited to play with the product. This phase is most commonly refered to as a beta test. Yet, at this stage, the feature set, software capabilities, user interface, Et cetera, is mostly frozen and very few, if any changes to these areas are made. Most of the time beta testing is used to eliminate bugs only.

The Serotek difference

All of us on the DocuScan Plus development team were very excited about this product. However, we knew that we were only a small segment of the population who would ultimately be using the product. We were determined to make the product as good as it could possibly be, not only for ourselves, but for the audience we wanted to serve. While we all had ideas on what we wanted the product to be, we decided that there was no better way to find out what the ideal document scanning solution should be like than to enlist the help of the people who would use the product the most. To do this, we knew we needed to go beyond the traditional model of software development. So, instead of bringing the users in on the traditional beta testing phase, we brought them in closer to the Alpha testing level.

The community difference

Unlike traditional beta testing, we decided that we would invite current owners of Document Scan to preview the new product. In exchange for their help with the development process, they were offered an introductory upgrade price. Over 20% of existing owners of Document Scan chose to participate in the preview. The interaction we had with this group was nothing short of amazing. We created a discussion forum in which preview users were asked to leave any feedback, ask questions, make suggestions, and report problems. As the development and testing phase moved forward, many of these suggestions were incorporated into the final product. In addition to the forum, weekly voice chats were held in order to allow more direct interaction within our community. Members of the Serotek staff including the lead programmer were present at these chats and in much the same fassion as the forum, these weekly discussions produced outstanding feedback and promoted great interaction both among the preview user’s themselves and with the development team directly.

We have no doubt That DocuScan Plus is a far superior product because of the community involvement in the creation of the program. Many of the suggestions and ideas that were refined over the preview period greatly enhanced the usability, feature set, and quality of the end product. The DocuScan Plus team would like to take this opportunity to thank all of the preview users for their outstanding feedback and help making DocuScan Plus what it is today. It is truly remarkable to be part of such an awesome community. It is our hope that this type of software development, with an emphasis on community involvement, will serve as a blueprint to follow for future assistive technology products.

Share this:

Filed Under: Serotek News
Tagged With: Accessibility, Accessible Digital Lifestyle, community, disruptive technology, DocuScan Plus, social networking

Primary Sidebar

Follow Us

  • Mastodon
  • Linked In

Recent blog articles

December Gift of Accessibility: Scribe for Meetings Free for All!

New Weekend Support Package for Remote Incident Manager. Available for $50 this weekend only!

Pneuma Solutions Is Going Global!

Bridging the Gap in AI: A Call for Inclusive Innovation

My Love Affair with Sous Vide Cooking: A Blind Cook’s Perspective

A Universal Remote for All Your Tech Needs: A User Perspective on Remote Incident Manager

Happy RIMiversary!

When The Silver Screen Meets Real Life: My Unforgettable Encounter with Tom Sullivan

The Country of the Blind: A Blind Man’s Praise

BlindShell Classic 2 Integrates Sero: A Leap Forward in Assistive Technology

Summer Shows for Us = Summer Savings for Everyone! 25% Off with Code show2023

Inclusive Design over Incidental Accessibility: Why Your Existing Remote Desktop Solution May Not Be Serving You as Well as You Think

Sero for Android Gets a Face Lift!

RIM It to Win It!

Inclusion and Resilience: A Glimpse into Cuba’s Programs for the Blind

Remote Incident Manager for macOS Officially Released!

Celebrating Global Accessibility Awareness Day: Affordable, Cross-Platform Remote Assistance for Everyone

Talking Pellet Grill Accessibility, as Heard on the Blind Grilling Experience Podcast

A Mammoth Milestone: 100 Mastodon Followers!

Raising Children with One Blind and One Sighted Parent

Pneuma Solutions Officially Joins the Fediverse!

Raising a Blind Child with Purpose

Fun with ChatGPT: Writing a story about aliens helping the blind community

New Ways to Pay as You Go with Remote Incident Manager

Remote Incident Manager Coming to the Mac Platform!

Finally! Holding Businesses Accountable

Remote Incident Manager vs the Other Players – Part 2: RIM vs. TeamViewer

Remote Incident Manager vs the Other Players – Part 1: RIM vs. JAWS Tandem and NVDA Remote

Guest Review of Remote Incident Manager (RIM) Version 3.0

Remote Incident Manager (RIM)

The Future of System Access

The End of an Era

Pneuma Solutions seeks experienced front-end web developer

Accessible Information vs the PDF: Are you breaking the law?

Scribe Enterprise: The Undisputed Best in Augmented Document Remediation

Copyright © Pneuma Solutions, LLC  •  Privacy Policy • Terms of Use • Follow us at LinkedIn