TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
UML as a TW requirement tells you a lot about the job, I think. If they rely on it, then they probably use it for design and development... UML not only describes a system, it can generate the scaffolding code for the whole system, or at least for each component of the system. So I would expect the dev team to be reasonably invested in UML as a development methodology. That's good news for you -- it means they actually *design* their software. If they do it right, it means you have diagrams to illustrate the design, from user characterizations and use cases, through process flows, all the way down to class interfaces. It's worth it to expose yourself to UML just so you can land a job on such a team.
That plus Agile, and you're finally in the 21st Century!
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-