Acoplamento e Coesão #219
Open
Acoplamento e Coesão #219
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
O acoplamento determina o nivel de dependencias entre as classes do programa, desse modo desejamos diminuir ao maximo essa dependencia, obtendo entao um BAIXO acomplamento
A coesao se refere a definicao da responsabilidade de um metodo/classe/funcao, no caso eles devem realizar unicamente a tarefa na qual corresponde ao intuito de sua criação. ex: em uma função SomarNumeros(), nao se deve multiplicar ou dividir. Desse modo podemos obter uma ALTA coesão
Nesse sentido, realizei algumas alteraçoes no codigo com base nesses conceitos de boas praticas de POO, movendo a entrada de dados do usuario para o arquivo principal do programa, pois essa entrada nao compete a classe estacionamento