Eliminate the ADMINISTRATIVE HEADACHES

It's the Business Analyst job to capture the requirements for a new
software project and communicate these requirements to the IT team.
But if this is a role that you perform regularly, you'll know that
it's not as easy as it sounds.

The business requirements for large IT projects are inevitably hard
to define. Users may not be able to easily articulate their needs,
and different teams may have different perceptions of the way
processes should work. Once requirements are captured - the change
management process starts with the challenge of keeping the team
continually updated without overwhelming them with documentation.

What's more, the introduction of new business systems is often the
catalyst for business process change. But getting it right is
essential. The requirements definition not only provides the roadmap
for the software development team, but also creates a framework for
effective quality assurance and testing. If the requirements are
incomplete or ambiguous, problems will occur later in the project
that will be costly to resolve

Contour helps to alleviate these challenges. It allows business
analysts to:

- Create one central repository for all requirements, so that there
is only ever one, up-to-date version of the project specification
- Display relationships between requirements, so that any gaps in
process flows can be easily identified
- Compare different versions of requirements, side-by-side, to
clearly see and assess the differences and changes made
- Create content templates, which speed up repetitive tasks
- Assess the impact of changes to requirements, before making them
and consider `what if' scenarios
- Decompose high-level requirements into individual system features
- Collaborate more effectively with business and IT teams
- Produce reports in a range of formats including Microsoft Word,
Excel and PDF


http://www.jamasoftware.com/screens.htm