Documents are still the tool of choice for Requirements Engineers and Business Analysts who define requirements. But even ardent adherents admit they leave much to be desired when it comes to handling them in the development envronment. But they're just so darned easy and convenient to use!
Polarion Documents, coming in Polarion 2011, deliver an exciting new approach that keeps document-oriented people working the way they work best, while streamlining collaboration, and seamlessly merging document-based artifacts into your overall development processes and best practices. And oh yes... they're darned easy and convenient to use!
Polarion 2011 GAIN
Documents are drafted on someone's desktop, sent by email, edited/commented on various people's desktops, sent back, comments & changes are integrated into "main" document on someone's desktop.
Emailed documents can't be compared to and edited/commented against the latest working version - people often don't know if they even have the latest version.
Cumbersome process repeats as many times as it takes to get consensus.
People can collaborate on the latest-greatest version of a document in a familiar-feeling, word processor-like editor, on the web, in real time, in less time.
The latest version of every Document is online and accessible to stakeholders located anywhere, any time.
Requirements in a document are segregated from everything: related requirements in other documents, test cases, source code revisions.
Requirements have to be duplicated for use by other teams executing different stages of process - time consuming and error-prone.
Nobody knows where the requirements are in the process right now.
Artifacts like Requirements exist as simple sections, paragraphs, even bullet points in easy to use, easy to share online Documents... but not in isolation. Document content becomes linkable, traceable, and manageable across team functions and throughout the entire lifecycle.
Easily view the priority, owner, current status, planned time point or any system-maintained data about the requirement artifacts defined in your documents.
Integrate artifacts with any process (no lock-in to a particular process), and automate process steps with customizable workflows so nothing every gets missed and everyone knows where things stand.
Structure is easy to show in office documents, but it's confined to the document.
Hierarchy of artifacts is unavailable to tools used to manage process.
Document structure is shown naturally as headings, indents, bullets, etc.
Structure is transparently translated into data - no tools involved.
Structure data is automatically updated as documents are modified.