I use MS Word for my intial discovery document with MS Visio for diagrams. For requirements i often start with spreadsheets, but our official tool at work is DOORS.

It does offer good traceability but is fiddly to use. The worse feature is the method for adding a row. This is one of the most common things we do, but its a real pain.

I think the designers need to spend more time with their customers!

We also use Visio for proces maps, its OK but if you need to move things, watch out!

I love Bizagi at home. Its so easy for process maps, Microsoft look out! more tools nedd to be designed this way.

For requirement discovery  meetings, well its the good old paper and post it notes.

whatever you use, think of your audience.

hi......

i am using some software in my computer system that is..

• SOFTWARE: MS World, PURPOSE: Functional Specifications, Requirements Documents, Vision Document, Business Case.
• SOFTWARE: MS Excel, PURPOSE: Capacity planning, Traceability, Data Analysis.
• SOFTWARE: MS Visio, PURPOSE: Process Models, Use Case Models, Domain Models (Class Diagram), Sequence Diagrams.
• SOFTWARE: ErWin, PURPOSE: Entity Relationship Diagrams.
• SOFTWARE: MS PowerPoint, PURPOSE: Present of problem statements, Present possible solutions, etc.
• SOFTWARE: Visual Studio Web Edition, PURPOSE: UI Mockups, Prototypes
• SOFTWARE:Vlc Media Player,Purpose For Listen Music and Watching Vedio..
•