Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Not about tools (mostly) (Score 1) 370

As others have said this isn't principly about tools, but about finding a simple and effective ways to extract and record the processes.

Don't get hung up on formal process notations unless you are planning to turn them into software / workflows.

I have done some of my most effective work with pen & paper / flipcharts. For documenting more formally Visio / Smartdraw or other simple diagramming software will do.

Techniques: soft systems for the big picture, use cases to identify processes and actors, activity diagrams with swimlanes for the actual processe.

Agree that somone outside of the process should be lead the documantation as they can ask the dumb questions.

Don't try and document all proceses - use a riak assesment ot identify key processes.

As for keeoping the documentation up to date -how often do the processes change? If they do change as part of a project ensure the project is responsible for updating the documenation

Once models are signed off make sure they are available to those who need them. If the only person who knows which folder they are in goes under a bus you have the same problem!

Good Luck!

United States

Submission + - Shooting at Virginia Tech leaves at least 32 dead

marcelo writes: A gunman massacred 32 people at Virginia Tech in the deadliest shooting rampage in modern U.S. history Monday, cutting down his victims in two attacks two hours apart before the university could grasp what was happening and warn students.

Slashdot Top Deals

Elliptic paraboloids for sale.