Click here to Skip to main content
15,850,446 members

Survey Results

How important is software architecture in Software Development?   [Edit]

Survey period: 8 Mar 2010 to 15 Mar 2010

Is spending the time architecting your software important, or does making it up as you go along satisfy your needs? Be honest. (Suggested by Abhinav S)

OptionVotes% 
Cannot do without it36346.36
Important - but not critical34343.81
Of little importance577.28
Not important202.55



 
GeneralRe: Everything is designed Pin
The Man from U.N.C.L.E.11-Mar-10 9:07
The Man from U.N.C.L.E.11-Mar-10 9:07 
GeneralRe: Everything is architected [modified] Pin
Muhammad Gouda8-Mar-10 7:37
Muhammad Gouda8-Mar-10 7:37 
GeneralRe: Everything is architected Pin
Duncan Edwards Jones8-Mar-10 8:16
professionalDuncan Edwards Jones8-Mar-10 8:16 
GeneralRe: Everything is architected Pin
Old Nic8-Mar-10 21:40
Old Nic8-Mar-10 21:40 
GeneralRe: Everything is architected Pin
PIEBALDconsult9-Mar-10 4:29
mvePIEBALDconsult9-Mar-10 4:29 
GeneralDepends on the Client Pin
thatraja8-Mar-10 4:06
professionalthatraja8-Mar-10 4:06 
GeneralRe: Depends on the Client Pin
brightmohan8-Mar-10 13:43
brightmohan8-Mar-10 13:43 
GeneralRe: Depends on the Client Pin
RedSonja8-Mar-10 21:03
RedSonja8-Mar-10 21:03 
Disagree. Some of our customers don't think about requirements until we have delivered something. I even had one turn up with a PHOTOGRAPH of someone else's product and demand a cheaper version (we did deliver it and they are still happy with it). But really they do know roughly what they want, and if we don't want to have yet another endless project we have to document it first and get their signatures on it.

Though yes, as a rule, we know what they want and we know what we want to build, and it's building on things we have done before, so we could just bumble ahead like we used to do. But most documents can be created by copy and paste from the previous project, so it is possible to do one in a week, even if there's a TBD in places. We have specs for documents, and most are available in template form.

I personally like to write down what I want to do to get it clear in my head. Usually I can write the contents list of the design document and create the classes on the screen at the same time. We have tried out these clever systems for creating code from the document, but I find it a bit inflexible, because I might suddenly see that class A belongs over there and that class B is actually an instance of class C. The requirements from our sales dept are often incomplete and ambiguous, so there is a lot of fine tuning going on. Some colleagues keep all this in their heads, but I am not clever enough for that, I have to write it down.

Often we work on legacy software, and if the documents were written afterwards instead of in parallel, then they are usually a bit thin and we curse our ancestors.
------------------<;,><-------------------

GeneralChannel 9 video on the topic (link) Pin
Josh Fischer8-Mar-10 3:31
Josh Fischer8-Mar-10 3:31 
GeneralPhilosophically Not So Clear Cut Pin
W Balboos, GHB8-Mar-10 3:03
W Balboos, GHB8-Mar-10 3:03 
GeneralDepends on the size of the project, and how experienced the developer is. Pin
ZTransform7-Mar-10 22:54
ZTransform7-Mar-10 22:54 
GeneralRe: Depends on the size of the project, and how experienced the developer is. Pin
Josh Fischer8-Mar-10 3:29
Josh Fischer8-Mar-10 3:29 
GeneralRe: Depends on the size of the project, and how experienced the developer is. Pin
Don Driskell8-Mar-10 4:12
Don Driskell8-Mar-10 4:12 
GeneralA Tale of Two Mistakes PinPopular
peterchen7-Mar-10 21:24
peterchen7-Mar-10 21:24 
GeneralRe: A Tale of Two Mistakes Pin
myker8-Mar-10 3:25
myker8-Mar-10 3:25 
GeneralRe: A Tale of Two Mistakes Pin
peterchen10-Mar-10 8:10
peterchen10-Mar-10 8:10 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.