The document discusses making software soft by refactoring it to better cope with changes. It advocates discovering the underlying "Tao" or domain model of the system through refactoring. The key is refactoring the software to reveal the natural relationships and interactions within the domain. This makes the software structure flexible and open to changes by decomposing it into loosely coupled components aligned with the domain. The heart of making software soft is finding its inherent design through refactoring, which allows the software to naturally follow and adapt to changes over time.

1. Make Software Soft
-- Learn from A Refactoring Case
赵喜鸿

2. Who am I?
From Alcatel-Lucent
Software developer
A fervent advocate of Agile methodologies
11 years' experience in software development
and team management
Now, refactoring a legacy telecom equipment
system.

3. Why call it “Software”?

4. Soft
• yielding readily to touch or pressure; easily
penetrated, divided, or changed in shape; not hard
or stiff
• Easily molded, cut, or worked.
• Easy to influence or impose upon
Easy to change

5. Is Software Soft?

6. Is Software Soft?
http://www.codeproject.com/KB/books/SoftwareProjectSecrets1.aspx

7. Is Software Soft?
http://gtwebmarque.com/wikis/gtwm/index.php/Project_Failure

9. “Reasons”
and “Solutions”

11. Contract

13. Insufficient Upfront Design

14. More Upfront Design

15. Design Reality

17. A Real Refactoring Case

18. Understand Problem Domain

19. Epon Management

20. Run On NT Board On LT Board
Is it soft?

21. Make It Softer

22. Update
op state
Save to
database
Configuration
Config to
hardware
Changed

23. Observer Pattern

24. Listener
“state”
Listener
“persist”
Configuration
Listener
Listener
“HWW”
“HWW”
New
Listener

26. PonData
Data- State
Config Fault PM HWW
Base

27. PonData
Data- State
Config Fault PM HWW
Base
NtPonLine LtPonLine

28. xxxData
Data- State
Config Fault PM HWW
Base
xxxLine
Config State
xxxData
Data-
Fault
Base

29. Now

30. New Line Object
Fault
State
xxxData PM
Config Data-
Base

31. New Line Object
Fault
State
xxxData PM
Config Data-
Base
Open to change?

35. config a line Context
Retrieve PM
PM
Config
Line Object
Role

36. Fault Handling
Context
Retrieve PM
Context
Retrieve State
Context
RetrieveLine
Context
ConfigLine
Context

37. DCI Architecture
Data
What the system is
Context
The Context is the class (or its instance) whose code
includes the roles for a given algorithm, scenario, or
use case, as well as the code to map these roles into
objects at run time and to enact the use case.
Interaction
The Interaction is "what the system does." The Interaction is
implemented as Roles which are played by objects at
run time
http://www.artima.com/articles/dci_vision.html

40. EponMgr
Pon
Ont
Llid
Uni
Is It Soft? Service

41. What is the essence of the problem?

42. EponMgr
Managed Object
Pon
Ont
Llid
Uni
Service
Relation

43. ManagedObject ManagedObject
Relation

46. Box Board Line Service

47. Domain Model
Box Board Line Service
ManagedObject ManagedObject

48. Soft
Software

49. What Missed
Domain Model
Soft
Bricks Software Refactoring
Framework

50. 道法自然
Tao follows nature

51. Summary

52. The only thing constant is
change

53. Cope with Changes by
making software soft

54. Heart of making software soft is
Discovering the “Tao”

55. The way to discover “Tao” is
refactoring

56. “Tao” is the heart of making
software SOFT
People are the brain to
find the heart

57. Thank You
Contact:
xihong.zhao@gmail.com
Weibo: http://weibo.com/zhaoxihong

58. Questions?