The industry’s first solution for Requirements Elicitation

Blueprint Requirements Center 2009’s elicitation module was designed in partnership with dozens of business analysts throughout all industry verticals. Through this partnership, Blueprint identified the need for a new kind of software requirements solution, built for the early stages of collaboration with the line of business and IT.

Rapid requirements capture – from the start

Elicitation involves interviews, JAD sessions, brainstorming workshops, and many other interactive events. Frantically jotting down items in a notebook only to later transcribe them into a requirements tool or document is inefficient and error-prone. Blueprint Requirements Center’s new elicitation module is designed to be used right from the beginning of requirements elicitation letting you rapidly capture and categorize information so nothing is missed. In elicitation, requirements concepts are captured in an Excel-like list, with customizable fields, unique identifiers, threaded comments, and robust search and sorting. All elements in the elicitation module are managed under version control and configuration management through integration with the Blueprint Definition Server.

Inline Glossaries

Ensuring business analyst teams are leveraging a common language and vocabulary is critical when building alignment and consensus between business and IT. When we’re dealing with requirements capture and elicitation, language mistakes can turn out to be very expensive when they’re discovered after something’s been built. Blueprint Requirements Center allows you to create multiple glossaries of terms that exist alongside the requirements being captured. You can have a company-wide glossary of terms, one for the department, and another for terms used on a specific project. This ensures all are speaking the same language, and removes many costly errors.

Capture all relevant information – regardless of the source

Blueprint understands that the early stage of requirements elicitation requires the use and re-use of existing documentation in multiple formats. (ie: These formats include emails, pdf documents, other applications, spreadsheets, and a multitude of other media.) Blueprint Requirements Center provides several means to capture and represent this disparate information. This can be project charter or vision documents, standards and guidelines that you need to adhere to, or screenshots of existing applications, etc. Blueprint Requirements Center lets you bring these references materials into a Requirements Project and lets you view & analyze them in their native applications embedded within Blueprint Requirements Center (example: MS Word, MS Excel, pdf, html, GIF, JPG, TIFF etc.). From that point forward whether you’re simulating requirements, viewing auto-generated tests, or generating documents automatically, these references are propagated and made available to users.

Proceed to the Elaboration phase of the requirements definition lifecycle.

Modules for the Requirements Definition Lifecycle

(Explore by selecting one of the above.)

© 2008 Blueprint Software Systems Inc. All rights reserved.  |  Sitemap  |  Privacy Policy  |  RSS Feed