Ooad presentation
Download as PPTX, PDF0 likes1,176 views
The document discusses principles of object-oriented analysis and design for creating great software. It emphasizes gathering customer requirements, designing for flexibility and resilience to change. Key principles discussed include the open-closed principle, single responsibility principle, and DRY principle to avoid duplicate code. The document stresses defensive programming and programming by contract to ensure the software handles problems safely.
Ooad presentation
- 2. How do you write great software every time?
- 4. The software must do what the customer wants it to do
- 6. Make your code smart Well-Designed Well-Coded Easy to mantain Easy to reuse Easy to extend
- 7. Great software satisfies the customer and the programmer
- 8. Programmers are satisfied when: Their apps can be REUSED Their apps are FLEXIBLE Customers are satisfied when: Their apps WORK Their apps KEEP WORKING Their apps can be UPGRADED
- 9. Ok but… what shall the software do?
- 10. Gathering requirements Pay attention to what the system needs to You can figure out how later
- 11. Requirement? It’s a specific thing Your system has to do to work correctly Usually a single thing, and you can test that thing to make sure you fullfilled the requirement The complete app or project you are working on 2 - so if you leave out a requirement or even if they forget to mention sth your system isnt working correctly 1 - The customer decides when a system works correctly,
- 12. Your software has a context
- 14. + Analysis = Real world context Textual analysis = nouns / verbsUse cases Diagrams
- 15. Nothing ever stay the same No matter how much you like your Right now, it’s probably going to ch Tomorrow… Good design = flexible and resilien
- 16. Design principles Techniques that can be applied for designing or writing code to make that code more Mantainable, flexible or extensible OCP Open-closed princople DRY Don’t repeat yourself SRP Single responsibility principle Classes are open for extension And closed for modification Avoid duplicate code by abstracting Things that are common Every object in your project should have a single responsabil
- 17. Open-closed principle class Printer{ public final void print(Printable p){ … } } class SquarePrinter extends Printer{ public void print(Square s){ … } } OPEN = Extending functionality ClOSED = NO OVERRIDES
- 18. Single responsibility principle public class MobileCaller{ public void callMobile(MobileNo mobileNo){ ... } } public class ValidationService{ public static boolean validateMobileNumber(MobileNo mobileNo){ ... } } Responsibility #1: Call Responsibility #2: validate number
- 19. DRY – Don’t repeat yourself
- 20. By Contract / Defensive programming programming defensively means you’re making sure the client gets “safe” response, no matter what the client wants to have happen Programming by contract means you are working with a client code to agree on how you’ll handle problem situations