Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Requirements  Tools for documentation and requirements management
Previous Previous
Next Next
New Post 4/12/2012 3:12 AM
User is offline Jose
3 posts
No Ranking

Tools for documentation and requirements management 


I am part of a Tools User Group that is evaluating a standard RE tool for implementation across our UK business. We currently have Doors 8.1 however it's out of date and only used by the half of the team that create declarative requirements. The other half of the team produce User Stories and manage their requirements in word. We are undertaking a large programme and the current solutions do not meet the requirements management job given the complexity of the work we are undertaking. We need a tool that we can use to document requirements and use for sign-off, and manage requirements right through the project process through test, compliance and traceability. Does anyone have any insights based on what they use?

Thanks Jo

New Post 4/12/2012 2:04 PM
User is offline Kimbo
456 posts
5th Level Poster

Re: Tools for documentation and requirements management 
Hi Jo, I use Enterprise Architect from Sparx Systems. It will do what you want. Others will have their favourites. Kimbo
New Post 4/13/2012 6:45 AM
User is offline Tony Markos
493 posts
5th Level Poster

Re: Tools for documentation and requirements management 


Don't first look at tools.  I repeat, do not first look at tools.  First, think Agile.  And remember, that Agile is not just about minimual documentation, it is just as much about quality documentation.  In other words think about requirements documentation that captures the essentials and only the essentials.  

Additionally, Agile says forget about long winded text based requirements.  Instead focus on requirements at higher level of abstraction, and then let the developers hash out the details.   Think modeling.

 The real need - especially in complex projects - is not so much about capturing the indivdual behaviroal requirements, but the essential interrelationships between higher level requirements. This puts the stongest empahsis on graphical requirements gathering techniques that capture these essential interrelationships.  User Stories fail here.

Also, to handle complexity, the BA needs to be guided in accopmplishing a logical, natural decomposition.  The typical sledge hammer approarch to systems decomposition will not work with complex systems.  User stories fail to guide in proper decomposition.

After such consideration THEN think tools.  My favorite tools, by the way, are pencils, paper, white out, and scotch tape - especially for complex systems.



Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Tools for documentation and requirements management

Community Blog - Latest Posts

In today's dynamic business environment, mastering effective business analysis techniques is crucial for organizations aiming to achieve sustainable growth and competitive advantage. Business analysis involves the systematic evaluation of business processes, requirements, and strategies to uncover insights that drive informed decision-making. T...
For many years now, a lot of people have found it difficult to identify the difference between Sankey diagrams and parallel sets. The two have made headlines, given that most people find it challenging to note what makes them different from each other. What remains to be undeniable is the fact that the Sankey diagram is among the top data visualiza...
Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - Business Architecture and AI In our recent conversation with Joseph Edward, we explored the transformative power of business architecture (BA) and technology as tools for uplifting communities. Joseph, with his rich background spanning from education to IT leadership, shared...



Copyright 2006-2024 by Modern Analyst Media LLC