1 / 16
Télécharger la présentation

Software Development Principles: Gems of Wisdom

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WARNING • These slides are not optimized for printing or exam preparation. These are for lecture delivery only. • These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here. • These slides contain a lot of animations. For optimal results, watch in slideshow mode.

  2. Prof. Fred Brooks, Jr. Brooks's law : "adding manpower to a late software project makes it later"

  3. Brooks's law : "adding manpower to a late software project makes it later"

  4. Gems of Wisdom: SoftwareDevelopment Principles. Brooks's law : "adding manpower to a late software project makes it later" CS2103/T, Lecture 9, Part 3, [Oct 14, 2016]

  5. Principle of separation of concerns SYSTEM • by EdsgerDijkstra Refresh data storage Interact with user Show message to user Authenticate user Get user input Encrypt password Store user data

  6. Open-closedprinciple Software entities should be open for extension, but closed for modification. Minefield * * MinedCell EmptyCell MagicCell *

  7. Open-closedprinciple Software entities should be open for extension, but closed for modification. • by Bertrand Meyer Minefield {abstract}Cell * MinedCell EmptyCell MagicCell

  8. Liskov substitution principle Subclasses should be substitutable for their base classes. • by Barbara Liskov Minefield {abstract}Cell * MinedCell EmptyCell MagicCell

  9. Single responsibility principle Every class should have only one reason to change (i.e. should have only one single responsibility). • by Robert C. Martin(Uncle Bob) Similar to Separation of Concerns? Minefield {abstract}Cell Score Mine SOLIDPrinciples

  10. The later you find a bug, the more it costs

  11. [extra] Good, cheap, fast: select any two • Good Cheap Fast

  12. “ • ” Some principles are nicely captured in famous quotes -- me E.g. The first 90% of the code accounts for the first 90% of the development time...The remaining 10% of the code accounts for the other 90% of the development time. -- Tom Cargill [More such quotes]

  13. 1. Separation of concerns 2.Single responsibility principle 3.Open closed principle 4. …… Use in the project as much as you can. At least, be able to relate to the project

More Related