Skip to content

Latest commit

 

History

History
54 lines (42 loc) · 2.05 KB

README.md

File metadata and controls

54 lines (42 loc) · 2.05 KB

Lauch Interceptor Program

By Ayub Atif, Isac Arvidsson, Eva Despinoy, Daniel Helle

Description of the program

As a part of a hypothetical anti-ballistic system, the decide() function generates a boolean signal which determines wether an interceptor should be launched based upon input radar tracking information.

The boolean signal is based on the boolean outputs of 15 functions.

How to use the program?

Make a new object of class Decide(). Set all the parameters of the class as wished. Then run the decide() function, which will return a boolean indicating if the interceptor should be launched.

Statement of contribution

Ayub Atif

  • Function LIC3() with corresponding tests
  • Function LIC7() with corresponding tests
  • Function LIC11() with corresponding tests
  • Function LIC13() with corresponding tests
  • Function LIC14() with corresponding tests
  • Function createFUV() with corresponding tests

Isac Arvidsson

  • Function LIC2() with corresponding tests
  • Function LIC6() with corresponding tests
  • Function LIC7() with corresponding tests
  • Worked on setting up travis, set up yml-file and debugged how the tests were performed
  • "Parprogrammering" on the PUM with corresponding tests with Daniel
  • Created launch and the decide methods and corresponding test with Ayub
  • Set up the first header file

Eva Despinoy

  • Function LIC1() with corresponding tests
  • Function LIC5() with corresponding tests
  • Function LIC9() with corresponding tests
  • Refactored code to make it more clean and coherent
  • Wrote first README.md draft
  • Worked on making the TestDecide.java file compile with Travis & wrote first test

Daniel Helle

  • Function LIC0() with corresponding tests
  • Function LIC4() with corresponding tests
  • Function LIC8() with corresponding tests
  • Function LIC8() with corresponding tests

Something(s) valuable and remarkable that we are proud of

  • Used Travis and Gradle
  • Worked with pair programming
  • Linked all pull requests with issues
  • Tried to avoid code duplication and to write clean code