Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Functional analysis, user manual etc.
Message
De
06/06/2007 11:18:00
 
 
À
06/06/2007 11:13:57
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows XP
Database:
Visual FoxPro
Divers
Thread ID:
01230919
Message ID:
01230964
Vues:
16
>>Hi Nikki,
>>
>>The terms 'program analysis' and 'functional analysis' are not used by me. My terms are 'technical documentation' (FD) as opposed to 'functional documentation' (TD).
>>
>>The FD and TD are officially two separate documents, but I also sometimes see only one document that contains both. Officially the FD must be written by a functional analyst, or better: business analyst (BA), whereas the TD is written by the systems analyst (SA) or systems programmer, whatever the inhouse name for this advanced employee is. The BA uses a non-technical approach and the SA 'translates' the FD to a 'technical' story.
>
>What? are you talking in Dutch to Nikki here?

Not sure what you're implying here, but if it's the wrong placement of (FD) and (TD) in the first sentence, that was to check whether it is read with attention. <g>

>>
>>If you are a BA, then it can be expected that you deliver an FD. The SA is the one for the SD. If you're 'merely' a programmer, then both can't really be expected from you. If these types of documentation are missing, then that is because the bosses have never regarded it to be an important topic.
>>
>>The consultant is not necessarilly trying to impress the boss. If he uses the right arguments and shows patience and understanding, then it may well turn out to be an impetus to all to become more professional and thus to benefit in the long run.
>>
>>The boss must be willing to professionalize all his employees and offer them the chance to do so. And that includes offering the opportunity to go back to (evening) school.
>>
>>
>>>i hv been a progrmmer for a few years most of it self taught, no fancy college stuff. recently our company hired a consultant and he was surprised that i hv not yet created a
>>>
>>>functional analysis
>>>program analysis
>>>user manual
>>>
>>>of the program
>>>
>>>and a lot of other stuff,
>>>
>>>we only have 5 employees in our company, everyone knows the program inside out.
>>>
>>>my question here is
>>>
>>>1. how important are these things and what are these things (except the user manual which i understand)
>>>
>>>2. is the consultant just trying to impress my boss
>>>
>>>3. what other documentations are there which are necessary to be done along with the program?
>>>
>>>4. where do i get to learn all this stuff?
>>>
>>>any help is welcome
>>>
>>>thanks
Groet,
Peter de Valença

Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform