• Starting point
  • text is in C#
  • all UT are green
  • the program behaves as expected (intermediate approval test)
• Data Layer
  • responsibility of this layer is to represent boundaries of the movement rectangle and balls
  • balls representation are independent and self-contained (no timer required)
  • balls implementation uses concurrent programming
• Logic Layer
  • responsibility of this layer is to manage movement rectangle boundaries and balls interaction (collisions)
  • prove that the protection of data integration is implemented
  • Logic uses only the abstract Data layer API
• Presentation Layer (MVVM)
  • responsibility of this layer is to manage the graphical user interface (GUI)
  • user => GUI interoperability must be implemented using interactive programming only
  • GUI => the user interoperability must be implemented using reactive programming only (timer is not allowed)
  • interoperability of the GUI and underlying layers must be synchronized
• Fulfill functional requirements of the task
• Testing
  • Unit Test - layers are tested independently using dependency injection (additional framework is not required)
  • Mock may be used for testing purposes (expected but not required)

Create a repository checklist

• the task provides required feedback and has been submitted (needs grading)
• the ability to clone the repository to the teacher's computer
• there is README.md formatted as expected
• README.md contains required information
• build succeeded
• all UTs are green

• Starting point
  • text is in C#
  • all UT are green
  • the program behaves as expected (intermediate approval test)
• Data Layer
  • responsibility of this layer is
    • to represent boundaries of the movement rectangle if necessary
    • implement balls behavior as self-contained independent entities
    • save diagnostic data to a file
  • protect balls velocity against any influence from other balls and the environmental behavior
  • balls implementation uses concurrent programming
  • prove that the diagnostic logging doesn't have an impact on the behavior of the balls
• Logic Layer
  • responsibility of this layer is to manage movement rectangle boundaries and balls interaction (collisions)
  • prove that the protection of data (balls position on the abstract table during collisions detection) integration is implemented
  • Logic uses only the abstract Data layer API
• Presentation Layer (MVVM)
  • responsibility of this layer is to manage the graphical user interface (GUI)
  • user => GUI interoperability must be implemented using interactive programming only
  • GUI => the user interoperability must be implemented using reactive programming only (timer is not allowed)
  • interoperability of the GUI and underlying layers must be synchronized
  • prove that the protection of data (balls position on the screen) integration is implemented
• Testing
  • Unit Test - layers are tested independently using dependency injection (additional framework is not required)
  • Mock may be used for testing purposes (expected but not required)

• text is in C#
• build succeeded
• all UT are green
• Data layer is clearly stated using language terms only (no database, no file)
• Data API is clearly stated
• Data API is abstract
• Logic layer is clearly stated using language terms only
• Logic API is clearly stated
• Logic uses only the abstract Data layer API
• Presentation layer is clearly stated using language terms only
• Presentation uses only the abstract Logic layer API
• MVVM and XAMLare applied to implement GUI
• reactive and interactive user interaction for user (operator) communication
• reactive and interactive programming is used for the communication of layers
• Presentation - object model representing process data
• Fulfill functional requirements of the task
• Unit Test - layers are tested independently using abstract API
• Dependency injection (additional framework is not required)
• Mock is used for testing purposes (expected but not required)