Object and Data Modelling- PDF

Added on - 14 Jun 2021

  • 12

    Pages

  • 2984

    Words

  • 42

    Views

  • 0

    Downloads

Trusted by +2 million users,
1000+ happy students everyday
Showing pages 1 to 4 of 12 pages
Running head:OBJECT AND DATA MODELLINGObject and Data ModellingName of StudentName of the UniversityAuthor Note
OBJECT AND DATA MODELLINGTable of Contents1. Identify and briefly describe the main functional and non-functional requirements...................3Functional Requirement:.............................................................................................................3Non-functional requirements:......................................................................................................42. Draw a use case model for the information system.....................................................................6Use Case Model Diagram............................................................................................................6Use case Description....................................................................................................................6Fully developed use case:............................................................................................................73. Draw a UML domain model class diagram for all systems.........................................................8Class Diagram..............................................................................................................................84. Specific Tasks Required for Each Design Activities:..................................................................9Bibliography..................................................................................................................................11
OBJECT AND DATA MODELLING1. Identify and briefly describe the main functional and non-functional requirementsFunctional Requirement:There are many functionalities of the Collins car Park system. Among the main functionsthe major functional requirements of the system are provide below:Ticket Generation:Ticket generation is one of the key functions of the Collins car parkingsystem. The system should be able to able to generate tickets for the car owners that are enteringinto the system. The system should start calculating the parking fees as soon as the car enters intothe car parking area. The ticket generated should be able to generate the owner information, thecar information and also the calculated hours and the total parking fees payable by the customer.Handling payments:The system should be able to handle all the payments regarding the parkingfees for the car parking system. The payment system should be able to store the details of thepayment options in the system of the organization. The payment system should also be able toprovide the customer with various type of payment options such as the cash payment or paymentby card. The system should also be able to details of the payment such as the payment weremade by card or by cash. The payment of the systems should be tracked by the payment id of thesystem.Recording problems in the log book:The system might encounter a number of problems andthe problems are to be noted in the systems. Additionally, the problems are to be recoded into thesystem as the problem logs and the problems are identified with the problems unique key. Thesystem should be able to store all the details of the problems into the system such as the time ofthe problems, the details of the problems and the people that have encountered the problems.Car owner’s details:The system should be able to store the details of the car owners in thesystem. The car owner details are to be stored with the unique identifier identifying the carowner number and also the additional details of the name of the customer, address of the carowner. In addition to this the information about should also be stored in the system. The car is tobe identified by the car id and it is to be referenced with the details of the owners.Calculation of parking fees:For the calculation of the of the parking fees are to be calculate bythe system and for the calculation of the parking fees the method should be able to identify the
OBJECT AND DATA MODELLINGdifferent type of customers available for the system. The system requires to evaluate thecustomers according the categories provided below:Fixed Customers:1 week 50 AUD2 weeks 95 AUD1 month 150 AUD3 months 350 AUD6 months 575 AUD12 months 800 AUDNormal Customers:Early bird (during weekday’s midnight to 10 AM) 2.5 AUD per hourNormal rate (during weekdays 10 AM to midnight) 5 AUD per hourEarly bird (during weekend’s midnight to 10 AM) 5 AUD per hourNormal rate (during weekend’s 10 AM to midnight) 10 AUD per hourThe calculation of the parking fees are to be done in accordance with the followingmeasurements provided above. The systems should have the methods installed in the systems.Authenticating Parking:The parking system already has the information about the car ownersstored in the systems and hence, the system should be able to use the details of the cars as theauthentication metrics. The authentication of the car owners should allow them an entry into thecar parking system, whereas an unidentified authentication should deny the access to the carowners into the systems.Data storage:The system should be able to provide an efficient data storage facility for the carparking system. The system consists of a number of entities such as the car owner, car, andpayment and invoice details in the system. The invoice would finally result into the generation ofthe tickets for the systems.Security Management:The system should provide an efficient essence of security for the systemand the system should be able to store the data and maintain the data integrity of the system. Thesystem would be maintaining a large amount of data for the car owners and also the data of the
desklib-logo
You’re reading a preview
Preview Documents

To View Complete Document

Click the button to download
Subscribe to our plans

Download This Document