The document discusses principles for maintainable software design, specifically advocating for loose coupling and modularity. It notes that in reality, code is often not well modularized and coupled, as seen in the common practice of putting many responsibilities into view controllers. Properly applying principles like loose coupling and decentralization leads to better maintainability and quality according to defined criteria.

1. Arif Akbarul Huda
Coding | Writing | Sharing
2013-now QISCUS & Univ. Amikom Yogykarta
Twitter : @omayib
Medium : www.medium.com/@omayib
The P.O.P implementation
Modular is Better

2. Functionality
Reliability
Usability Efficiency
Maintainability
0
5
10
The High Quality Software Criteria
(ISO 9126-1 software quality model)
*i was ignore the Portability factor

3. Maintainability
“Maintainability is impacted by code
readability or complexity as well as
modularization” ..
“Also the ability to verify (or test) a
system, i.e. testability, is one of the
subcharacteristics of maintainability. “

4. 5 Principles
to meet maintainability criteria

5. Loose coupled is better

6. The Reality

7. With a simple case

8. Reality
Inside a UIViewController …
●
Managing data from local remote
●
Managing data from local cache
●
Managing TableView and its DataSource
●
Managing UIViewController‘s state
●
Managing progressViewHUD‘s state
●
Managing other...

9. Reality
you are breakfest with a spagetthi code

10. View
Controller
Model
XxProgressHUD.show()
XxProgressHUD.hide()XxProgressHUD.show()
Decentralized :
A Bad Practice

13. https://github.com/omayib/ModularIsBetter