1 / 12

Project 5: New Venue

Project 5: New Venue. New Venue. Based on the posted New Venue scenario http://www.cse.usf.edu/~turnerr/Object_Oriented_Design/077_Ticket_Booth_Scenarios.pdf create a class diagram for classes needed to implement the New Venue scenario. It is OK to provide multiple diagrams if desired.

abrial
Download Presentation

Project 5: New Venue

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. Project 5: New Venue

  2. New Venue • Based on the posted New Venue scenario http://www.cse.usf.edu/~turnerr/Object_Oriented_Design/077_Ticket_Booth_Scenarios.pdf create a class diagram for classes needed to implement the New Venue scenario. • It is OK to provide multiple diagrams if desired. • These classes should describe software vs. the real world. • Your diagram(s) should be in the form of a file, so that you can submit it via Blackboard assignments. You can either use a drawing program such as Visio or PowerPoint, or draw the diagram by hand and scan it or photograph it. • Be sure it is legible.

  3. Venue Classes • Be sure that there is a responsible class for each operation that the system must perform in the New Venue scenario. • Be sure there is a home for each piece of information needed in order to perform the required actions. • Show required associations between the classes. • Avoid redundancy. • There should be only one class responsible for a given operation. • Each required piece of information should have only one home.

  4. New Venue • Write a program to implement the New Venue use case. • Omit login and function selection. • Start at the beginning of the Add Venue operation. • Terminate upon completion.

  5. Existing Classes • Reuse class definitions from previous projects where possible. • Update them if necessary. • New method in class Venue: • Display_All( ) • Display seats and seating sections as well as name and address.

  6. Seating Plan 1 1 1 1 1 1 2 2 2 2 2 2 3 3 3 3 3 3 4 4 4 4 4 4 5 5 5 5 5 5 6 6 6 6 6 6 7 7 7 7 7 7 Row F Row E Row D Row C Row B Row A Center Section Right Section Back Section Left Section Front Section

  7. User Interface

  8. User Interface

  9. User Interface

  10. Ground Rules • You may work with one other person. • OK to work alone if you prefer. • If you do work as a pair • Work together! • Both members are expected to contribute. • Submit a single set of the deliverables. • Both members should understand work in detail. • Do not share your work with other students. • Before or after submitting the project. • It is OK to discuss the project. • Do not copy any other student’s work. • Don’t look at anyone else’s deliverables. • Don’t let anyone look at your deliverables.

  11. Ground Rules Except for code posted on the class web site • Do not copy code from the Internet • or any other source. • Write your own code.

  12. Submission • Project is due by 11:59 PM, Sunday, March 27. • Deliverables: • Document file for class diagram(s). • Source code for the program. • If you work with another student, include both names in the assignment comments. • Submit only one solution. • Use the Blackboard Assignment to submit your project.

More Related