Time required to design a database

#11

Brian Cryer wrote:

Quote:

"Captain Paralytic" <paul_lautman (AT) yahoo (DOT) com> wrote in message
news:30e9cab8-e20f-4c48-bfa4-050b44ee14d9 (AT) f8g2000yqd (DOT) googlegroups.com...
On Jan 11, 11:30 am, The Natural Philosopher <t... (AT) invalid (DOT) invalid
wrote:
Captain Paralytic wrote:
On Jan 11, 5:26 am, Michael Vilain <vil... (AT) NOspamcop (DOT) net> wrote:
In article
vbydneSX68iBJbbQnZ2dnUVZ_qidn... (AT) posted (DOT) internetamerica>,
gordonb.ka... (AT) burditt (DOT) org (Gordon Burditt) wrote:

I know this is a vague question but maybe someone can help.
Suppose we have an app with a MySQL database of 20 or so tables
and > >>>> the
app is web based, say LAMP. What ballpark figure is available
to > >>>> how
much time it would take to write the app, from understanding the
requirements to delivering a working app?
Does the app have to be PCI-compliant? (handles credit card
information?)
Does the app have to be HIPAA compliant? (contains patient medical
information?)
Does the app have to be certified by the FAA? (does it fly
airplanes?)
I suspect that alone adds 5 years, regardless of how much manpower
you add to the project.
Does the app operate a nuclear reactor?
How many changes in requirements will there be per week?
Will it be in a reasonable ballpark if I answer "4", leaving it
to someone else to indicate whether it means 4 hours or 4 decades?
Truly, after 20+ years in software and sysadmin, what divided me
from > >> a
junior programmer to a more senior one was the ability to accurately
gage "how long would it take you?" And that's just my ability to
code.

