Object and Data Modelling- PDF

Running head: OBJECT AND DATA MODELLING
Object and Data Modelling
Name of Student
Name of the University
Author Note

OBJECT AND DATA MODELLING
Table of Contents
1. Identify and briefly describe the main functional and non-functional requirements...................3
Functional Requirement:.............................................................................................................3
Non-functional requirements:......................................................................................................4
2. Draw a use case model for the information system.....................................................................6
Use Case Model Diagram............................................................................................................6
Use case Description....................................................................................................................6
Fully developed use case:............................................................................................................7
3. Draw a UML domain model class diagram for all systems.........................................................8
Class Diagram..............................................................................................................................8
4. Specific Tasks Required for Each Design Activities:..................................................................9
Bibliography..................................................................................................................................11

OBJECT AND DATA MODELLING
1. Identify and briefly describe the main functional and non-functional requirements
Functional Requirement:
There are many functionalities of the Collins car Park system. Among the main functions
the major functional requirements of the system are provide below:
Ticket Generation: Ticket generation is one of the key functions of the Collins car parking
system. The system should be able to able to generate tickets for the car owners that are entering
into the system. The system should start calculating the parking fees as soon as the car enters into
the car parking area. The ticket generated should be able to generate the owner information, the
car 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 parking
fees for the car parking system. The payment system should be able to store the details of the
payment options in the system of the organization. The payment system should also be able to
provide the customer with various type of payment options such as the cash payment or payment
by card. The system should also be able to details of the payment such as the payment were
made by card or by cash. The payment of the systems should be tracked by the payment id of the
system.
Recording problems in the log book: The system might encounter a number of problems and
the problems are to be noted in the systems. Additionally, the problems are to be recoded into the
system as the problem logs and the problems are identified with the problems unique key. The
system should be able to store all the details of the problems into the system such as the time of
the 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 the
system. The car owner details are to be stored with the unique identifier identifying the car
owner number and also the additional details of the name of the customer, address of the car
owner. In addition to this the information about should also be stored in the system. The car is to
be 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 by
the system and for the calculation of the parking fees the method should be able to identify the

OBJECT AND DATA MODELLING
different type of customers available for the system. The system requires to evaluate the
customers according the categories provided below:
Fixed Customers:
 1 week 50 AUD
 2 weeks 95 AUD
 1 month 150 AUD
 3 months 350 AUD
 6 months 575 AUD
 12 months 800 AUD
Normal Customers:
 Early bird (during weekday’s midnight to 10 AM) 2.5 AUD per hour
 Normal rate (during weekdays 10 AM to midnight) 5 AUD per hour
 Early bird (during weekend’s midnight to 10 AM) 5 AUD per hour
 Normal rate (during weekend’s 10 AM to midnight) 10 AUD per hour
The calculation of the parking fees are to be done in accordance with the following
measurements provided above. The systems should have the methods installed in the systems.
Authenticating Parking: The parking system already has the information about the car owners
stored in the systems and hence, the system should be able to use the details of the cars as the
authentication metrics. The authentication of the car owners should allow them an entry into the
car parking system, whereas an unidentified authentication should deny the access to the car
owners into the systems.
Data storage: The system should be able to provide an efficient data storage facility for the car
parking system. The system consists of a number of entities such as the car owner, car, and
payment and invoice details in the system. The invoice would finally result into the generation of
the tickets for the systems.
Security Management: The system should provide an efficient essence of security for the system
and the system should be able to store the data and maintain the data integrity of the system. The
system would be maintaining a large amount of data for the car owners and also the data of the

