go back to Overview
UML-And-Object-Oriented-Design-Foundations - Content
If you want to access to this project and be part of it, please send me an email: c.santiago.cruz@icloud.com
- 1. Introduction
- 2. Why you should learn Object-Oriented Design?
- 3. What's covered in this book ?
- 4. Prerequisites
- 5. Software Development Methodologies
- 6. The Waterfall Model
- 7. Agile
- 8. Waterfall or Agile?
- 9. Core Object-Orientation Concepts
- 10. Objects
- 11. The Class
- 12. Abstraction
- 13. Encapsulation
- 14. Inheritance
- 15. Polymorphism
- 16. Object-Oriented Analysis and Design
- 17. Collecting Requirements
- 18. Mapping Requirements to Technical Descriptions
- 19. Why do we need a Common Descriptive Language
- 20. UML Basics and fundamental diagram types
- 21. The Use-Case Diagram
- 22. Visibility
- 23. Associations
- 24. Generalization
- 25. Dependency, Aggregation, composition & Realization
- 26. Sequence Diagrams
- 27. Activity Diagrams
- 28. Statechart diagrams
- 29. Case Study: Designing a Note-Taking App
- 30. Collecting the requirements
- 31. Creating User Stories
- 32. Diagraming the Main Use Cases
- 33. Identifying the classes
- 34. Describing the Flow of Note Creating using Sequence Diagrams
- 35. The Note Object´s StateChart Diagram
- 36. What is next?