Re: Test first as specification
- From: ggroups@xxxxxxxxxxx
- Date: 8 Aug 2005 07:00:51 -0700
Laurent Bossavit wrote:
>> Late last yr I proposed the game of Go, where I would write SPEC
>> (using mathematical techniques) for the game, and an XP bod would write
>> TEST as "customer" tests. The premise being that what was specified/
>> omitted/incorrect using either approach could be scrutinised. That one
>> soon went quiet.
> Let's start again... We ended up with the following candidate
> requirements (and a critique of them from me, which never got a
> response) :
> ) Provide a 19x19 board with the ability for two players to exchange
> moves
> 2) Remove captured groups/stones automatically
> 3) Implement end-of-game rule (3 consecutive passes)
> 4) Implement the Ko rule
> 5) Allow default komi editable by player before a game (not during)
> 6) Support setting number of handicap stones
> 7) Support 13x13 and 9x9 board sizes (adjust max handicap accordingly)
> 8) Score the game at the end
> 9) Save game to file (SGF format?)
> 10) Replay game loaded from file (SGF format?)
> 11) Supply estimate of score while game is in progress
Yes. I suggest requirements (REQ) = 1-8, 11.
So we have :
- You to write (in whatever form you see fit) , all the "customer"
tests
you need in order to verify that any submitted impl of the game of
Go conforms to REQ.
- Me to write a spec (in whatever form I see fit) that captures REQ
sufficiently well enough to enable an impl to be devised by a
developer.
1. I suggest deliverables grouped as follows :
1/2/3/4/8, 5/6/7, 11
This way we can see the artifact evolution thru the work activity.
2. We need the same requirements sources (online game rules etc) .
Info not available in those sources is not usable.
3. We need an independent source to hold the deliverables until we
have both finished. I do not want to be unfairly advantaged by seeing
your stuff thus potentially bettering what I might otherwise devise.
It will be interesting to see if I can define the whole thing so a
developer merely has to cut and paste my spec as Design By Contract
artifacts.
Regards,
Steven Perryman
.
- Follow-Ups:
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- References:
- Re: Test first as specification
- From: Roger L. Cauvin
- Re: Test first as specification
- From: paul campbell
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- From: Daniel Parker
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- From: Daniel Parker
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- From: Daniel Parker
- Re: Test first as specification
- From: Robert C . Martin
- Re: Test first as specification
- From: paul campbell
- Re: Test first as specification
- From: Robert C . Martin
- Re: Test first as specification
- From: Lurker
- Re: Test first as specification
- From: ggroups
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- Prev by Date: Re: Test first as specification
- Next by Date: Re: Test first as specification
- Previous by thread: Re: Test first as specification
- Next by thread: Re: Test first as specification
- Index(es):
Relevant Pages
|