1 / 19

Object Oriented Analysis and Object Oriented Programming

Object Oriented Analysis and Object Oriented Programming. Session 4 LBSC 790 / INFM 718B Building the Human-Computer Interface. Agenda. Class diagrams Object diagrams Object design Object oriented programming in Java. Object Modeling. Models are abstractions of reality

leejohnson
Download Presentation

Object Oriented Analysis and Object Oriented Programming

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. Object Oriented AnalysisandObject Oriented Programming Session 4 LBSC 790 / INFM 718B Building the Human-Computer Interface

  2. Agenda • Class diagrams • Object diagrams • Object design • Object oriented programming in Java

  3. Object Modeling • Models are abstractions of reality • That are created for a specific purpose • Classes represent types of entities • That are important for the chosen purpose • Specify subordinate objects and methods • Objects are specific instances of classes • Encapsulate specific objects and methods

  4. Flight Finder Exercise http://www.glue.umd.edu/~oard/spacea/ff/

  5. Flight Finder Background • The traveler (or a system administrator) will first obtain schedule data from JOSAC using their Web browser and store it on their hard drive in the received format. Upon program initiation, the Parse Sched use case will run automatically. Once that completes, the traveler may specify the origin, destination, radius around each, and a connection radius (or leave any of the default values set), earliest and latest times, and then initiate the search. Once the search completes, the traveler may step through the interesting routes one at a time, viewing information on which their decision might be based. Once one or more acceptable routes have been identified, the traveler can then contact the appropriate facilities directly to make travel arrangements.

  6. FlightFinder Use Case Diagram Search <<include>> JOSAC Parse Sched Traveler <<include>> Select

  7. Search Use Case Narrative • Assumptions • Current JOSAC schedule parsed • Pre-conditions • None • Initiation • Search function selected • Dialog • Search parameters selected, search initiated, unknown locations resolved, route list displayed • Termination • Route search complete (normal), unknown location (error) • Post-conditions • Route list displayed (if available) or blank

  8. Select Use Case Narrative • Assumptions • Route list displayed • Pre-conditions • At least one available route • Initiation • Route selected from list • Dialog • Select route, display details in map+timeline+text • Termination • Display completed • Post-conditions • Details displayed

  9. Flight Finder Background • The traveler (or a system administrator) will first obtain schedule data from JOSAC using their Web browser and store it on their hard drive in the received format. Upon program initiation, the Parse Sched use case will run automatically. Once that completes, the traveler may specify the origin, destination, radius around each, and a connection radius (or leave any of the default values set), earliest and latest times, and then initiate the search. Once the search completes, the traveler may step through the interesting routes one at a time, viewing information on which their decision might be based. Once one or more acceptable routes have been identified, the traveler can then contact the appropriate facilities directly to make travel arrangements.

  10. FlightFinder Class Diagram * 1..9 1..* 1 Route Leg Flight Sequence of Sequence of * * * * Displayed in Flies between Contains 1 0..1 2 1 GUI Airfield Schedule 1 1 Travel between Uses Displayed in 1 2 1 Map Location AircraftType Displayed in 1 Timeline

  11. Full FlightFinder Class Diagram * 1..9 1..* 1 Route Leg Flight Sequence of Sequence of * +addLeg(l:Leg) +summary():String -seats: integer -departureTime: Time -arrivalTime:Time +parse(s:String) +summary():String -flightNumber:String +parse(s:String) * * Displayed in * Flies between Contains 0..1 Uses GUI Airfield Schedule 1 1 +search(p:Param) +display(r:Route) -name:String -icaoIdentifier:String{4} -updated:Time -source:URL +parse(f:File) 2 1 1 Travel between 1 Map Location AircraftType Displayed in 2 Displayed in +draw(r:Route) -latitude:double -longitude:double -timeZone:TimeZone +distanceTo(l:Location) -name:String -speed:int +flightTime(o:Location, d:Location) 1 1 Timeline +draw(r:Route)

  12. FlightFinder Object Diagram 1st 1:Route 2nd NV514:Flight :Leg -flightNumber:NV514 -seats=34 -departureTime=1600Z -arrivalTime=1900Z :Leg AF302:Flight Lambert:Airfield :GUI -seats=3 -departureTime=1200Z -arrivalTime:1400Z -flightNumber:AF302 -name=Lambert Field -icaoIdentifier=KSTL O LAX:Airfield Andrews:Airfield -name=LA Intl Airport -icaoIdentifier=KBLV -name=Andrews AFB -icaoIdentifier=KADW Sep26:Schedule D :Map -updated:Sep 26/1200Z -source:http://www… O DC:Location Scott:Airfield D -latitude:38-48N -longitude:076-51W -timeZone=EASTERN -name=Scott AFB -icaoIdentifier=KBLV O C-9B:AircraftType :Timeline -name=C-9B -speed=450 knots LA:Location Key: O = Origin D = Destination -latitude=33-57N -longitude=118-24W -timeZone=PACIFIC D

  13. Class Critique • Multiple instances must be possible • Each uniquely identifiable • Can’t be subdivided into distinct classes • Multiple attributes needed to describe • No empty attribute values • Methods needed • At least for creation and modification

  14. Attribute Critique • Naturally describes the object • Does not describe some other object • Value will be known for some instances • Value will never be empty • Cannot be subdivided into smaller attributes • One value, not a list of values • Cannot be computed from other attributes

  15. Relationships • Object relationships • Has-a • Aggregation • Composition • Class relationships • Generalization (“extends”) • “Implements”

  16. Practice Exercise • Create a Class Diagram for an academic transcript • Include a method to compute grade point average • Include a method to print the transcript • Code (only) the transcript class in java • Include a main method that tests the class • Create stubs for any other needed classes • Run your main method

  17. Classes to Explore in the API • String • Manipulate strings (e.g., to extract substrings) • StringTokenizer • Pick apart strings (e.g., into words) • GregorianCalendar • Dates and times • Hashtable • Like arrays, but with any object as the index

  18. Muddiest Point On a blank sheet of paper, write a single sentence that will convey to me what you found to be the most confusing thing that was discussed during today’s class.

  19. FlightFinder Class Diagram Location latitude longitude distanceTo() timeZone() Airfield name icaoIdentifier location display() Flight flightNumber aircraft legs display() Options keyboard routes compute() display() Route legs display() Leg flight departureField departureTime arrivalField arrivalTime availableSeats display() Aircraft type display() Schedule webpage readFlight() readDate() display()

More Related