Skip to content

Design Meeting Minutes

Jump to bottom
Preet Patel edited this page Aug 26, 2019 · 7 revisions

Meeting 1

Date: 24/07/2019
Time: 3:00 PM - 5:30 PM
Topic: Planning Project 1

Members attended: Everyone

Basic summary:

  1. Created code practices
  2. Created git practices
  3. Created general team practices

Programming

  1. Please comment your code. Please.
  2. Pascal cases for class names, Camel cases for variable + methods
  3. Do _camelCase field names. Having this.FIELD implementation is optional but not required...

Github rules:

  1. Commit messages address/ includes the relevant issues number(s)
  2. Do not merge directly - use pull requests for review. Reviewer please write a comment if the pull request is not approved and return it back to the original author. Reasons to not approve the request include (Merge Conflict, Not Following Conventions, Redundant Code, etc...)
  3. User stories is a subset of issues
  4. Use branches please (remember to prune your branches)
  5. Do consistent null checks (Use GuardNull Extension Methods)
  6. Asserts are good - regular code to test (Leave Asserts for production code)

What will we use?

  1. Java + JavaFXML (scenebuilder)
  2. MVC Model
  3. Preet's build tools

Minutes Taken By: Eric

Meeting 2

Date: 25/07/2019
Time: 10:00 AM - 12:00 PM
Topic: Planning Project 2

Members attended: Harman, Jainal, Gargi, Salma, Eric

Basic Summary of the meetings:

  1. WBS was defined on the whiteboard and is now being electronically created by @Jainal
  2. Based on the WBS @Jainal, @Salma, @Gargi, and @Harman created the essential items to be displayed on the flow graph
  3. The Network Flow Graph is electronically being created by @Salma

Important Notes for the next meeting and dates:

  1. Next meeting has-beens scheduled for Friday 26th 15:00 - 17:00 at 55 Symonds Street
  2. No prior work has to be done apart from what has been allocated
  3. Main Goal of the next meeting is to finish the Gantt Chart, decide upon on a team leader, and start the work allocation in order to stay up to date with the plan in action.
  4. An important question to consider that came up during the meeting was to consider how the GUI will have live updates with the search in progress and can have interactive elements such as zoom or focus on certain aspects.
  5. Another important question to consider is when the requirements says to contrast both the algorithm running in parrallelism vs not does the GUI run both at the same time, or one and then the other? This then relates to the run time (i.e. What if one takes 30 min? Do we just disable the secondary portion of the GUI?)

Minutes Taken By: Harman

Meeting 3

Date: 26/07/2019
Time: 3:00 PM - 5:00 PM
Topic: Planning Project 3

Members attended: Everyone

Basic Summary:

  1. Spreading "sub-tasks" of WBS into appropriate sections
  2. Adding more tasks and re-imagining tasks of future project operation
  3. Undergo more design decisions - specially implementation of GUI, multi-threading
  4. Completing WBS & Network diagram

Notes:

  1. Make sure to not break waterfall process - debugging of single features allowed
  2. Make sure tasks are consistent, makes sense and minimal tasks
  3. Establish Essential external java libraries for algorithm implementation DIFFERENT to GUI implementation libraries

Task Allocation by Next Meeting (28/07/2019)

  1. Jainal: Help @Harman with the WBS write up
  2. Salma: Finish Flow-Chart Color and grouping with @Gargi
  3. Harman: Create the Latex Document (with the essential PDF libraries) and share it with the team. Write up the introduction and help @Jainal write up the justification for the WBS.
  4. Eric: Write up of the Network Graph with @Preet
  5. Preet: Write up of the Network Graph with @Eric
  6. Gargi: Finish Flow-Chart Color and grouping with @Salma

Overleaf Report Link: https://www.overleaf.com/3271994454qwjzyqkjgrgv

Minutes Taken By: Eric

Meeting 4

Date: 28/07/2019
Time: 12:00 PM +
Topic: Planning Project 4

Members attended: Everyone

Basic Summary:

  1. Decisions made from design decisions of plans in WBS and network diagram including rewording, numbering, introducing GUI test procedure, changed dependencies in parallel.
  2. Developing Gantt chart - finishing Gantt chart 1.3
  3. Developing report + proof reading

Notes:

  1. Section numbering required for gantt chart
  2. Tasks in plan are now using appropriate numbering according to main-tasks + each waterfall phase is numbered

Task Allocation by Next Meeting (29/07/2019)

  1. Jainal: Proof-read help @Harman with Latex formatting
  2. Salma: Proof-read and try making the report more concise
  3. Harman: Start to port the whole report to Latex and proofread and make the report more concise
  4. Eric: Proofread and make the report concise
  5. Preet: Write up of the Gantt Chart
  6. Gargi: Help @Preet with the Gantt Chart Write up

Minutes Taken By: Eric + Jainal

Meeting 5

Date: 29/07/2019
Time: 13:00
Topic: Proof Reading and A1 submission

Members attended: Everyone

Basic Summary:

  1. The team met together to proof-read and double check the final report with the document
  2. Some changes were made to the Work Breakdown Structure, Network Diagram, and the Gantt Chart which were then updated in the document.

Next meeting date has still not been organized, this will be done soon and messaged to the group members via the Group Chat in Messenger

Minutes Taken By: Harman

Meeting 6

Date: 31/07/2019
Time: 5:20 PM
Topic: Design Process 1

Members attended: Everyone

