|
Jobs
Encapsulate: Better--COMMENT PLEASE!
Modifications Nov. 5 in italics, mostly Main = Wikoff Big encasing loop: Play again: Y/N Ask if 2 person, or computer/person;
Has sufficient space available for global arrays control flow., change player. Initializing Globals (preloaded arrays, copy to working array) = Thomas:
(Proc: Output board (From where/how?) = Stacey) Proc: User's move Call Output board Solicit move, check validity, repeat. Pass LastPipe (See ToResolve), and change Pipes. Jamie-Leigh Proc: Computer move (find a valid move, preferably smart, pass it back (See ToResolve) Bailey Proc: from LastPipe: = Brandon (Pipes to Squares) From Pipes to Squares, Mark new pipe in, send pair(?) of squares affected. (See ToResolve) Proc(s): 1 or more: Check if new square, send newsquare/not, check if done, tally win Dayton (Who's in charge of labeling squares?dayton (See ToResolve) Output gets from here.)
Algorithms: From horiz/vert pipes labeling, to Squares sides, is pretty clean? (Brandon) . |
Sign in to add a comment
I'd say we need someone in charge of the main loop, someone in charge of populating the data structures, someone in charge of output, someone in charge of input (and input validation), someone in charge of updating the data structures, someone in charge of seeing who's move it is (or if the game's over). That's 7 major jobs that I can think of. Since the global variables are used by everyone, I don't think it makes sense to assign a person to "oversee" a global variable. Rather, I think we should document the nature of our globals together as a class.