Documentation: How thorough are you with it?
-
There is a lot going on with a project outside of the FRD. This is what I am driving at.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
What is FRD? I hope it is kid-sister-safe. You never know when it comes to any F word. :laugh:
-
Not code documentation so much but the documentation involved with requests/mods/enhancements. Stuff like who made the request, dates and times, reason for the change or mod, that kind of stuff. Documentation that you would use for audit purposes and for catching people in lies. I am glad that I archive my e-mails and keep files for EVERY project that I work on; it has saved my ass on numerous occasions. I have been in a back and forth, he said - she said, ordeal as of late, where a project manager has said that they notified us of some enhancements/changes that needed to be made and we show no documentation or proof that this meeting ever took place. Now, the powers that be want to know who dropped the ball.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
Fortunately this no longer impinges on my life. I say fortunately because I was probably the worlds worst. Code documentation - immaculate. Any other form of documentation - abysmal. I would forever be in the situation of meeting 'fred' (who submitted a feature request a couple of days ago), in the lift or canteen, or wherever, and during the conversation we would agree some change to it. That remained in my head, it got done, but wouldn't be documented until the completion stage. Personally I blame him, he should have submitted a change to the change request.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
-
What is FRD? I hope it is kid-sister-safe. You never know when it comes to any F word. :laugh:
Functional Requirements Document/Documentation I believe and yes it is an F word. :-D
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
-
Not code documentation so much but the documentation involved with requests/mods/enhancements. Stuff like who made the request, dates and times, reason for the change or mod, that kind of stuff. Documentation that you would use for audit purposes and for catching people in lies. I am glad that I archive my e-mails and keep files for EVERY project that I work on; it has saved my ass on numerous occasions. I have been in a back and forth, he said - she said, ordeal as of late, where a project manager has said that they notified us of some enhancements/changes that needed to be made and we show no documentation or proof that this meeting ever took place. Now, the powers that be want to know who dropped the ball.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
"Documentation" you say? Hmm, documentation,, DocumentAtion... I'm sure I've heard the word somewhere...
MVVM# - See how I did MVVM my way ___________________________________________ .\\axxx (That's an 'M')
-
Functional Requirements Document/Documentation I believe and yes it is an F word. :-D
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
Oh, I get it. That's the one analyst gives you after you have done all your coding. :) In exchange, I give them the SDD.
-
Functional Requirements Document/Documentation I believe and yes it is an F word. :-D
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
Slacker007 wrote:
Functional Requirements Document/Documentation
No swearing in the lounge please. :-D
...and I have extensive experience writing computer code, including OIC, BTW, BRB, IMHO, LMAO, ROFL, TTYL.....
-
Not code documentation so much but the documentation involved with requests/mods/enhancements. Stuff like who made the request, dates and times, reason for the change or mod, that kind of stuff. Documentation that you would use for audit purposes and for catching people in lies. I am glad that I archive my e-mails and keep files for EVERY project that I work on; it has saved my ass on numerous occasions. I have been in a back and forth, he said - she said, ordeal as of late, where a project manager has said that they notified us of some enhancements/changes that needed to be made and we show no documentation or proof that this meeting ever took place. Now, the powers that be want to know who dropped the ball.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
I save every e-mail I get, and I usually (well, sometimes) add a code comment on a feature saying which user requested it... If I think it's a stupid idea, I'll usually add something like:
/* Yes, this looks stupid and counter-intuitive, but ____
* wanted it to work this way. (IS 2011-05-19)
*/But not much formal documentation... I'm a one-man development team.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
I save every e-mail I get, and I usually (well, sometimes) add a code comment on a feature saying which user requested it... If I think it's a stupid idea, I'll usually add something like:
/* Yes, this looks stupid and counter-intuitive, but ____
* wanted it to work this way. (IS 2011-05-19)
*/But not much formal documentation... I'm a one-man development team.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Ian Shlasko wrote:
I'm a one-man development team.
I belong to a 4 person team (was going to say "man" but we do have a female in the team). 2 seniors, 1 junior, and one obnoxious 2 year old (myself). :)
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
-
Not code documentation so much but the documentation involved with requests/mods/enhancements. Stuff like who made the request, dates and times, reason for the change or mod, that kind of stuff. Documentation that you would use for audit purposes and for catching people in lies. I am glad that I archive my e-mails and keep files for EVERY project that I work on; it has saved my ass on numerous occasions. I have been in a back and forth, he said - she said, ordeal as of late, where a project manager has said that they notified us of some enhancements/changes that needed to be made and we show no documentation or proof that this meeting ever took place. Now, the powers that be want to know who dropped the ball.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
I'm very bad at it, although I do keep every e-mail sent or received. We're at the start of a big culture shift here though, where before anything can be put live it needs the following documents; Technical Details User Guide Requirements Design Sign Off I am sure you can see the acronym for yourself, but it is absolutely true.
Every man can tell how many goats or sheep he possesses, but not how many friends.
-
Slacker007 wrote:
Now, the powers that be want to know who dropped the ball.
That's good. In my company, the power that be never want to know who dropped the ball. All they ever ask is who can fix it and how long will it take. By not asking, I think they assume it is your fault (your name is the de-fault value). :)
Xiangyang Liu 刘向阳 wrote:
(your name is the de-fault value
:doh:
-
Slacker007 wrote:
Now, the powers that be want to know who dropped the ball.
That's good. In my company, the power that be never want to know who dropped the ball. All they ever ask is who can fix it and how long will it take. By not asking, I think they assume it is your fault (your name is the de-fault value). :)
-
Ian Shlasko wrote:
I'm a one-man development team.
I belong to a 4 person team (was going to say "man" but we do have a female in the team). 2 seniors, 1 junior, and one obnoxious 2 year old (myself). :)
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
Slacker007 wrote:
(was going to say "man" but we do have a female in the team)
Wow, really? That's rare.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
I'm very bad at it, although I do keep every e-mail sent or received. We're at the start of a big culture shift here though, where before anything can be put live it needs the following documents; Technical Details User Guide Requirements Design Sign Off I am sure you can see the acronym for yourself, but it is absolutely true.
Every man can tell how many goats or sheep he possesses, but not how many friends.
The smell is always there. :) :thumbsup:
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
-
Slacker007 wrote:
(was going to say "man" but we do have a female in the team)
Wow, really? That's rare.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Ian Shlasko wrote:
That's rare.
Sarcasm? Can't tell. I have always worked in shops that have women on the teams. Some of the best developers I have worked with are women. My immediate boss is a woman and I have learned a lifetime of stuff from her.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
-
Not code documentation so much but the documentation involved with requests/mods/enhancements. Stuff like who made the request, dates and times, reason for the change or mod, that kind of stuff. Documentation that you would use for audit purposes and for catching people in lies. I am glad that I archive my e-mails and keep files for EVERY project that I work on; it has saved my ass on numerous occasions. I have been in a back and forth, he said - she said, ordeal as of late, where a project manager has said that they notified us of some enhancements/changes that needed to be made and we show no documentation or proof that this meeting ever took place. Now, the powers that be want to know who dropped the ball.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
-
Ian Shlasko wrote:
That's rare.
Sarcasm? Can't tell. I have always worked in shops that have women on the teams. Some of the best developers I have worked with are women. My immediate boss is a woman and I have learned a lifetime of stuff from her.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
Wow, really? My entire career, I've only worked with two female developers... Well, they were on the server team, while I was working on the client, but still... There were a couple women in QA too, but no other programmers.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels) -
Wow, really? My entire career, I've only worked with two female developers... Well, they were on the server team, while I was working on the client, but still... There were a couple women in QA too, but no other programmers.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Ian Shlasko wrote:
Wow, really?
Yes. and some are very easy on the eyes as well. ;)
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
-
Not code documentation so much but the documentation involved with requests/mods/enhancements. Stuff like who made the request, dates and times, reason for the change or mod, that kind of stuff. Documentation that you would use for audit purposes and for catching people in lies. I am glad that I archive my e-mails and keep files for EVERY project that I work on; it has saved my ass on numerous occasions. I have been in a back and forth, he said - she said, ordeal as of late, where a project manager has said that they notified us of some enhancements/changes that needed to be made and we show no documentation or proof that this meeting ever took place. Now, the powers that be want to know who dropped the ball.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
That's what BA's are for.
I wasn't, now I am, then I won't be anymore.
-
Actually that is a very good practice ! At least they focus on a solution instead of on the problem. :-D
V.
It is also polical correctness. Basically there is no reward for high quality work and no punishment for screwing up, because nobody should be "pointing fingers" no matter what.
-
Not code documentation so much but the documentation involved with requests/mods/enhancements. Stuff like who made the request, dates and times, reason for the change or mod, that kind of stuff. Documentation that you would use for audit purposes and for catching people in lies. I am glad that I archive my e-mails and keep files for EVERY project that I work on; it has saved my ass on numerous occasions. I have been in a back and forth, he said - she said, ordeal as of late, where a project manager has said that they notified us of some enhancements/changes that needed to be made and we show no documentation or proof that this meeting ever took place. Now, the powers that be want to know who dropped the ball.
-- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.
FRD before coding starts (I call it a Solutions Requirement Document, although it is heavy on Function and light on Form), possibly augmented by Use Cases. Solutions Control Document after the project is implemented - describes the platform, deployment type, etc. Additonally, we are bound by Sarbanes-Oxley (SOX) auditing, and every change/implementation to a production server requires a Change Request to be created. This typically includes tasks for: . Request to Proceed (completed by customer) . Testing Completed (completed by customer) . Deployment to Production (documented by IT, approved by Change Management) . Post-Release Review (completed by customer)
