atw: Documenting and the Zachman Framework
- From: "John New" <jpnew@xxxxxxxxxxxxxxx>
- To: <austechwriter@xxxxxxxxxxxxx>
- Date: Sat, 5 Jun 2004 16:33:51 +1000
Hi all,
I'm working on a contract with an organisation who have a documentation
problem.
They have a lot of existing documentation that documents their computer
systems and networks but much of it is incomplete. They also know that there
is a lot that should be documented but isn't.
I've been asked to do a requirements-led analysis using the Zachman
Framework (do a search on Google if you don't know what this is, I didn't).
I am to use the Zachman Framework to analyse what should be documented. Then
compare this with what is already documented and with what isn't but should
be documented (basically assume everything should be). Then prepare a
strategy to create a documentation framework for all documentation. Then
create a project timeline to get everything documented. Then get stuck into
the actual writing.
Has anyone done this before, that is, used the Zachman Framework to help
create a documentation plan? If so, would you like to share your experiences
with me and everyone else? I would very much appreciate it.
Regards,
John New
jpnew@xxxxxxxxxxxxx
http://www.writetechniques.com/
**************************************************
To post a message to austechwriter, send the message to
austechwriter@xxxxxxxxxxxxxx
To subscribe to austechwriter, send a message to
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field.
To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with
"unsubscribe" in the Subject field.
To search the austechwriter archives, go to
www.freelists.org/archives/austechwriter
To contact the list administrator, send a message to
austechwriter-admins@xxxxxxxxxxxxx
**************************************************
Other related posts:
- » atw: Documenting and the Zachman Framework