Basic Summary:

  1. Finding inspiration for GUI graphical designs
  2. Allocating tasks (ideally design research) to sub-teams of our team to do algorithms (Salma, Gargi, Eric, Jainal) or multithreading/parallelisation (Preet, Harman)
  3. Decisions to look @ DF-BnB*, A*, AO algorithms (AO is quite hard to understand)

Meeting 7

Date: 01/08/2019
Time: 3:00 PM
Topic: Design Process 2

Members attended: Harman, Jainal, Gargi, Salma, Eric

Basic Summary:

  1. Researching AO algorithm implementation
  2. Decisions on other possible algorithms for scheduling
  3. Discussion on implementation - viability of algorithms and techniques

Meeting 8

Date: 02/08/2019
Time: 3:30 PM
Topic: Design Process 3

Members attended: Harman, Jainal, Salma, Eric

Basic Summary:

  1. Researching IDBnb properties
  2. Researching IDA* properties: https://researchspace.auckland.ac.nz/bitstream/handle/2292/27803/whole.pdf?sequence=2https%3A%2F%2Fresearchspace.auckland.ac.nz%2Fbitstream%2Fhandle%2F2292%2F27803%2Fwhole.pdf%3Fsequence
  3. Contacting researchers for further information on scheduling search algorithm
  4. Parallelisation research
  5. Software architecture setup (JUnit, JavaFX, Pyjama) libraries
  6. IMPORTANT: Decided to implement IDA* (+ designing possible optimization techniques)

Task Allocation by Next Meeting (05/08/2019)

  1. Jainal: Work with @Salma and present the current progress, create UML
  2. Salma: Work with @Jainal and present the current progress
  3. Harman: Work with @Eric and present the plan, create UML
  4. Eric: Work with @Harman and present the plan
  5. Preet: Work with @Gargi and present current troubles
  6. Gargi: Work with @Preet and present the current troubles

Please ensure that you are only working on the GOOGLE PRESENTATION and that we all don't have our own slides.

Minutes Taken By: Eric

Task Allocation By: Harman

Meeting 9

Date: 05/08/2019
Time: 2:00 PM - 6:00 PM
Topic: Project structure setup and IO implementation

Members attended: Everyone

Basic Summary:

  1. Implemented the UML class structure we designed.
  2. Started to implement IO Reading and Writing functionality

Minutes Taken By: Salma

Task Allocation By: Harman

Meeting 10

Date: 07/08/2019
Time: 2:00 PM - 6:00 PM
Topic: IO Validity handling and starting algorithm implementation

Members attended: Everyone

Basic Summary:

  1. Added a variety of validity checks for the input and output files. Had to make exceptions
  2. Started implementing the algorithm infrastructure ie Factory pattern applied (class AlgorithmBuilder)

Minutes Taken By: Salma

Task Allocation By: Harman

Meeting 11

Date: 10/08/2019
Time: 10:00 AM - 4:30 PM
Topic: Finalizing Milestone 1 Submission

Members attended: Everyone

Basic Summary:

  1. Commented EVERYTHING - classes, methods, in-line
  2. Unit test cases written for IO
  3. Final tweaks and locking of the branch
  4. Fixed output IO bug where output file is written w/o input

Minutes Taken By: Salma

Task Allocation By: Harman

Meeting 12

Date: 16/08/2019
Time: 11:30 AM - 8:00 PM
Topic: The birth of the GUI and the growing up of the Algorithm

Basic Summary:

  1. [Harman, Eric] - Went over UI sketches made in the design phase and thought about the valuable info we now know from implementing the algorithm. For example, decided to add branches pruned stat.
  2. [Salma, Gargi, Jainal] - Made leaps and bounds on IDA* - pair programming baby!
  3. [Preet] - Started working on parallelising the IDA* algorithm with explanations of the algorithm from Gargi

Minutes Taken By: Salma

Task Allocation By: Harman

Meeting 13

Date: 21/08/2019
Time: 11:00 AM - 2:00 PM
Topic: The thick of parallelisation and refining the GUI

Basic Summary:

  1. Parallelised IDA* has been implemented by Gargi and Preet, now debugging it. Assigned Salma to help debugging.
  2. Extreme makeover GUI edition - ie further styling discussed and assigned.

Minutes Taken By: Salma

Task Allocation By: Harman

Meeting 14

Date: 20/08/2019
Time: 3:00 PM - 4:30 PM
Topic: Validation Phase

Basic Summary:

  1. Short meeting with Salma, Gargi, Jainal to talk about approach to verification, validation and testification.
  2. Decided to mirror the project structure for test classes, Boundary Value Analysis test cases for file IO tests, and optimal schedule checking tasks for our range or algorithms and input dot files
  3. Salma assigned to implement

Minutes Taken By: Salma

Task Allocation By: Harman

Meeting 15

Date: 24/08/2019
Time: 3:00 PM - 6:00 PM
Topic: Finalising the Milestone 2 Submission

Basic Summary:

  1. Final testing for bugs and assigning bug fixes for minor GUI issues (Harman, Eric)
  2. Decided to use BBA* algorithm instead of IDA* becuase IDA* parallelised was failing for some cases
  3. Documentation, commenting and clean-up of code assigned
  4. Decided to refactor the long MainController class (Eric)
  5. Logo graphics for branding created by Preet

Minutes Taken By: Salma

Task Allocation By: Harman

Clone this wiki locally