The missing part of software development: engineering
1 like103 views
The document discusses how software engineering principles can be applied to software development to address common pain points experienced by developers. It advocates adopting practices used in civil engineering like solid principles, design patterns, object-oriented design, and test-driven development. This includes starting with use cases to understand requirements at a high level, hiding complexity behind abstractions, and developing loosely coupled code through interfaces and dependencies. The goal is to develop software using a more rigorous engineering approach to improve quality and sustainability.
![10
“The creative application of scientific principles to
design or develop structures [..] utilising them
singly or in combination; or to construct or
operate the same with full cognisance of their
design; or to forecast their behaviour under
specific operating conditions; all as respects
an intended function, economics of operation
and safety to life and property.”
A m e r i c a n E n g i n e e r s ' C o u n c i l f o r P r o f e s s i o n a l D e v e l o p m e n t
“ENGINEERING”](https://image.slidesharecdn.com/enterprisepresentationgrakn-171208131251/85/The-missing-part-of-software-development-engineering-10-320.jpg)
The missing part of software development: engineering
- 1. 1 THE MISSING PART OF SOFTWARE DEVELOPMENT: ENGINEERING M I C H E L E O R S I
- 2. 2 WHAT DO WE DO HERE? C R E A T E V A L U E
- 3. 3 HOW DO WE DEVELOP A PROJECT/PRODUCT/FEATURE? I D E A I M P L E M E N TAT I O N C H A N G E ( S ) I M P L E M E N TAT I O N R E F I N E M E N T I M P L E M E N TAT I O N A N A LY S I S
- 4. 4 HOW DO WE USUALLY PERCEIVE THIS WORFLOW? F R U S T R A T I O N
- 5. 5 HOW THIS WOULD BE SEEN BY CIVIL ENGINEERS? O P P O R T U N I T Y
- 6. 6 WHERE’S THE OPPORTUNITY? Q U I C K A N D E A S Y T O C H A N G E L O W G R A N U L A R I T Y F I X E S E A S Y T O M O V E S T U F F A R O U N D A B S T R A C T I O N F R I E N D LY D E V E L O P E D W I T H F E W T O O L S P O S S I B I L I T Y T O I T E R AT E
- 7. 7 WHERE’S DEVELOPER PAIN? Q U I C K A N D E A S Y T O C H A N G E S L O W G R A N U L A R I T Y F I X E S E A S Y T O M O V E S T U F F A R O U N D A B S T R A C T I O N F R I E N D LY D E V E L O P E D W I T H F E W T O O L S P O S S I B I L I T Y T O I T E R AT E R I G I D I T Y F R A G I L I T Y I M M O B I L I T Y V I S C O S I T Y O PA C I T Y B I G D E S I G N U P F R O N T
- 8. 8 NOT SO EASY TO EXPLAIN B E D = B E D R O O M
- 9. 9
- 10. 10 “The creative application of scientific principles to design or develop structures [..] utilising them singly or in combination; or to construct or operate the same with full cognisance of their design; or to forecast their behaviour under specific operating conditions; all as respects an intended function, economics of operation and safety to life and property.” A m e r i c a n E n g i n e e r s ' C o u n c i l f o r P r o f e s s i o n a l D e v e l o p m e n t “ENGINEERING”
- 11. 11 ENGINEERING BEST PRACTICES IN SOFTWARE S O L I D P R I N C I P L E S H E X A G O N A L / P O R T A D A P T E R / O N I O N A R C H I T E C T U R E D O M A I N D R I V E N D E S I G N D E S I G N PAT T E R N O B J E C T O R I E N T E D D E S I G N P R I N C I P L E S G R A S P P R I N C I P L E S C Q R S PAT T E R N
- 12. 12 T E S T A B S T R A C T I O N D E T A I L S WHERE SHOULD WE START FROM? U S E C A S E
- 13. 13 L I B R A R Y D E T A I L S F E A T U R E WHERE SHOULDN’T WE START FROM? I N T E G R AT I O N T E S T
- 14. 14 USE CASE DRIVEN APPROACH CREATE LICENSE W H AT I S A L I C E N S E ? W H AT ’ S T H E P U R P O S E ? W H I C H A R E T H E E X P E C TAT I O N S ? W H AT A R E U N N E C E S S A R Y D E TA I L S ? T A C K L I N G C O M P L E X I T Y I N T H E H E A R T W H AT C A N W E H I D E B E H I N D A N A B S T R A C T I O N ?
- 16. 16 TEST DRIVEN DEVELOPMENT CREATE LICENSE E N C A P S U L AT E D O M A I N O B J E C T H I D E D E TA I L S M O C K A B S T R A C T I O N T E S T E X P E C TAT I O N S S T A R T F R O M E X P E C T A T I O N S V E R I F Y I N T E R A C T I O N S
- 17. 17 UBIQUITOUS LANGUAGE CREATE LICENSE L O A D E N C R Y P T I O N K E Y S AV E T H E L I C E N S E E N C R Y P T T H E L I C E N S E L A N G U A G E B E T W E E N D E V S A N D U S E R S
- 18. 18 DEPEND UPON ABSTRACTION CREATE LICENSE <<interface>> LOAD ENCRYPTION KEY <<interface>> ENCRYPTER <<interface>> SAVE LICENSE L O W C O U P L I N G
- 19. 19 MULTIPLE LOW-LEVEL IMPLEMENTATION CREATE LICENSE <<interface>> LOAD ENCRYPTION KEY <<interface>> ENCRYPTER <<interface>> SAVE LICENSE F A S T I N T E G R A T I O N T E S T S LOAD FROM DISK LOAD FROM DB LOAD FROM RPC SAVE TO DISK SAVE TO DB SAVE THROUGH RPC SIMPLE ENCRYPTER
- 20. 20 MAIN PARTITION public static void main B U I L D T H E A P P L I C A T I O N FACTORY +newLicenseApp() CREATE LICENSE LOAD FROM DISK SAVE TO DISK SIMPLE ENCRYPTER <<create>> <<create>>
- 21. ADAPTER 21 ONION/HEXAGONAL ARCHITECTURE D O M A I N A N D A D A P T E R S DOMAIN DATABASE FILESYSTEM MEMORY NETWORK REST
- 22. 22 DEMO TIME
- 23. 23 HANDLE WITH CARE! E X P E N S I V E
- 24. 24 EVALUATE THE BENEFITS! L E A R N I N G
- 25. 25 WHAT DO WE DO HERE? C R E A T E V A L U E
- 26. 26 THANKS