Re: What is analysis?

From: JOG <>
Date: Mon, 3 Dec 2007 13:51:09 -0800 (PST)
Message-ID: <>

On Dec 3, 12:23 am, "David Cressey" <> wrote:
> I had thought that all software engineers were familiar with what analysis
> is, and how it differs from design. But perhaps not. There have been a
> couple of basic questions in this newsgroup, from people that seem like
> serious professionals, that suggest that analysis itself is widely
> misunderstood.
> Given the number of large projects that have begun with inadequate analysis,
> and have ended in disaster over the last decade, perhaps there's a
> widespread ignorance of the fundamentals of analysis.
> I'm hesitant to offer a definition off the top of my head, because it will
> surely be torn apart by the usual gang of vultures.

What!? Good grief Man. Its a colony. A _colony_ of vultures for pete's sake. Please do some research before posting. Sighs, plonks, etc. Jim.

<big grin/>

> In the meantime, I'd
> like to hear from everybody with a degree in software engineering. Did you
> ever take a course on analysis? Or, alternatively, did you ever take a
> course on methodologies that put a strong emphasis on analysis?
> Have any of you ever undertaken a large scale database design project
> without doing any formal analysis, or just by writing down the requirements
> in a doc? What happened after that? I'm not talking about a little
> database with 20 or 30 columns. I'm talking a database with upwards of 300
> columns and a good number of tables.
Received on Mon Dec 03 2007 - 22:51:09 CET

Original text of this message