1. TEAM LOVELACE GROUP FORMATION PROJECT DESIGN PRESENTATION

2. OBJECTIVE Our project is designed to take a large group of people and divided them into teams based on  Availability  Skills  Letter Grade  Gender

3. MODULAR LAYOUT Driver FormulasRandomizer AVL Tree Input file Output file

4. DRIVER Main Module : - Receives input file and name of output file. - Manages data between it and the AVL tree. - Outputs the calculated groups to the output file. - Signature: team-creator - team-creator is the function the user will call to initiate the program.

5. AVL - TREE Data Structure : - AVL-Tree ( AVL-Tree) - Contains data for the Randomizer module and the Formulas module -Signature: switch-members-from-two-teams - Signature contains code which switches members between two teams

6. FORMULAS -Contains functions which are used to calculate the best group combinations. -Functions: -Gender -Grades -Schedule -Skills -Exception -Signature: calculate-groups -Takes the AVL tree of groups and calculates their score

7. RANDOMIZER -Creates the initial random teams - Picks random members form teams to switch - Contains a random number generator, a linear congruential generator -Signature: pick-initial-group, pick-non-worst-group-to-switch-with

8. INPUT FILES

10. OUTPUT FILES Team Set Criteria: Criteria i (w i ) Suggested Team Set: Team i:Team member i | Common time availability E.g. Team Set Criteria: Grade (0.2) 2 Skill sets (0.4): programming skill (0.5), team interaction skill (0.5) Time availability (0.2) Gender (0.2) Suggested Team Set: Team 1:1 Calvin Nelms, 3 Matt Rainwater | W 7:00 – 8:30 pm Team 2: 2 Ashley Nanni, 4 Nha Hoang | T 1:30 – 2:15 pm, R 5:00 – 5:45 pm

11. PROBE ESTIMATE - Driver I/O: 290 lines Calc: 439 lines Total = 729 lines - Randomizer I/O: 0 lines Calc: 298 lines Total = 298 lines - AVL Tree I/O: 0 lines Calc: 175 lines Total = 175 lines - Formulas I/O: 0 lines Calc: 357 lines Total = 357 lines TOTAL LINES OF CODE = 1559

12. PROJECTED SCHEDULE Jan 31 Feb 7 Feb 14 Feb 21 Feb 28 Mar 6 Mar 13 Mar 20 Mar 27 Apr 3 Apr 10 Apr 17 Apr 24 May 1 Design Code Code Review Testing Re- Design Re- Test Final Design