ticketbox's Issues
POST /USER/CREATE
POST /CANCEL/ORDER
GET /MOVIES/ALL
Design Class Diagrams
- A class diagram without attributes and behavior that only shows the class name and
the relationships among them. The purpose of this diagram is to show the entire
system in one page. Please make sure lines never cross each other and the diagram
is clear and easy to read
NOTE:
• You class diagram should be traceable in your use-case scenarios. Mark will
be deducted for class that are not traceable in the use-case diagram.
• In your class diagram you don’t need to show Java library classes such as
Exceptions, Buttons, String, ArrayList, etc.
• Make sure clearly identify the stereotypes of your classes (such as
<>, <>, <>
• Make sure the multiplicity/cardinality is properly indicated. - A class diagram with no relationships, only showing the class details: attributes and
behaviours. This diagram can be organized in multiple pages. Please try to keep
them well organized, clear, and easy to read.
Note: You don’t need to show constructor/destructor, getters/setters
POST /CHECKOUT
POST /USER/REACTIVATE
#27 - POST cancelling a ticket from homepage
Package Diagrams
GET /SEATS/BY/SHOWTIME
Detailed "Scenario" for each use case
A detailed “Scenario” for each use case, having all candidate objects underlined, and all
candidate operations underlined (use single-underline for objects and double-underline for
operations)
POST /CANCEL/TICKET
#26 - GET all movies on homepage
#31 - POST payment info
Movies Page
#30 - GET seats by showtime
check if showtime < 72 hours before canceling ticket
Annual Payment required notification for RU
On log in, check "validUntil" property for RU, and if its passed then prompt user to pay again.
POST /USER/LOGIN
Seat Selection
Systems Activity Diagram
Implement POST reactivate api
#28 - POST user login info
#29 - POST register user info
System Use Case Diagram
#21 - Link movie list page to seat selection
- After pressing VIEW SEATS, user is sent to seat selection page
- Seats are for selected movie and showtime
System Interaction Diagrams
System interaction diagrams for at least four major and important use cases in this system
(each team member must take responsibility for one and his/her name must appear on the
related page).
Must create four sequence diagrams
- Buying a ticket (Topan)
- Cancelling a ticket (Jason)
- Logging in (Topan)
- Registering for an account (Jason)
SQL statement + add movie cover column
State Transition Diagrams
- Ticket Object (Dimitar)
- Payment Object (Ajay)
- Another Use Case: Seat Object (Dimitar)
- Another Use Case (Ajay)
Deployment Diagram
payment class + strategy pattern
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.