Analisis kopling objek dari penerapan Dependency Injection dan Model-View-Presenter pada aplikasi Android
Total View This Week5
Total View This Week5
Institusion
STMIK Bumi Gora
Author
Apriliansyah, .
Subject
T Technology (General)
Datestamp
2021-09-10 08:11:36
Abstract :
Coupling is one indicator of the quality of a structured and oriented software design. Tight coupling is an early indication that an object-oriented software design is difficult to maintain. The first step in controlling the clutch properly is to apply the design pattern. However, experimental evidence of the implementation of design patterns does not guarantee that the code base on software apart from design smell has a negative impact on the maintenance aspect. There is a coupling problem between the android context object and the model object. Implementing Model-View-Presenter can help pass android context object references to models. However, the code written becomes complex and redundant. As of May 2021, android announced the use of hilt as standard in dependency injection automation, this also resolves the coupling issue between android context objects and model objects. This study aims to further analyze object coupling from the application of dependency injection manually and automatically using hilt on android applications. The results of the study concluded that there was an increase in the number of class couplings on the view and reducing the number of class couplings on the presenter. In addition, the benefits of implementing dependency injection automatically reduce class responsibilities on presenter and eliminate design smell. However, implementing dependency injection automatically affects the Model-View-Presenter pattern that uses dependency injection manually in the context of using the Java programming language.
Coupling is one indicator of the quality of a structured and oriented software design. Tight coupling is an early indication that an object-oriented software design is difficult to maintain. The first step in controlling the clutch properly is to apply the design pattern. However, experimental evidence of the implementation of design patterns does not guarantee that the code base on software apart from design smell has a negative impact on the maintenance aspect. There is a coupling problem between the android context object and the model object. Implementing Model-View-Presenter can help pass android context object references to models. However, the code written becomes complex and redundant. As of May 2021, android announced the use of hilt as standard in dependency injection automation, this also resolves the coupling issue between android context objects and model objects. This study aims to further analyze object coupling from the application of dependency injection manually and automatically using hilt on android applications. The results of the study concluded that there was an increase in the number of class couplings on the view and reducing the number of class couplings on the presenter. In addition, the benefits of implementing dependency injection automatically reduce class responsibilities on presenter and eliminate design smell. However, implementing dependency injection automatically affects the Model-View-Presenter pattern that uses dependency injection manually in the context of using the Java programming language.
Download
book
BibTex
Latex, Jabref
cloud_download
Original Resource
url resource Institution
