Download presentation
Presentation is loading. Please wait.
PublishVivian Patrick Modified over 9 years ago
1
Chandan Rupakheti Office: Moench Room F203 Phone: (812) 877-8390 Email: rupakhet@rose-hulman.edu These slides and others derived from Shawn Bohner, Curt Clifton, Alex Lo, and others involved in delivering 374. CSSE 374: Getting a Grasp on GRASP Q1 Steve Chenoweth Office: Moench Room F220 Phone: (812) 877-8974 Email: chenowet@rose-hulman.edu Left – Whose responsibility is it? Always a tough question, and the results vary!
2
In the flow of programming… It’s a lot like playing music – Combines effortless logic With intuition And “it” loves for us to do it! But… “The flow” suppresses self- consciousness Which is the part of the brain that’s supposed to remember what you did! So, when you come back to your own code – You need to rely on its being logical, conceptual, and coherent! Thus – OO… and Patterns! And anyone else reading it surely needs this, too!
3
Mastering Object-Oriented Design A large set of soft principles It isn’t magic. We learn it with: Patterns (named, explained, and applied) Examples Practice “The critical design tool for software development is a mind well- educated in design principles.” Q2
4
Today SOLID GRASP (From Uncle Bob back to Larman) SRP specifically – The basis for the Cohesion pattern, that we’ll study today SRP more generally – basis for today’s “Responsibility Driven Design” ideas Bob Martin – Popularized SRP Craig Larman – Your Book’s Author
5
Responsibility-Driven Design Responsibility Driven Design (RDD) Pioneered by Rebecca Wirfs-Brock in early 1990s Think of objects in terms of: What they do or What they know …the human worker metaphor! An object’s obligation or contract that it offers to other objects
6
Responsibilities for an Object Doing a Sale is responsible for creating instances of SalesLineItem Knowing a Sale is responsible for knowing its total cost
7
Knowing and Doing Responsibilities “Doing” Responsibilities Create another object Perform a calculation Initiate an action in an object Control/coordinate activities of objects “Knowing” Responsibilities Knowing it’s own encapsulated data Knowing about other objects Knowing things it can derive or calculate Q3,4
8
Responsibilities Come in All Sizes BIG : provide access to a relational database small: create a Sale A responsibility is not the same thing as a method
9
When Do We Assign Responsibilities? While coding While modeling UML is a low-cost modeling tool Can assign responsibilities with minimal investment
10
General Responsibility Assignment Software Patterns (GRASP) 1/2 General Responsibility Assignment Software Patterns (or Principles) A set of patterns for assigning responsibilities to software objects What is a Pattern? A pattern is a named and well-known problem-solution pair that can be applied in a new context
11
General Responsibility Assignment Software Patterns (GRASP) 2/2 Five Covered In Chapter 17 1. Creator 2. Information Expert 3. Controller 4. Low Coupling 5. High Cohesion Four Later In Chapter 25 PolymorphismPure Fabrication IndirectionProtected Variations
12
Design: Floor Tiles The worst part is when sidewalk cracks are out-of- sync with your natural stride.
13
Information Expert Pattern Pattern Name Information Expert Problem What is a basic principle by which to assign responsibilities to objects? Solution Assign a responsibility to the class that has the information needed to fulfill it. Names Matter! “New pattern” is an oxymoron! Q5,6
14
Information Expert and Unique IDs Basic principle of RDD: Assign responsibility to the object that has the required information “Tell the expert to do it!” Who should get a square given a unique ID? Let the Board do it because it knows about the squares
15
Creator Pattern Who should create object A? Solution (advice): Let B do it if: B contains or aggregates A B records A B closely uses A B has the initializing data for A Monopoly Board Example When you start a game, who creates the squares for the board? Let Board create them since it contains the squares Q7
16
Monopoly Example
17
Create “in Action”
18
Composition
19
Exercise on Creator Examples Break up into your project teams Given the following: Domain Model for BBVS Identify Creator pattern examples (hint) B contains or aggregates A B records A B closely uses A B has the initializing data for A Q8
20
Store Address Phone# Customer name address phone# Video ID Transaction date Payment /amount: Money type authorization Initiates Records- rental-of Pays-for Transacts Rents-from, Buys-from Stocks Selects *1 1 * * 1 * 1..*111 0..* 1 Makes- Authorizes 1 1..* Rental dueDate ReturnDate ReturnTime VideoDescription title subjectCategory VideoSupplier address name newVideos Basket Shelf location stock Membership ID startDate PricingPolicy perDayRentalCharge perDayLateCharge 1 Obtains 1 1 Maintains 1 * Determines- rental-charge 1 * Contains 1 * * 1 Stores- video-on Defines 1 * Provides 1 * * Describes Contains 1 0..* Provides 1 0..* 1 1 Holds- videos-in 1
21
GRASP Fits in with the Goals of Software Design In many areas of engineering: In software: Gather Requirements Design for Production Build & Sell It / Them Decide What to Do Next Gather Requirements Design & Deliver Rel 1 Design & Deliver Rel 10 Decide What to Do Next … Short engineering cycle. Maintenance is most of the engineering cycle. So, we need to keep coming back to the design.
22
GRASP Fits in with Systems Engineering Principles Like top-down design that minimizes interface complexity: And having an understandable “design” to build the pieces into.
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.