From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,de98d0782a843079
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-05-13 03:56:01 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: maa@liacc.up.pt (=?ISO-8859-1?Q?M=E1rio_Amado_Alves?=)
Newsgroups: comp.lang.ada
Subject: Re: Problem space and solution space
Date: 13 May 2003 03:56:00 -0700
Organization: http://groups.google.com/
Message-ID: <4a4de33a.0305130256.658ef102@posting.google.com>
References: <mailman.1.1052790237.11797.comp.lang.ada@ada.eu.org>
NNTP-Posting-Host: 193.137.36.168
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1052823361 6059 127.0.0.1 (13 May 2003 10:56:01
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 13 May 2003 10:56:01 GMT
Xref: archiver1.google.com comp.lang.ada:37269
Date: 2003-05-13T10:56:01+00:00
List-Id: <comp.lang.ada>

<<parts of "solution space" may be viewed as a "problem space" of
software development process>> (Alexander)

Indeed. A typical situation occurs in the chain
  1 requirements specification
  2 design
  3 program
where 1 is a problem to the designer, 2 is a solution to 1, 2 is a
problem to the programmer, and 3 is a solution to 2 (and transitively
to 1).

--Marius