Then there's the project management skill of looking at the
requirements
(fixed price or open-ended Time&Materials), have a sense of what
direction a project might grow, and gage how much it would take to
design (that's the hard part), code, build, and integrate it all
together.

Luckily enough one of the requirements to progress from a junior
programmer wasn't the ability to spell words like "gauge" ;-)

I think that is acceptable american spelling.

You think wrong then. I checked before I posted and even the Americans
spell it "gauge".

Perhaps you should have spent just a little bit more time checking it
out - according to http://en.wikipedia.org/wiki/Gage quote "Gage is a
variant spelling of the word gauge".

That's what I thought.

But if someone asks me to pass a green gage, he's going to get a soft fruit.

#12

On Jan 11, 3:20*pm, "Brian Cryer" <not.h... (AT) localhost (DOT) invalid> wrote:

Quote:

"Captain Paralytic" <paul_laut... (AT) yahoo (DOT) com> wrote in message

news:30e9cab8-e20f-4c48-bfa4-050b44ee14d9 (AT) f8g2000yqd (DOT) googlegroups.com...

On Jan 11, 11:30 am, The Natural Philosopher <t... (AT) invalid (DOT) invalid
wrote:
Captain Paralytic wrote:
On Jan 11, 5:26 am, Michael Vilain <vil... (AT) NOspamcop (DOT) net> wrote:
In article <vbydneSX68iBJbbQnZ2dnUVZ_qidn... (AT) posted (DOT) internetamerica>,
gordonb.ka... (AT) burditt (DOT) org (Gordon Burditt) wrote:

I know this is a vague question but maybe someone can help.
Suppose we have an app with a MySQL database of 20 or so tables and
the
app is web based, say LAMP. What ballpark figure is available to
how
much time it would take to write the app, from understanding the
requirements to delivering a working app?
Does the app have to be PCI-compliant? (handles credit card
information?)
Does the app have to be HIPAA compliant? (contains patient medical
information?)
Does the app have to be certified by the FAA? (does it fly
airplanes?)
I suspect that alone adds 5 years, regardless of how much manpower
you add to the project.
Does the app operate a nuclear reactor?
How many changes in requirements will there be per week?
Will it be in a reasonable ballpark if I answer "4", leaving it
to someone else to indicate whether it means 4 hours or 4 decades?
Truly, after 20+ years in software and sysadmin, what divided me from
a
junior programmer to a more senior one was the ability to accurately
gage "how long would it take you?" And that's just my ability to
code.

Then there's the project management skill of looking at the
requirements
(fixed price or open-ended Time&Materials), have a sense of what
direction a project might grow, and gage how much it would take to
design (that's the hard part), code, build, and integrate it all
together.

Luckily enough one of the requirements to progress from a junior
programmer wasn't the ability to spell words like "gauge" ;-)

I think that is acceptable american spelling.

You think wrong then. I checked before I posted and even the Americans
spell it "gauge".

Perhaps you should have spent just a little bit more time checking it out-
according tohttp://en.wikipedia.org/wiki/Gagequote "Gage is a variant
spelling of the word gauge".
--
*Brian Cryer
*http://www.cryer.co.uk/brian

I used an American dictionary (well 2 of them actually). They tend to
be written by folks who really know.

#13

On Tue, 11 Jan 2011 15:20:43 -0000, Brian Cryer wrote:

Quote:

Perhaps you should have spent just a little bit more time checking it out -
according to http://en.wikipedia.org/wiki/Gage quote "Gage is a variant
spelling of the word gauge".

*grin* Using Wikipedia to prove anything is an exercise in futility. I
can prove almost anything with it, for several minutes at a time.

--
54. I will not strike a bargain with a demonic being then attempt to
double-cross it simply because I feel like being contrary.
--Peter Anspach's list of things to do as an Evil Overlord

#14

"Brian Cryer" <not.here (AT) localhost (DOT) invalid> wrote

Quote:

"Captain Paralytic" <paul_lautman (AT) yahoo (DOT) com> wrote in message
news:30e9cab8-e20f-4c48-bfa4-050b44ee14d9 (AT) f8g2000yqd (DOT) googlegroups.com...
On Jan 11, 11:30 am, The Natural Philosopher <t... (AT) invalid (DOT) invalid
wrote:
Captain Paralytic wrote:
On Jan 11, 5:26 am, Michael Vilain <vil... (AT) NOspamcop (DOT) net> wrote:
In article
vbydneSX68iBJbbQnZ2dnUVZ_qidn... (AT) posted (DOT) internetamerica>,
gordonb.ka... (AT) burditt (DOT) org (Gordon Burditt) wrote:

I know this is a vague question but maybe someone can help.
Suppose we have an app with a MySQL database of 20 or so tables
and the
app is web based, say LAMP. What ballpark figure is available to
how
much time it would take to write the app, from understanding the
requirements to delivering a working app?
Does the app have to be PCI-compliant? (handles credit card
information?)
Does the app have to be HIPAA compliant? (contains patient medical
information?)
Does the app have to be certified by the FAA? (does it fly
airplanes?)
I suspect that alone adds 5 years, regardless of how much manpower
you add to the project.
Does the app operate a nuclear reactor?
How many changes in requirements will there be per week?
Will it be in a reasonable ballpark if I answer "4", leaving it
to someone else to indicate whether it means 4 hours or 4 decades?
Truly, after 20+ years in software and sysadmin, what divided me
from a
junior programmer to a more senior one was the ability to accurately
gage "how long would it take you?" And that's just my ability to
code.

Then there's the project management skill of looking at the
requirements
(fixed price or open-ended Time&Materials), have a sense of what
direction a project might grow, and gage how much it would take to
design (that's the hard part), code, build, and integrate it all
together.

Luckily enough one of the requirements to progress from a junior
programmer wasn't the ability to spell words like "gauge" ;-)

I think that is acceptable american spelling.

You think wrong then. I checked before I posted and even the Americans
spell it "gauge".

Perhaps you should have spent just a little bit more time checking it
out - according to http://en.wikipedia.org/wiki/Gage quote "Gage is a
variant spelling of the word gauge".
--
Brian Cryer
http://www.cryer.co.uk/brian

Should have added, its not the way I'd spell it and I'd assumed it was a
typo.
--
Brian Cryer
http://www.cryer.co.uk/brian

#15

On Jan 11, 4:00*pm, "Brian Cryer" <not.h... (AT) localhost (DOT) invalid> wrote:

Quote:

"Brian Cryer" <not.h... (AT) localhost (DOT) invalid> wrote in message

news:ighsgh$g6j$1 (AT) news (DOT) eternal-september.org...

"Captain Paralytic" <paul_laut... (AT) yahoo (DOT) com> wrote in message
news:30e9cab8-e20f-4c48-bfa4-050b44ee14d9 (AT) f8g2000yqd (DOT) googlegroups.com...
On Jan 11, 11:30 am, The Natural Philosopher <t... (AT) invalid (DOT) invalid
wrote:
Captain Paralytic wrote:
On Jan 11, 5:26 am, Michael Vilain <vil... (AT) NOspamcop (DOT) net> wrote:
In article
vbydneSX68iBJbbQnZ2dnUVZ_qidn... (AT) posted (DOT) internetamerica>,
gordonb.ka... (AT) burditt (DOT) org (Gordon Burditt) wrote:

I know this is a vague question but maybe someone can help.
Suppose we have an app with a MySQL database of 20 or so tables
and the
app is web based, say LAMP. What ballpark figure is available to
how
much time it would take to write the app, from understanding the
requirements to delivering a working app?
Does the app have to be PCI-compliant? (handles credit card
information?)
Does the app have to be HIPAA compliant? (contains patient medical
information?)
Does the app have to be certified by the FAA? (does it fly
airplanes?)
I suspect that alone adds 5 years, regardless of how much manpower
you add to the project.
Does the app operate a nuclear reactor?
How many changes in requirements will there be per week?
Will it be in a reasonable ballpark if I answer "4", leaving it
to someone else to indicate whether it means 4 hours or 4 decades?
Truly, after 20+ years in software and sysadmin, what divided me
from a
junior programmer to a more senior one was the ability to accurately
gage "how long would it take you?" And that's just my ability to
code.

Then there's the project management skill of looking at the
requirements
(fixed price or open-ended Time&Materials), have a sense of what
direction a project might grow, and gage how much it would take to
design (that's the hard part), code, build, and integrate it all
together.

Luckily enough one of the requirements to progress from a junior
programmer wasn't the ability to spell words like "gauge" ;-)

I think that is acceptable american spelling.

You think wrong then. I checked before I posted and even the Americans
spell it "gauge".

Perhaps you should have spent just a little bit more time checking it
out - according tohttp://en.wikipedia.org/wiki/Gagequote "Gage is a
variant spelling of the word gauge".
--
Brian Cryer
http://www.cryer.co.uk/brian

Should have added, its not the way I'd spell it and I'd assumed it was a
typo.
When it is done more than once it usually signifies more than a typo.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Time required to design a database

comp.databases.mysql comp.databases.mysql

Re: Time required to design a database - 01-11-2011 , 09:46 AM

Re: Time required to design a database - 01-11-2011 , 09:51 AM

Re: Time required to design a database - 01-11-2011 , 09:57 AM

Re: Time required to design a database - 01-11-2011 , 10:00 AM

Re: Time required to design a database - 01-11-2011 , 10:35 AM