[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: UMLish modellers?

Subject: Re: UMLish modellers?
From: Andreas Monitzer <email@hidden>
Date: Sun, 9 Sep 2001 02:20:41 +0200

On Sunday, September 9, 2001, at 02:08 , Erik M. Buck wrote:

If there is no rational specification for a piece of software, there is no
way to verify that the software meets the specification at the end of the
project. What is the point of designing something that is not specified ?

From my experience with specifications at school:

What is the point of specifying something when that's only possible by developing the system?

We had to write a specification for our one-year-project (hardware/software combined). The teachers required us to specify EVERYTHING, for instance the temperatures our device will work with. That meant we had to know what components we'll use (what ICs, what capacitances etc). Which lead to designing the whole system beforehand (in two weeks).
There's no difference to software design, it's just not as obvious.

How is a design evaluated without a specification to compare? Specifying
non-trivial software a-priori is very hard!

I'd call it usually impossible. At least without writing it first.

andy
--
Description forthcoming.

Follow-Ups:
- Re: UMLish modellers?
  - From: Georg Tuparev <email@hidden>

References:
	>Re: UMLish modellers? (From: "Erik M. Buck" <email@hidden>)

Prev by Date: Re: UMLish modellers?
Next by Date: Re: Mac OS X 10.1 File Name Extension Guidelines
Previous by thread: Re: UMLish modellers?
Next by thread: Re: UMLish modellers?
Index(es):
- Date
- Thread

Home