CIS 764 Database Systems EngineeringSlide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Fall 2008http://www.cis.ksu.edu1CIS 764 Database Systems EngineeringL13 Pet Sequences .2 Review of in-class sequences for select/purchase a pet. … status … …. Then, recall the class model … slide 3 (you should have larger copy)Fall 2008http://www.cis.ksu.edu2CIS 764 Database Systems EngineeringID ADF217 5759 5180056427 542 48304516648705 48888 49047 432523728 25302 21488 04182 05878 07955 08484 09471 0Fall 2008http://www.cis.ksu.edu3CIS 764 Database Systems EngineeringComments: -- difficult to debug -- careful attention to settings to setting that affect code generation -- check if server runs -- TA Pranshu Gupta … linked from syllabus page -- encourage consulting/helps from other students (but send email to identify who provides useful helps)Fall 2008http://www.cis.ksu.edu4CIS 764 Database Systems EngineeringFall 2008http://www.cis.ksu.edu5CIS 764 Database Systems EngineeringFall 2008http://www.cis.ksu.edu6CIS 764 Database Systems EngineeringFall 2008http://www.cis.ksu.edu7CIS 764 Database Systems EngineeringSummary of issues ( + and - ) :Basic rules: -- arrow at the top; return at the bottom -- instance name wherever multiple instances ( e.g. Category) -- caution about get/give objects to GUI : give … for data bound components get ….unlikely , rather return a values object (same fields, but not a managed entity bean) Aspect oriented design: ignore login operation -- login determines “theCustomer” objectFall 2008http://www.cis.ksu.edu8CIS 764 Database Systems EngineeringSummary of issues ( + and - ) :Basic rules: -- arrow at the top; return at the bottom -- instance name wherever multiple instances ( e.g. Category) -- generally, don’t get/give objects to GUI Aspect oriented design: ignore login operation Interaction patterns: -- added “getCategories ( ) to class model -- might assume “getCatNames( ): [String]Fall 2008http://www.cis.ksu.edu9CIS 764 Database Systems EngineeringSummary of issues ( + and - ) :Interaction patterns: Data bound GUI components (e.g. ADF components). e.g. If pull-down list (or other) is linked to a component that provides [string] .. such as category list, then that call is auto part of the GUI … don’t need to show it in the model sequences.Fall 2008http://www.cis.ksu.edu10CIS 764 Database Systems EngineeringFall 2008http://www.cis.ksu.edu11CIS 764 Database Systems EngineeringSummary of issues ( + and - ) :Basic rules: -- arrow at the top; return at the bottom -- instance name wherever multiple instances ( e.g. Category) -- generally, don’t get/give objects to GUI -- show (…) or (parms) or ( …) + supporting text Aspect oriented design: ignore login operation Interaction patterns: -- added “getCategories ( ) to class model -- might assume “getCatNames( ): [String] -- “getObject( id) ” belongs to the owning collection / session -- found model error: need PO object ! (or status for shopping cart )Fall 2008http://www.cis.ksu.edu12CIS 764 Database Systems EngineeringSummary of issues ( + and - ) : Interaction patterns: -- addCartItem() vs addToCart() model shows CartItem owned by the Cart … change method to addToCart( ) … make addItem( ) an internal method -- pass PetID vs Pet model shows Cart references the Pet object … so pass the aPet objectFall 2008http://www.cis.ksu.edu13CIS 764 Database Systems EngineeringFall 2008http://www.cis.ksu.edu14CIS 764 Database Systems EngineeringSummary of issues ( + and - ) : Aspect oriented design: ignore login operation Interaction patterns: -- added “getCategories ( ) to class model -- might assume “getCatNames( ): [String] -- “getObject( id) ” belongs to the owning collection / session -- shows CartItem , but not the Cart -- who creates the Cart ?? model shows from the CustomerFall 2008http://www.cis.ksu.edu15CIS 764 Database Systems EngineeringSummary of issues ( + and - ) :Basic rules: -- arrow at the top; return at the bottom -- instance name wherever multiple instances ( e.g. Category) -- generally, don’t get/give objects to GUI -- show (…) or (parms) or ( …) + supporting text -- callee cannot out-live the caller -- call-back requires new activation-record box Aspect oriented design: ignore login operation Interaction patterns: -- added “getCategories ( ) to class model -- might assume “getCatNames( ): [String] -- “getObject( id) ” belongs to the owning collection / sessionFall 2008http://www.cis.ksu.edu16CIS 764 Database Systems EngineeringFall 2008http://www.cis.ksu.edu17CIS 764 Database Systems Engineering -- “get status( )” is a Pet method , not Collection method -- “isCartEmpty( )” is a Cart method , not a PO method and is not a sub-part of “addItem( )Fall 2008http://www.cis.ksu.edu18CIS 764 Database Systems EngineeringFall 2008http://www.cis.ksu.edu19CIS 764 Database Systems Engineering
View Full Document
Unlocking...