OBJECT AND DATA MODELLING
cars would be stored in the system and hence, there is huge need of securing the data that stored
in the system.
Non-functional requirements:
Non-functional requirements are those requirements which elaborate the performance
characteristic of the system and define the constraints on how the system will do so. The non-
functional requirement of the Collins Car Park system is provided in the section below:
Availability: The system should be available to the staffs of the system 24x7 so that the staffs of
the organization can work efficiently and provide services to their customers 24x7. This is very
important for the organization as the car owners would not like to park their cars anywhere else
as they are already paying for the services they are receiving. The business of the system would
also be hampered to a great deal.
Performance: The system should be able to provide the staffs and the customer of the
organization with an excellent performance. The system staffs of the system would be able to
perform all the required activities within the system. Additionally, the authentication and the
payment features of the system should be performed efficiently so that the requirements of the
organization and the business efficiencies would be maintained.
Scalability: It is referred to as the desired graceful change in system's performance
characteristics under growing utilization, and whether system can handle increasing load by
simply adding computing units. The system should be scalable the so that the staffs would be
having a limit to which they would be able to perform the activities. This would mean that the
access control aspects of the system are maintained and the data of the system would be well
structured.
Maintainability: The system should be maintainable and the maintenance of the system should
not be much of a head ache for the organization or the company. For the maintenance of the
Collin’s Car Park System, the maintenance procedures should be done at the day when the cars
are not parked and maintenance of the parking area should be done on the busiest day of the
week when the cars out of the car parking areas.

OBJECT AND DATA MODELLING
Security: The system designed for the organization should accurately secured. This would enable
the organization to maintain the confidentially within the system. The data of the organization
should be secured efficiently and the organization should be able to maintain the data integrity in
the database of the system. It is also to be seen that the data of the users of customers of the
organization are not leaked out as this might be hampering the privacy of the customers of the
Collin’s Car parking system.
2. Draw a use case model for the information system.
Use Case Model Diagram
Figure 1: Use Case Model Diagram
(Source: Created by Author)
Use case Description
The description for the use case diagram created is provide in the table below:
Use Case Description

OBJECT AND DATA MODELLING
Parking Area
Entrance
The car owner would enter into the car parking system.
Car Parking The car owner would be able to park their cars in the parking area
Provide Details The details of the of the car owner is saved in the system
Car details
Recording
The car details would be recorded in the system.
Ticket
Generation
The tickets for the car parking and the owner would be generated.
Payment
Calculation
The parking fees of the car owner would be calculated.
Make Payment The car owners would be able to make the payment in the system.
Payment option
Selection
The payment option can be selected easily by the car owner.
Exit system The car owner would be able to exit the system.
Use Case Actors
Use Case Actors
Parking Area Entrance Car Owners
Car Parking Car Owners
Provide Details Car Owners
Car details Recording Car Owners, Administrator
Ticket Generation System
Payment Calculation System
Make Payment Car Owners, System, Administrator
Payment option Selection Car Owner
Exit system Car Owners

OBJECT AND DATA MODELLING
Fully developed use case:
The car owner making a payment for the parking fee generated from the system is being
discussed in this section:
Use Case Name: Make payment
Primary Actor: Car Owner
Secondary Actors: System
Other
Stakeholders:
Administrator
Business Goal: The business goal of the organization is to provide the car owner with
the procedures of paying the parking fees to the organization.
Additionally, the car owner is also to be provided with an efficient
payment options.
Precondition: The owner of the car and the car is to be registered into the system and
also the owner is to be provided access to the system.
Success Condition The success condition is reached when the payment by the car owner is
successfully completed.
Main Path The main path of make payment
1.Payment calculation 4. Make Payment
2.Ticket generation
3.Payment option selection
Post condition: Exit System

OBJECT AND DATA MODELLING
3. Draw a UML domain model class diagram for all systems
Class Diagram
Figure 2: UML Class Diagram
(Source: Created by Author)
4. Specific Tasks Required for Each Design Activities:
Describe the environment
The system would be working with the other components of the system and also the
system would be interfaced with the ticket collection and payment system.
Design the application components
The application components would be divided into three parts, the ticketing system, the
parking system and the car owner validation system.
Design the user interface
The user interface would be divided into two sectors, firstly the interface would be
designed for the customers and the other aspect of the system would be designed for the staffs of
the Collins car parking system.

