Time required to design a database

#1

Hi,

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?

Thanks,
Joe

#2

On 1/10/2011 8:02 PM, Joe Hesse wrote:

Quote:

Hi,

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?

Thanks,
Joe

Anywhere from a couple of days to a year or more.

Number of tables is only a *very* minor piece of a very big puzzle. You
need the entire requirements to give even a ballpark figure.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex (AT) attglobal (DOT) net
==================

#3

Quote:

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?

#4

On Jan 11, 5:26*am, Michael Vilain <vil... (AT) NOspamcop (DOT) net> wrote:

Quote:

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" ;-)

#5

Joe Hesse wrote:

Quote:

Hi,

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?

Thanks,
Joe
About 6 an months. Takes me about two days to write a given screen form:

More if its complex.

#6

Captain Paralytic wrote:

Quote:

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.

What do you expect from a country that constantly invents new longer
words to overcome their inferiority complex.

I pissed myself laughing watching Cagney and Lacey when they said
'burglarize' - I mean everyone knows that a burglar is someone who
burgles...Until I discovered that is in fact the actual normal word in use.

#7

Joe Hesse:

Quote:

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?

Hi Joe,
can you say something about the complexity of the organization? How
much effort is required to get your application tested by users and
decision makers? How difficult is it to get the application through
Change Management?

[If end users are hardly involved and there's no formal Change
Management in place, my first vague guess would be one to several
months for requirement sessions (3 sessions a week, including
definition of interfaces to other applications), and 200-400 hours of
programming (including programmer's tests). But then the fun part
starts!]

--
Erick
"How much for a 19th century painting?"

#8

On Jan 11, 11:30*am, The Natural Philosopher <t... (AT) invalid (DOT) invalid>
wrote:

Quote:

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".

#9

"Captain Paralytic" <paul_lautman (AT) yahoo (DOT) com> wrote

Quote:

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

#10

Captain Paralytic wrote:

Quote:

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".

Oh well.

Its hard to tell, with Americans

Gage is acceptable spelling, in English, but its a type of plum.