Re: How to specify complex code?

Path	csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From	"Rod Pemberton" <dont_use_email@xnohavenotit.cnm>
Newsgroups	comp.lang.forth
Subject	Re: How to specify complex code?
Date	Fri, 27 Dec 2013 01:07:34 -0500
Organization	Aioe.org NNTP Server
Lines	30
Message-ID	<op.w8qlywex5zc71u@localhost> (permalink)
References	<7619435e-495f-458c-a1cb-d878db85dac5@googlegroups.com> <bi2dvgFmeuU1@mid.individual.net> <9da38468-4d24-40f5-b0c4-94d753d66b6f@googlegroups.com> <bi3p7aF9i6uU1@mid.individual.net>
NNTP-Posting-Host	CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org
Mime-Version	1.0
Content-Type	text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding	7bit
X-Complaints-To	abuse@aioe.org
User-Agent	Opera Mail/12.16 (Linux)
X-Notice	Filtered by postfilter v. 0.8.2
Xref	csiph.com comp.lang.forth:27469

Show key headers only | View raw

On Thu, 26 Dec 2013 17:34:17 -0500, Paul E Bennett  
<Paul_E.Bennett@topmail.co.uk> wrote:

> [snip]
>
> That is why I always say the first Review you do is on the customer's
> requirements specification to ensure that it is:- Clear, Concise,
> Correct, Consistent, Confirmed and Testable. If it does not meet those
> criteria you need to get the ambiguities resolved before proceeding much
> further into the design.

With one exception, I agree.

It's obvious to me that what you labeled as the first review should
actually be the second review.  The first review should be to check
that the business's employees have made sure their spell checkers
have been enabled, since it's clear yours wasn't:

  compexity -> complexity
  ar -> are
  implemntation -> implementation
  powrful -> powerful

I think those are enough to say you failed to satisfy four of your
stated requirements: "Clear," "Correct," "Concise," and "Confirmed".

Yes?  Or, is there a problem with your 'e' and perhaps 'l' key?  ;-)

Rod Pemberton

Thread

how do forthers control compexity and make easy user interfaces? the_gavino_himself <visphatesjava@gmail.com> - 2013-12-25 21:54 -0800
  Re: how do forthers control compexity and make easy user interfaces? Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2013-12-26 10:16 +0000
    How to specify complex code? mhx@iae.nl - 2013-12-26 02:52 -0800
      Re: How to specify complex code? ForthFreak <forthfreak@gmail.com> - 2013-12-26 03:45 -0800
        Re: How to specify complex code? mhx@iae.nl - 2013-12-26 05:20 -0800
      Re: How to specify complex code? Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2013-12-26 22:34 +0000
        Re: How to specify complex code? "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-27 01:07 -0500
          Re: How to specify complex code? Mark Wills <markrobertwills@yahoo.co.uk> - 2013-12-27 02:20 -0800
          Re: How to specify complex code? Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2013-12-27 12:27 +0000
    Re: how do forthers control compexity and make easy user interfaces? Richard Owlett <rowlett@pcnetinc.com> - 2013-12-26 06:54 -0600
      Re: how do forthers control compexity and make easy user interfaces? Paul E Bennett <Paul_E.Bennett@topmail.co.uk> - 2013-12-26 22:37 +0000
    Re: how do forthers control compexity and make easy user interfaces? Spam@ControlQ.com - 2013-12-27 17:13 -0500
    Re: how do forthers control compexity and make easy user interfaces? the_gavino_himself <visphatesjava@gmail.com> - 2013-12-31 17:34 -0800
  Re: how do forthers control compexity and make easy user interfaces? Richard Owlett <rowlett@pcnetinc.com> - 2013-12-26 06:52 -0600
    Re: how do forthers control compexity and make easy user interfaces? the_gavino_himself <visphatesjava@gmail.com> - 2013-12-31 17:42 -0800

csiph-web