OBJECT AND DATA MODELLING
Design the database
The database design would be include the details about the data regarding the customers,
the cars and the payment details.
Software methods
The software development lifecycle is to be adopted for the development of the system
fop the Collins car park system. Firstly the functional and non-functional requirements of the
system are to be identified. After this the design of the system should be ideated. The next stage
involves the development of the prototype for the system and sending it to the clients of the
system. The clients of provide the feedback for the system and the further development of the
system is done according to the feedback provided by the clients.
Planning- The planning phase of the software development lifecycle involves the development of
the plan of the system. The system requirements and the other criteria of the system are decide
during this phase. The planning for the system are done in this phase.
Analysis- In the analysis phase the business rules of the organization are studied and the
functional and the non-functional requirements of the system are developed and ideated during
this phase. Additionally, the functional analysis of the system is done before further proceeding
with the design of the system.
Design- The core interfaces of the systems are designed in this phase the interfaces designed in
this phase are integrated with the modules of the system. Additionally, the methods for the
system are developed in this phase and the methods are called into a single function during the
implementation phase.
Implementation- the Collins car parking system would be implemented in the parking area of the
organization and additionally, the system would be integrated with the systems that are already
implemented in the car parking area. The implemented system would be providing the
organization with the payment and the authorization features.
Testing- The system is tested in this phase and the analysis of the system is performed in this
phase and the system is updated according to the analysis.

OBJECT AND DATA MODELLING
Maintenance– The maintenance of the Collins car parking system is done after the system is
been implemented. The maintenance of the parking system is done at night as the parking lot
would be busy during morning.

OBJECT AND DATA MODELLING
Bibliography
Ahmed, M. A., Butt, W. H., Ahsan, I., Anwar, M. W., Latif, M., & Azam, F. (2017, March). A
Novel Natural Language Processing (NLP) Approach to Automatically Generate
Conceptual Class Model from Initial Software Requirements. In International
Conference on Information Science and Applications (pp. 476-484). Springer, Singapore.
Almorsy, M., Grundy, J., & Müller, I. (2016). An analysis of the cloud computing security
problem. arXiv preprint arXiv:1609.01107.
Bello, S. I., Bello, R. O., Babatunde, A. O., Olugbebi, M., & Bello, B. O. (2017). A University
Examination Web Application Based on Linear-Sequential Life Cycle Model.
Bertoncello, V., Possamai, O., Bortolozzi, F., & Vosgerau, D. S. (2017, April). A Model for the
Development of Learning Objects Using Educational Design. In Proceedings of the 2017
International Conference on Information System and Data Mining (pp. 111-118). ACM.
Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Dwarakanath, A., Chintala, U., Virdi, G., Kass, A., Chandran, A., Sengupta, S., & Paul, S. (2015,
May). CrowdBuild: a methodology for enterprise software development using
crowdsourcing. In Proceedings of the Second International Workshop on CrowdSourcing
in Software Engineering (pp. 8-14). IEEE Press.
Elamin, R., & Osman, R. (2017, July). Towards Requirements Reuse by Implementing
Traceability in Agile Development. In Computer Software and Applications Conference
(COMPSAC), 2017 IEEE 41st Annual (Vol. 2, pp. 431-436). IEEE.
Gude, B. C., Kakumani, L. R., Phanindhar, S., & Singireddy, S. R. (2016). GSU Event Portal.
Johnston, S. K., & Nally, M. P. (2015). U.S. Patent No. 9,122,422. Washington, DC: U.S. Patent
and Trademark Office.
Mall, R. (2014). Fundamentals of software engineering. PHI Learning Pvt. Ltd..
Mao, K., Capra, L., Harman, M., & Jia, Y. (2017). A survey of the use of crowdsourcing in
software engineering. Journal of Systems and Software, 126, 57-84.