This READ.md template was written based on this repository.

⏪ Dependency Inversion ⏪

Developed by 💻:

• Fernando Schettini.
• Antonio Horácio Magalhães.
• Orlando Mota Pires.

Special thanks to 🥰:

• Edson Mota - Our supervising teacher, your experience and knowledge have been invaluable to our progress.

About 🤔:

This repository showcases a C# project developed in Visual Studio that addresses a specific code smell in a abstract example. By applying the dependency inversion principle, the code was refactored to enhance flexibility and maintainability, improving class relationships.

The application of the dependency inversion principle brings several advantages to the codebase. By inverting dependencies and promoting loose coupling, it enables easier maintenance and scalability. This approach fosters modularity and code reusability by relying on abstractions rather than concrete implementations. Additionally, it improves testability by facilitating the isolation of dependencies during testing. This factor further enhances flexibility and scalability as it allows for the addition of new functionalities without modifying existing code. Moreover, it centralizes dependency management, contributing to improved code maintainability.

This repository includes the source code and documentation, serving as an educational resource for understanding and implementing effective coding practices.

Resourses 🧑‍🔬:

• Use the available classes to create elements and simulate and establish relationships between them, while each one performs its function.

How to run it 🏃:

First, clone this repository. After that, open the project with Visual Studio and execute Program.cs.

Code Feedback 🎬:

Figure 1 - Screens from code feedback.

Logic Model 🧮:

Here's the logic model that represents how the code works with their classes.

Figure 2 - Logic Model.

UML‍ 💬:

Here's the UML that represents how the code works with their classes.

Figure 3 - Code UML.

Development Process ⚙️:

The project was developed in a few hours during a meeting, without a formal methodology or strategy. Team members brainstormed ideas, discussed requirements, and collaboratively implemented functionalities. Flexibility and quick decision-making were prioritized, but there may be challenges in terms of organization and scalability without a defined methodology.

Tools Used 🛠️:

• Visual Studio.
• Miro.

How to contribute 🫂:

Feel free to create a new branch, fork the project, create a new Issue or make a pull request contact one of us to develop at code.

Licence 📜:

Apache V2

References 📙:

[1] MOTA, Edson. Code Smells. 2022. Slides. SENAI CIMATEC, Salvador.