Skip to content

Milestones

List view

  • Implementing Interfaces and Polymorphism

    Using higher abstraction with interfaces and polymorphism.

    Overdue by 11 year(s)
    •
    Due by June 22, 2014
    •1/1 issues closed
    100% complete0 open1 closed

  • Unit testing

    Design and implement unit tests covering the entire project functionality. To ensure the project works correctly according to the requirements and behaves correctly in all possible use cases, design and implement unit tests that cover all use cases and the entire program logic. If needed, first redesign the program logic to make the code testable. Test the normal expected behavior (correct data) and possible expected failures (incorrect data). Put special attention to the border cases. The code coverage of the unit tests should be at least 80%. Use unit testing framework of your choice (e.g. Visual Studio Team Test, NUnit, MbUnit or other).

    Overdue by 11 year(s)
    •
    Due by June 22, 2014
    •2/2 issues closed
    100% complete0 open2 closed

  • Implementing at least 6 design patterns

    Structural patterns – implement at least 2 of the structural design patterns (adapter, aggregate, bridge, composite, decorator, extensibility, façade, etc…) Behavior patterns – implement at least 2 of the behavioral design patterns (chain of responsibility, command, interpreter, iterator, mediator, observer, etc…) Creational patterns – implement at least 2 of the creational design patterns (abstract factory, builder, factory method, singleton, prototype, etc…)

    Overdue by 11 year(s)
    •
    Due by June 22, 2014
    •1/1 issues closed
    100% complete0 open1 closed

  • DRY Implementation On the Original Source Code

    Don't Repeat Yourself - all appearances of a repeated code should be extracted in a new method or in any other possible way.

    Overdue by 12 year(s)
    •
    Due by May 31, 2014
    •3/3 issues closed
    100% complete0 open3 closed

  • Renaming Bad Variables' Names In Original Code

    All variables in the original source code that use improper names - not descriptive, misleading and so on, should be renamed.

    Overdue by 12 year(s)
    •
    Due by May 28, 2014
    •6/6 issues closed
    100% complete0 open6 closed