Scribd Logo
Upload

Welcome to Scribd!

  • SE P1 12 Data Modeling

    Uploaded by

    Ayush Pareek
    11 views7 pages
    The document discusses identifying attributes for classes in a domain model for a movie ticket booking system. It provides examples of attributes for a "Course" class like code, venue, and topics. Attributes are described as units of information relevant to describing a class. Only attributes important to user stories should be included. The document gives examples of potential attributes for a "Multiplex" class like name, city, number of screens, contact details, date opened, and social media URLs. It outlines the purpose and Sprint 1 functionality of the system to provide context for identifying attributes for relevant classes.

    Original Description:

    cbjkascasc asc as vas vs v ds vsv s vs vd vs dv dv sdv sdvs dvdv

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses identifying attributes for classes in a domain model for a movie ticket booking system. It provides examples of attributes for a "Course" class like code, venue, and topics. Attributes are described as units of information relevant to describing a class. Only attributes important to user stories should be included. The document gives examples of potential attributes for a "Multiplex" class like name, city, number of screens, contact details, date opened, and social media URLs. It outlines the purpose and Sprint 1 functionality of the system to provide context for identifying attributes for relevant classes.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    11 views7 pages

    SE P1 12 Data Modeling

    Uploaded by

    Ayush Pareek
    The document discusses identifying attributes for classes in a domain model for a movie ticket booking system. It provides examples of attributes for a "Course" class like code, venue, and topics. Attributes are described as units of information relevant to describing a class. Only attributes important to user stories should be included. The document gives examples of potential attributes for a "Multiplex" class like name, city, number of screens, contact details, date opened, and social media URLs. It outlines the purpose and Sprint 1 functionality of the system to provide context for identifying attributes for relevant classes.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 7

    Software Engineering

    Sale

    Payment

    Paid by4

    -date
    -time

    -amount
    1

    1
    1..*
    Item
    -id
    -description
    -price

    Sold4
    1 0..*

    Sales Line Item

    Cash Payment

    Card Payment

    -quantity

    -cash tendered

    -card number
    -expiry date
    -name
    -type

    Data Modeling (contd.)


    Prof. Narsi Bolloju
    LNMIIT

    Topics for today


    How to identify attributes of various
    classes in the domain model

    Multiplex Domain Model


    Sprint 1

    What is an Attribute?
    Objects
    Class
    Attribute Values

    :Course

    Attribute

    Course
    code
    venue
    topics

    code= SWE
    venue= LH-04
    topics=[methods;
    design;testing]

    :Course
    code= DBMS
    venue= LH-02
    topics=[ERD;
    design;relational]

    Attributes

    Units of information relevant to the


    description of the class
    Only attributes important to the user
    stories should be included
    Attributes can be simple or complex
    (e.g., lists, nested structures)
    Each class may include a unique key (e.g.,
    orderID, employeeNo, ); but no foreign
    keys (FK is relevant to relational db)
    Slide 5

    Attributes of Multiplex Class

    name
    city
    noOfScreens
    contactDetails
    dateOpened
    webURL
    facebookURL

    Identify attributes of various


    classes in the domain model
    System purpose/objective: Booking system to enhance
    ticket sales efficiency of sales persons, to assist in
    scheduling shows effectively, and to provide best booking
    experience for the customers.
    Use cases (or the functionality described in user stories)

    Sprint 1: maintain information about movies; maintain


    multiplex details; propose show schedule and ticket prices
    for new releases; schedule counter staff; approve show
    schedule and ticket prices

    You might also like