HiYa
I and my group use the Rational documentation process and follow their templates. Look here for an idea of what they do. Bookwise check out the Addison Wesley Object Technology Series with Booch, Jacobsen and Runbaugh as the series editors. A good book to start with is 'The Rational Unified Process An Introduction, Second Edition' - this is required reading within my group. 'Managing Software Requirements' by Leffingwell and Widrig of the same series is a good practical book on requirements gathering and documentation, IMO.I suspect if you look around the web for a bit you'll see templates to use somehwere.
MadraghRua
yet another biologist hacking perl....
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
