Re: Project report requirements

ibeleveyou@xxxxxxxxx said:

Hello,everyone.I need some help about project report requirements.

Do you know how many reports or documents should be made in the
process of sofeware project development .What are they? Thanks.

As many as necessary, but as few as possible. There is no universal (or
even wide) agreement as to what is required, but here's a list of
possibilities that should be trimmed aggressively:

Requirements Specification (produced by customer) - what does the customer
want?
Requirements Analysis (produced by team analyst with input from customer) -
what can the customer have?
Design Specification (produced by team designer with input from analyst) -
what's the best way to provide the requirements?
User Acceptance Test Specification (produced by team analyst with input
from customer) - what is the best way to demonstrate that the program
meets the requirements agreed with the customer?
Program Specification (produced by team lead programmer with input from
designer) - what's the best way to write the program?
Unit Test Specifications (produced by team lead tester with input from
designer and lead programmer) - what is the best way to test the various
modules that will be written, to ensure that each works according to its
specification?
Integration Test Specification (produced by team lead tester with input
from analyst and designer) - what is the best way to ensure that all the
various modules work together properly?
Program Maintenance Documentation (produced by team technical author with
input from designer and lead programmer) - contains information required
by maintenance programmers.
User Documentation (produced by team technical author with input from
analyst, lead programmer, alpha testers, and customer) - what information
does the user need, to be an effective user of the program?

Trim as many as possible, but no more. Each document should be as short as
possible, but no shorter. And each document should be written by someone
who can write. (This last requirement is the hardest, and is hardly ever
met.)

Recommended reading: "A Hacker's Guide to Project Management"

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
.

Relevant Pages

  • Re: XP Requirement Analysis?
    ... > of existing documentation. ... Regarding "how to go to the customer", I would be glad to go into ... When formal analysis and design are bypassed ... these earlier techniques and methodologies, ...
    (comp.object)
  • Re: DTV antennas?
    ... of the customer base has some form of written or on-screen learning or ... How about they can't find the documentation to read? ... It's not easy, rough reading, totally ... Manuals that are full of illustration and examples work ...
    (sci.electronics.design)
  • Re: OpenVMS Support Issues
    ... assumed that the call tracking system does this on its own, without the customer ... documentation; if you want something done, ... should be making its money by contractimng to fix the customer's broken systems, ... Unofficial OpenVMS Hobbyist Support Page: ...
    (comp.os.vms)
  • Re: Write a GUI for a python script?
    ... the Dabo Designer that contains a Notebook. ... I'm having a heck of a time finding any documentation at all on ... I don't want to code the GUI ...
    (comp.lang.python)
  • Re: Once again, comparison wxpython with PyQt
    ... Qt has far better documentation, and it has Qt Designer. ... I wrote a little project in wxPython, and I spent 90% of my time just trying to find the names of member functions and then to figure out what they do. ... Pros for Qt: ...
    (comp.lang.python)