Week 7: Programming Script Hierachy

Earlier this week I have been working with Daniel T and Pat, the other programmers,  in order to design a system under which to organise our programming.

Some individual programmers may prefer to work ad hoc, but when there's more than one person working with a code repository, certain design considerations need to be made.

What needs to happen (from a leadership perspective):

• Code must be well documented.
• Functions must be implemented according to a specification.
• Class relationships and hierachies must be adhered to.

Having established these expectations with the other programmers, work can begin on the code design. Following is a rough draft of a script heirachy that I worked out as an example to show Pat and Dan:

 We'll refine and expand on this as a team, then I'll define some specification documents and upload them to our wiki for reference.