pstrachota / concurrent_programming

Ellastic ball collision - MVVM, WPF project for concurrent programming class in TUL.

Hello world👋, I'm Piotr

IT student from Poland

👨🏻‍🎓 About Me:

I am currently in the VI semester of Applied Computer Science in Lodz University of Technology (TUL).

My university programming adventure started with C++ and my first bigger project sums up gained knowledge (mainly about object oriented paradigm) in library system application. The next step was to learn about concurrent programming and layered architecture in C#.

Another great achievement was learning the basics of building web applications backend in Java and Typescript, using Spring, Jakarta EE and Nest.js.

During my journey, I also learned about relational and non-relational databases, cryptography, linux operation system, basics of artificial intelligence in Python and a solid dose of front-end knowledge - also with mobile apps.

💻 Tech Stack:

📜 Cerfificates

Name	Issued By	Date Of Obtaining
MS SQL Server	CRC Program	06.2022
Optimization of SQL queries in practice	LSI Software	04.2022

📊 GitHub Stats:

concurrent_programming's Issues

Repository checklist for tutor

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

Repository checklist for third task

• Starting point
• 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 parallel programming if applicable (depends on the run time platform)
• 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
• Testing
• Unit Test - layers are tested independently using dependency injection (additional framework is not required)
• Mock may be used for testing purpose (expected but not required)

Repository checklist [tutor] for third task

• Starting point
  • 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 environment behavior
  • balls implementation uses parallel programming if applicable (depends on the run time platform)
  • prove that the diagnostic logging doesn't have impact on the balls behavior
• 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 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 purpose (expected but not required)

Repository checklist [tutor] for third task

• Starting point
• 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 parallel programming if applicable (depends on the run time platform)
• 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
• Testing
• Unit Test - layers are tested independently using dependency injection (additional framework is not required)
• Mock may be used for testing purpose (expected but not required)

Repository checklist

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

Repository checklist [tutor] for second task

• text is in C# and use .NET
• build succeeded
• all UT are green
• Data layer is clearly stated using language terms only (no database of file access is required)
• 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
• mvvm and xaml is applied to implement GUI
• reactive and interactive user interaction for user (operator) communication
• reactive and interactive programming is used for layers communication
• Object model representing process data
• 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)

Repository checklist for second task

• text is in C# and use .NET
• build succeeded
• all UT are green
• Data layer is clearly stated using language terms only (no database of file access is required)
• 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
• mvvm and xaml is applied to implement GUI
• reactive and interactive user interaction for user (operator) communication
• reactive and interactive programming is used for layers communication
• Object model representing process data
• 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)

Repository checklist for third task

• Starting point
  • 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 environment behavior
  • balls implementation uses parallel programming if applicable (depends on the run time platform)
  • prove that the diagnostic logging doesn't have impact on the balls behavior
• 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 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 purpose (expected but not required)