When is a Database Finished. Where do I stop. (1 Viewer)

RainLover

VIP From a land downunder
Local time
Today, 20:49
Joined
Jan 5, 2009
Messages
5,044
Programming is:

Phase 1
Design
Coding
Testing, Testing, Testing
Find what does not work

Phase 2
More Design
More Coding
More Testing, Testing, Testing
Find what does not work now

repeat Phase 2 until you do not find an more issues.

Phase 3
Give the app to the end users
End users find what does not work now
Go back to Phase 2

Phase 4
Wait for the end users to have issues or the requirement have changed
or
Developer/programmer learns how to do things better

Go back to Phase 2

Phase 5
Developer/programmer learns how to do things better and the original design will no longer meet the needs of the users.

Time scrap the old app and create a new one and convert the data.

Back to Phase 1.


I have found that a database app never really is finished until it is no longer used at all.

 

Galaxiom

Super Moderator
Staff member
Local time
Today, 20:49
Joined
Jan 20, 2009
Messages
11,989
From the developer's perspective, the database is finished when they are no longer paid to keep working on it.
 

The_Doc_Man

Happy Retired Curmudgeon
Local time
Today, 05:49
Joined
Feb 28, 2001
Messages
17,044
The only time an application can be finished is if the process on which it is modeled can never be changed again. Which is why the government thinks that some projects can actually be finished. But as long as Congress is still alive and kicking, it ain't necessarily so.
 

gemma-the-husky

Super Moderator
Staff member
Local time
Today, 11:49
Joined
Sep 12, 2006
Messages
13,892
I think its finished when the user has an app that does what he wants.

It may need some support from time to time, but generally that's it.

I have several apps that have been running without amendment or intervention for at least 5 years.
 

ButtonMoon

Registered User.
Local time
Today, 11:49
Joined
Jun 4, 2012
Messages
304
I have found that a database app never really is finished until it is no longer used at all
Exactly. Software should reflect changing business needs. Very often change is the only constant.

Your description of the software lifecycle looks like a Waterfall methodology. Many organisations have realized that Waterfall isn't such a good fit for the modern business environment. Increasingly these days Agile software development approaches are used instead (Scrum, Kanban, XP).
 

RainLover

VIP From a land downunder
Local time
Today, 20:49
Joined
Jan 5, 2009
Messages
5,044
I hope you all realise that what I posted was mainly for light entertainment. Even though it is based upon reality.
 

vbaInet

AWF VIP
Local time
Today, 11:49
Joined
Jan 22, 2010
Messages
26,374
After several iterations...

Phase 5

Fix all bugs, test, hand over to client's IT guys, do a runner!
 

spikepl

Eledittingent Beliped
Local time
Today, 12:49
Joined
Nov 3, 2010
Messages
6,144
That is all totally [struck by the censor].


Any project has 6 phases:


  1. Enthusiasm,
  2. Disillusionment,
  3. Panic and hysteria,
  4. Hunt for the guilty,
  5. Punishment of the innocent, and
  6. Reward for the uninvolved
.
 
Last edited:

The_Doc_Man

Happy Retired Curmudgeon
Local time
Today, 05:49
Joined
Feb 28, 2001
Messages
17,044
Spike, you must have worked for the U.S. Government as a contractor (if you know the six-step project guide).
 

burrina

Registered User.
Local time
Today, 05:49
Joined
May 10, 2014
Messages
974
Rain, I was thoroughly entertained, Thanks for the memories.

P.S.
Short Answer: NEVER
 

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Top Bottom