Code Monkey home page Code Monkey logo

ticketbox's Issues

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

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)

Movies Page

Movie page after searching

Image

Requirements:

  • Search bar works as intended
  • List of all movies matching title show up (Case-insensitive and as long as an instance of the word matches)
  • Movies are listed in list format

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)

State Transition Diagrams

  • Ticket Object (Dimitar)
  • Payment Object (Ajay)
  • Another Use Case: Seat Object (Dimitar)
  • Another Use Case (Ajay)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.