Detailed Architecture And Design Of XYZ Car Park System
Database
Main Functional requirement:
Database: The main component for storing the records of the employees and customer. The database is required to be connected with the devices of the car parking system and should be updated at real time for responding to the query of the customer (Atzeni et al., 2013). The database also store the different applications and the tariff plans for increasing the efficiency of the system.
Business rules: A parking space is allocated for the sessional ticket holders and the user needs to use the space for parking their car on the weekdays. The tariff plan is displayed at the screen installed in the entry gate (Clarke, 2012). For the normal user a token is generated with the entry time and the registration number of the vehicle printed on the ticket. The parking charge is calculated at the exit gate calculating the entry time and the exit time. In the weekends the seasonal ticket holder are not allowed to use the ticket.
Payment: The user can pay the parking charge using debit or credit card by inserting their card at the card reader slot installed at the exit barrier of the car parking lot (Geng & Cassandras, 2013). The user can also pay in cash at the counter and get a token with printed barcode and exit the parking lot.
Level of Authorization: The information system should not be accessible and the servers required for maintaining the car parking system is installed in a room under surveillance and lock and key such that it is not physically accessible by any third party (Khomtchouk, Van Booven & Wahlestedt, 2014). The DBA and the system admin have the right to access the server and modify the information such as changing the tariff plan, delete or entry employee information, etc.
Main Non-Functional Requirement:
Performance: The information system developed for XYZ car park is required to be handle huge number of client request and respond to the query immediately.
Scalability: The developed system should be scalable and it must respond according to the demand of the customer.
Availability: The system should be available for the user all the time and the maintenance of the system is required to be done during the lean hours.
Reliability: Customer should rely on the information system and it should calculate the parking charge efficiently. The parking lot is require to be installed with CCTV cameras for increasing the security of the parking lot and thus increase the reliability of the system.
Business Rules
Recoverability: The system should be able to recover against any damage and the information residing in the database of the organization should never get lost.
Security: The database of the information system is required to be secured from unauthroised access and it is also required to be encrypted such that if any hacker gets access to the database they should not recover the data.
The use case is required to be developed identifying the actors and the roles for development of the information system. The functionality of the system can be defined from the developed use case. Two use case are developed one for the operational section and one for the management section for the identification of the activity associated with the system. The main actors identified for the development of the use case diagram are the normal customer, attendant, seasonal ticket holder, security officers, city council. Their roles are described below:
Normal Customer: The normal customer can use the car parking system 24*7 and enter the parking lot by generating a ticket from the entry barrier.
Attendant: The attendant assist the user and have the control to open or close the barrier manually in emergency situation.
Seasonal ticket holder: The seasonal ticket holder have ticket for a season and they park their registered car in the fixed allocated space. They need to renew their ticket on expiry.
Security officers: The records of the car entering and leaving the parking lot are maintained in a log book. They also monitors the activity of the users using the parking lot and responds in emergency situation.
City council: The city council have the authority to evaluate the tariff and monitors the records of transaction. The staffs are paid by the city council and monthly report is generated and stored for auditing.
Use case for Management section of XYZ car park system.
Figure 1: management section use case
(Source: Created by author)
Use case for the operational section of XYZ car park
Figure 2: Operational section use case
(Source: Created by author)
Operational section class diagram
Figure 3: Class diagram for operation section
(Source: Created by author)
Management section class diagram
Figure 4: Class diagram for management section
(Source created by author)
The software development life cycle model is used for the developing the car information system of the car park and requirement of the project is identified and categorized as functional and non-functional requirement. The different phases are reviewed for the identification of the functional and the non-functional requirement and they are as follows;
Requirement analysis and specification: The requirement for the development of the car parking system is required to be gathered and analyzed for the development of the XYZ car parking system. A prototype of the project is required to be developed and approved by the city council for starting the development of the project.
Payment
Design phase: The framework of the car parking system is required to be developed and the different components of the car parking system is required to be interconnected for increasing the functionality of the system. A layout of the car parking system is required to be prepared for identification of the places where the barriers and the CCTV are required to be installed.
Implementation phase: The implementation of the information system is done by designing the interface and coding different programs such as calculation of the ticket price and generation of the ticket code, etc. The database of the information is also required to be designed to store the information of the employees and the customer in the information system.
Maintenance phase: In this phase the errors identified in the system are resolved with the help of technical experts. The usability of the system is also improved by implementing necessary change in the information system and modification of the system and aligning it with the needs of the customer.
The XYZ car park framework should have been produced with the end goal that all the procedure of the framework is mechanized, for example, allocating a parking space for the vehicles entering the parking lot, printing of the ticket with all the information such as the time, registration number printed in the form of barcode on the ticket. To computerize the framework, and control the entry and the exit barrier of the car parking lot automatically and assist the vehicle to park their vehicle in the parking space allotted for the vehicle. It is additionally required to connect the different IoT devices used in the parking space to automate the operation of the parking lot.
The occurrence of the human errors can be minimized with the implementation of the automated information system and controls for the car parking system. The administration of the framework should be possible proficiently and it would build the security of the stopping territory enabling approved vehicles to go into the part. The reason for the answer to recognize the defects and hazard related with the mechanization of the car park system and give answer for relieve these issues.
Assumption/ Dependencies
The different assumption made for the development of the project are as follows:
- Different IoT sensors like motion detection and scanner are installed at the entry point and the exit barriers.
- The number of free and occupied space are calculated and displayed at the giant screen installed at the different levels of the parking lot.
- The entry point and the exit point barriers respond quickly to the request of the user and is connected to central server to decrease the response time and operate quickly
- The fixed space allocated to the seasonal ticket holder are never allocated to the normal users on the weekdays.
- The ticket is generated from the entry barrier on successful scanning of the registration number of the vehicle and it is embedded in the ticket in the form of barcode.
- The parking fees is calculated at the exit point and the ticket is verified and registration number of the vehicle is scanned for increasing the security of the system.
- A LCD screen is required to be installed at different levels of the parking lot for informing the user about the level and the number of free space available in the parking lot.
The XYZ car park system should precisely ascertain the stopping time and the stopping charge. The framework ought to have the capacity to decide the free space accessible for the new vehicles to be stopped. In the event that there is any issue in the framework it ought to have the capacity to recuperate in a brief timeframe and no data ought to be lost amid this procedure.
Level of Authorization
The XYZ car park system is required to be available for the normal user all the time and for the seasonal ticket holder in the weekdays. By and large there are more clients in the ends of the week and in this way the city gathering have received the strategy to give the occasional ticket holder parking spot just on the weekdays.
Features
The data of the customer and the employees are required to be recorded in the database of the information system of the XYZ car park system. The database is required to be secure and available all the time such that it can respond to the query of the user all the time. The parking charge is required to be calculated by scanning the barcode and noting the entry and the exit time. The information system is also required to be connected with a payment gateway system for taking payment from the customer.
Requirement
The regular ticket client would utilize their ticket at the entry barrier and the exit barrier and the framework ought to have the capacity to recognize the standard client and the occasional ticket holder by scanning the barcode printed on the ticket. The customary client gathers their ticket each time however, if there should arise an occurrence that a normal user enters the car parking system the validity of the ticket expires on leaving the car parking system.
Figure 5: WBS of XYZ car park
(Source: Creatd by author)
Atzeni, P., Jensen, C. S., Orsi, G., Ram, S., Tanca, L., & Torlone, R. (2013). The relational model is dead, SQL is dead, and I don’t feel so good myself.ACM SIGMOD Record, 42(2), 64-68.
Byrne, B., & Shahzad Qureshi, Y. (2013). The Use of UML Class Diagrams to Teach Database Modelling and Database Design. In Procs of the 11th Int Workshop on the Teaching, Learning and Assessment of Databases (TLAD). The Higher Education Academy.
Clarke, S. (2012). Information systems strategic management: An integrated approach. Routledge.
Cunha, A., Garis, A., & Riesco, D. (2015). Translating between Alloy specifications and UML class diagrams annotated with OCL. Software & Systems Modeling, 14(1), 5-25.
Geng, Y., & Cassandras, C. G. (2013). New “Smart Parking” system based on resource allocation and reservations. IEEE Transactions on Intelligent Transportation Systems, 14(3), 1129-1139. Ma, T., & Mohammed, O. A. (2014). Optimal charging of plug-in electric vehicles for a car-park infrastructure. IEEE Transactions on Industry Applications, 50(4), 2323-2330.
Hanumantharaju, M. C., Ravishankar, M., & Rameshbabu, D. R. (2013). Design of Novel Algorithm and Architecture for Gaussian Based Color Image Enhancement System for Real Time Applications. In Advances in Computing, Communication, and Control (pp. 595-608). Springer Berlin Heidelberg.
Ji, Z., Ganchev, I., O’Droma, M., Zhao, L., & Zhang, X. (2014). A cloud-based car parking middleware for IoT-based smart cities: Design and implementation. Sensors, 14(12), 22372-22393.
Khomtchouk, B. B., Van Booven, D. J., & Wahlestedt, C. (2014). HeatmapGenerator: high performance RNAseq and microarray visualization software suite to examine differential gene expression levels using an R and C++ hybrid computational pipeline. Source code for biology and medicine,9(1), 1.
Larman, C. (2015). Applying UML and Patterns: An Introduction to object-oriented Analysis and Design and iterative development”, Pearson Education, 2005.
Levy, N., Martens, K., & Benenson, I. (2013). Exploring cruising using agent-based and analytical models of parking. Transportmetrica A: Transport Science, 9(9), 773-797.
Rosen, M., Lublinsky, B., Smith, K. T., & Balcer, M. J. (2012). Applied SOA: service-oriented architecture and design strategies. John Wiley & Sons.
Sarkar, M. K., Chatterjee, T., & Mukherjee, D. (2013). Reverse engineering: An analysis of static behaviors of object oriented programs by extracting UML class diagram. International Journal of Advanced Computer Research, 3(3), 135.
Sharon, A., & Dori, D. (2015). A Project–Product Model–Based Approach to Planning Work Breakdown Structures of Complex System Projects. IEEE Systems Journal, 9(2), 366-376.
Straub, J., Whitney, T., Leben, T., Karboviak, K., Maguire, Z., Korvald, C., & Kerlin, S. (2013). OpenOrbiter Combined Software Work Breakdown Structure. In 2nd Annual North Dakota Space Robotics Forum.
Sun, S. P., & Chao, W. S. (2013). An Architecture-Oriented Design Method For Gaming Business Administration Systems. In C], Asia Pacific Conference on Gambling & Commercial Gaming Research (APCG2013), Taiwan.
Zhou, Y., Yang, Y., Xu, B., Leung, H., & Zhou, X. (2014). Source code size estimation approaches for object-oriented systems from UML class diagrams: A comparative study. Information and Software Technology, 56(2), 220-237.
