French/English:Cahier des Charges or User Process Report (?)

Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy.
This forum is not for asking programming related questions.

Moderator: General Moderators

Post Reply
freddymio
Forum Newbie
Posts: 3
Joined: Mon Jun 10, 2002 6:08 am

French/English:Cahier des Charges or User Process Report (?)

Post by freddymio »

:( Hello!
I can't find the English term for the document that holds Users' Needs in a Project (pre-development).
I'd like a Guideline for structuring that document.
If it is not much to ask, I'd need to know the normal docs involved in a project and their sections. I'm interested in the conventional structure of these documents.
Thanks in advance.
Freddy

Bonjour !
J'aimerais savoir quelles sont les parties qui composent un Cahier des Charges d'un projet. Rien de compliqué, quelque chose "straight forward".
Si ce n'est pas trop demander, j'aimerais aussi la documentation impliquée dans un projet, et ses rubriques. Je suis intéresé à la structuration conventionnelle de ces documents.
Merci d'avance.

Freddy
User avatar
twigletmac
Her Royal Site Adminness
Posts: 5371
Joined: Tue Apr 23, 2002 2:21 am
Location: Essex, UK

Post by twigletmac »

When I was an engineer we used to have,
  • User specification -> what the user wanted,
  • Functional specification -> how we thought we would achieve what the user wanted, and
  • Technical specification -> what it ended up as.
Every company I've worked for seems to structure these documents differently or has a different name for them.

Mac
User avatar
mikeq
Forum Regular
Posts: 512
Joined: Fri May 03, 2002 3:33 am
Location: Edinburgh, Scotland

Post by mikeq »

twigletmac wrote:When I was an engineer we used to have,
  • User specification -> what the user wanted,
  • Functional specification -> how we thought we would achieve what the user wanted, and
  • Technical specification -> what it ended up as.
Every company I've worked for seems to structure these documents differently or has a different name for them.

Mac
Yes ,we use a similar structure with a slight variation

User specification -> what the user is getting
Functional specification -> how we achieve what the user is getting
Technical specification -> what the user got, but not really because no-one bothered to update the document.

:wink: :D :lol:
User avatar
twigletmac
Her Royal Site Adminness
Posts: 5371
Joined: Tue Apr 23, 2002 2:21 am
Location: Essex, UK

Post by twigletmac »

mikeq wrote:User specification -> what the user is getting
Functional specification -> how we achieve what the user is getting
Technical specification -> what the user got, but not really because no-one bothered to update the document.
:lol: I like that - sort of the real world example.

Now I better get back to retrospectively writing that functional spec. for a project that was launched 3 months ago...

Mac
freddymio
Forum Newbie
Posts: 3
Joined: Mon Jun 10, 2002 6:08 am

Post by freddymio »

Thank you Twig and Mike.
I understand that basically there are three reports. Which would be the main sections that make them up?
Have a nice day.

(For the 3rd doc, it seems that the same thing happens mostly everwhere. When a user dies, or resigns, there is no head or tail of how things were finally done... :lol: )

Thanks again
Post Reply