U++ framework: Coffee corner » What do you do first when you start developing an application?

Home » Community » Coffee corner » What do you do first when you start developing an application?

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

What do you do first when you start developing an application? [message #38396]

Thu, 13 December 2012 21:13

lectus
Messages: 329
Registered: September 2006
Location: Brazil

Senior Member

Some people recommend that we create the database first and then we create the application interface and logic to handle that.

What's your opinion?

Report message to a moderator

Re: What do you do first when you start developing an application? [message #38400 is a reply to message #38396]

Thu, 13 December 2012 22:00

zsolt
Messages: 705
Registered: December 2005
Location: Budapest, Hungary

Contributor

I write a textfile with requirements first.
Then I start implementation with one of the requirements.
I create a very small part of the database and code fulfilling only the selected requirement. I like creating unit tests first, but not always.
After the first requirement I continue with an other one and so on.

This is a natural way of software development, I think.
Nowadays this is called agile development Smile

Report message to a moderator

Re: What do you do first when you start developing an application? [message #38408 is a reply to message #38396]

Fri, 14 December 2012 12:02

dolik.rce
Messages: 1796
Registered: August 2008
Location: Czech Republic

Ultimate Contributor

I usually follow the same flow as zsolt, minus the writing to textfile (I'm very lazy Smile

)

Also, I usually start without GUI (if possible), writing the main functionality as console app, testing it with some fixed values representing user inputs and only later binding the functions to GUI.

Honza

Report message to a moderator

Re: What do you do first when you start developing an application? [message #38412 is a reply to message #38396]

Fri, 14 December 2012 14:13

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

lectus wrote on Thu, 13 December 2012 15:13

Some people recommend that we create the database first and then we create the application interface and logic to handle that.

What's your opinion?

Well, if it is some client/server SQL stuff, I usually develop GUI and DB together.

Sometimes even going so far that I design dialog layout first, then copy dialog widget ids into .sch file and make a SQL table out of it.

Generally, I always liked to create simple skeleton app first, then continually add features, improving things in all parts.

I do not even care too much about requirements. Usually it is faster for me to create more iterations of code - usual problem being is that to interrogating users about requirements is time consuming process, but it is much easier to them to tell you what is wrong with the application (something they can see and try to use).

Report message to a moderator

Previous Topic:	Frustration when not using U++
Next Topic:	Automatic generation of SCH-file from UML

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Nov 04 08:06:51 GMT+1 2026

Total time taken to generate the page: 0.40784 seconds