[go: up one dir, main page]

Skip to content

Java-based application using MVC design pattern simulating the purchase and reservation of movie tickets

Notifications You must be signed in to change notification settings

619ProjectGroup1/A-Movie-Theater-Ticket-Reservation-App

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

86 Commits
 
 
 
 
 
 
 
 

Repository files navigation

A-Model.Movie-Theater-Model.Ticket-Reservation-App

Design Phase (40 marks)

In this phase you should submit a Design Document that includes a clear description of system’s requirements, and design artefacts in the following order:

• Systems use case diagram. • Systems activity diagram • A state transition diagram for the following objects in your system: o Model.Ticket object o Payment object • A detailed “Scenario” each use case, having all candidate objects underlined, and all candidate operations underlined (use single-underline for objects and double-underline for operations). • System interaction diagrams for four major and important use cases in this system (each team member must take responsibility one and his/her name must appear on the related page). • A Design Level Class Specification that includes: o Aclassdiagramwithoutattributesandbehaviorthatonlyshowstheclassnameand 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 into your use-case scenarios. Mark will be deducted for class that are not trace able in these documents. o A class diagram with no relationships (no lines), 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. o A state transition diagram for at least two major and core classes in the system • A Package Diagram • A Deployment Diagram Note: In this stage you need to apply all possible design strategies and techniques to make the architecture of the system more: reusable, scalable, maintainable, reliable, and using necessary concepts such as modular design, inheritance, realization, aggregation, composition, polymorphism, and appropriate design patterns as needed.

Due Date for Design Document: Friday Nov 20, 2020 before midnight (11:59 PM)

Part II (60 marks)- Implementation Stage

In this phase will implement your proposed design, in Java. The details of implementation will be discussed later. What to submit on the D2L?

  1. A jar file that contains all .class files.
  2. A tar file that contains all .java files.

Due Date for implementation is Monday November 30th, 2020. You need to demonstrate your working application on Friday Dec 4.

About

Java-based application using MVC design pattern simulating the purchase and reservation of movie tickets

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages