Results 1 to 4 of 4
  1. #1
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Melbourne, Australia
    Posts
    1,294
    Thanks
    0
    Thanked 0 Times in 0 Posts

    spec documentation (word97 sr2b)

    Hiya

    I've been asked to write some in-house documentation on obtaining specifications for new projects the projects being Word documents.
    As what were experiencing is our users are always sneaking new changes into existing projects & that obviously blows out & effects delivery dates & the actual project becomes a monster.
    Are there any books or websites which have a step by step instructions for obtaining specifications from the users that I can use as guidelines?

    many thanks
    Diana

  2. #2
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Location
    Silicon Valley, USA
    Posts
    23,112
    Thanks
    5
    Thanked 93 Times in 89 Posts

    Re: spec documentation (word97 sr2b)

    This might fit under the banner of "project management" books for software development. I've never read any of them, but there sure seem to be a lot out there. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  3. #3
    5 Star Lounger jujuraf's Avatar
    Join Date
    Jun 2001
    Location
    San Jose, California, USA
    Posts
    1,061
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: spec documentation (word97 sr2b)

    No matter how well a spec is written, if no one enforces it, it's just toilet paper <img src=/S/hosed.gif border=0 alt=hosed width=73 height=24>

    I've done lots of specs, and for bad or worse everyone says they want them, but they hate to write then and follow them. The 'official' way to do it for software is using UML (actually you can use this for non-software too). It's a process whereby you really have to think about your end users (those people who have use your hopefully well thought-out tool), flow of data between each components, error handling, and tons of other things.The more time you spend on the spec, the easier development and debugging will be. Unfortunately few people (aka managers) like to see their engineers sitting around thinking and writing, they want them pounding out code (even if it's wrong and needs to be re-written 10 times).

    What's that saying... there's never time to do it right, but there's always time to do it again. <img src=/S/bash.gif border=0 alt=bash width=35 height=39>

    You can be as detailed as you want with UML (more the better but then reality takes over and enough is enough...). There are tools that make it easier to write (prepare the diagrams) but you can do it manually for a small project.

    http://uml.tutorials.trireme.com/
    http://www.pacestar.com/uml/index.html
    http://www.rational.com/uml/index.jsp?SMSESSION=NO
    (Rational has the most used tools for UML)

    Can you tell I've been down this road too many times? <img src=/S/cranky.gif border=0 alt=cranky width=18 height=25>

    Deb

  4. #4
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Melbourne, Australia
    Posts
    1,294
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: spec documentation (word97 sr2b)

    HI Deb -
    thanks for the website links. I'll have a look at them.
    many thanks Diana

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •