Collins Parking Essay: Design And Development Considerations.

Discuss about the Collins Parking Car Park System.

Functional Requirement

External Interface – An interface should be designed that such that it can be used by the users to create a link between the database. The response time of the system must be kept minimum and the interface must be simple such that the user can use it easily.

Approval – The access of the database server must be restricted to the normal users and the full access must be given to the administrator account. The database administrator should be able to read, write and delete the database tables and the users must be divided into different categories for the management of the information generated from different sources of the Collins parking car parking system. The connecting with the database proper authorization should be used and a login account and strong password should be provided to the users of the parking system for monitoring the activity of the parking system.

Payment - Different payment options should be used by the client such that the user does not face any difficulty while using the Collins parking car parking system. The payment options should include cash, debit card or credit card and an invoice receipt should be generated for recording the transaction Id that can be used in future auditing. The payment should be calculated for the fixed users, weekly, monthly and yearly users and a session should be used depending on the payment made. For example for the weekly users a session should be creation for 7 days after which the session expires and the customer needs to recharge their account. A checking is done at the entry point and the details of the car and the owner is recorded for the increasing the security of the car parking system.

Database – The data base administrator is responsible for the management of the data residing in the database of the Collins parking car parking system. Separate tables should be used for recording the records of the customers and the payment options such it should be integrated with each other for creating a unified view of the items residing in the database. Foreign key must be used for creating relation between the different tables and joining them to provide an accurate result of the query of the customer. The tables should be created and broken down into third normal form such that the complexity in the database is kept minimum and virtual servers can be used for the development of the database. The use of virtual server helps in backing up the data easily irrespective of the configuration of the physical machine.

Business Rules – The current Collins parking car parking system have different types of customers such as fixed, weekly, monthly and yearly customers and tickets are required to be generated based on the types of the customer. A space should be reserved for the fixed customer and the information system should be designed to record all the details of the customer. The parking fees should be recorded in the database based on the time and a payment gateway should be used for accepting different modes of payment. The information system should be designed for accommodating the changes in the business rules and the tariff plans such that the scalability and flexibility of the system is improved.

Approval

Adaptability – the system should be able to serve the users efficiently and apart from the automation of the entry and the exit barriers some manual process must be involved for handling the emergency conditions such as malfunctioning of the barriers. Installation of more than one barrier at the entry point can also resolve the issue and increase the security of the parking area.

Execution – Barriers should be installed in the entry and the exit point for creating a checking procedure. The activity of the users in the parking system should be recorded with the details of the customer and the vehicle and the user should be notified for each of the procedure maintained in the information system.

Unwavering Quality – Security management is important for securing the information of the car parking system. All the records of the customers must be maintained in the database such a contract should be created with the security companies. The entry and the exit point in the parking system should be secured such that unauthorized users does not have the access and the parking lot is secured from illegal users.

Accessibility – the information system developed for Collins parking car parking system must be available to the users all the time. The maintenance of the information system should be done in the midnight such that the maintenance does not affects the users to access the car park system.

Use Case Description for each of the Use case

Use Case ID	Primary Actor	Use Cases
UC-1	Sensors	Detect Vehicles
UC-2	Sensors	License plate scan
UC-3	Car	Activate entry sensor
UC-4	Car	Activate exit sensor

 

Use Case ID:	UC-1
Use Case Name:	Identification of the parking space
Created By:	Enter your name and student ID
Date Created:	April 17th, 2018
Actors:	The actors are divided into Primary actors and secondary actors. List of Primary Actors – ·         Sensors ·         Camera List of Secondary Actors  - ·         Car ·         Display
Description:	The user needs to be notified about the free space available in the parking lot and a space needs to be allocated to the user such that they can park their vehicle. At the entry point the vehicle is scanned by using the license plate scanner and the information is added to the database about the vehicle and the user. The time of entry should be recorded for calculation of the fare.
Trigger:	The camera sensor starts when the motion detector senses the presence of the vehicle arrives at the entry barrier.
Preconditions:	The following list of activities are performed for the development of the use case: 1. The vehicle enters the car parking system 2. The available parking space is evaluated 3. The sensors should be connected with the information system 4. The data should be stored in the database for storing the information generated from the sensors.
Postconditions:	Different IoT devices must be connected with the network and all the data generated from the devices should be combined to find an appropriate result.
Normal Flow:	The car enters the car parking system through the entry barrier and a verification process runs on the back end of the system. When the car parks into the system a sensor identifies is the database is identified as the space is occupied. In the exit point the data gathered at the entry point is matched and on successful matching the barrier is raised.
Alternative Flows: [Alternative Flow 1 – Not in Network]	On mismatching of the data the barrier not opens and the car cannot leave the parking lot.
Exceptions:	If the IoT device returns error value in the information system then it can cause malfunctioning of the system. Thus a checking should be done for verification of the data and application of the error handling can resolve the problem and increase the efficiency of the car parking system.
Includes:	There are other cases that should be considered or the development of the use case such as limitation of the parking space and generating notification message for the users using the information system.
Frequency of Use:	The system is repeated each time a new vehicle arrives at the entry point of the car parking system.
Assumptions:	The following assumptions are made for the development of the car parking information system. ·         Proper instruction message are displayed on the screen installed at the entry barrier for increasing the usability of the system. ·         The selection of language option must be present such that the user can use the appropriate language of their choice for increasing the flexibility of the system. ·         Proper authorization should be used by the users for accessing the resources of the information system. ·         The database is encrypted with the application of MD5 algorithm such that the customer information are securely stored.
Notes and Issues:	The system can malfunction if the IoT devices generate error values. If any of the IoT devices or the sensors stops working the column in the database should be left empty and the system must be managed manually until the device is repaired.

 

For the development of the car parking information system a software development lifecycle model is needed to be followed. The functional and the non-functional requirement identified for the development of the Collins parking car parking system should be reviewed along with the requirement for designing the activity and development of the model. For the identification of the requirement if the project the current environment of the parking system should be evaluated and the users of the system is needed to be identified. The analysis of the user requirement can be done by arrangement of stake holder meetings with the client and interviewing them for documentation of the requirement. Some assumptions should be made for the system and a prototype of the model should be created for presentation to the stakeholders of the project. The information system should be developed following the five phases of the SDLC model and they are given below:

Planning – In the planning phase the development team identifies the requirement if the client and identifies the needs of the client to develop the information system. This is done by asking questions to the client. An initial project plan is created by the project manager to schedule the activity involved for the development of the project and assigning resources for each of the activity who are responsible for the completion of the task.

Analysis – In the analysis phase the resource list must be evaluated and their availability and the cost should be determined for proceeding with the project. The existing system should be identified and the flaws in the current system should be identified for the identification of the requirement. The analysis is important for the identification of the budget of the project and improve the efficiency of the organization. The replacement that should be made for the current system should be identified and helps in resolving the errors in the project.

Payment

Design – In this phase a preliminary design of the car parking system and the location of the placement of the network and other hardware device are identified. A demilitarized zone should be created for the installation of the server and a firewall should be used for blocking the unknown request. The system is divided into different functional component and developed independently. The independent modules are integrated with each other for creation of a fully functional car parking system. For the development of the information system different hardware and software components are required and it should be listed.

Implementation – For the implementation of the design, the system components are evaluated and the modules prepared are tested for identification of the errors. The modules are integrated with each other for functioning as a combined module and this phase consists of the installation of the physical server, installation of the database, the continuous operation and update is necessary for the expansion of the database and the information system. This is the longest phase of the software development life cycle model and the exceptions and the risk should be evaluated for increasing the efficiency of the final software developed.

Maintenance – In this phase the routine maintenance and management of the database is performed and there are different types of maintenance service that can be performed on the information system such as preventive maintenance, adaptive maintenance, revoking the access permission or addition of new users in the system, generation of usage statistics report. Security auditing, etc.

Atzeni, P., Jensen, C.S., Orsi, G., Ram, S., Tanca, L. and Torlone, R., 2013. The relational model is dead, SQL is dead, and I don't feel so good myself. ACM SIGMOD Record, 42(2), pp.64-68.

Byrne, B. and 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. and Riesco, D., 2015. Translating between Alloy specifications and UML class diagrams annotated with OCL. Software & Systems Modeling, 14(1), pp.5-25.

Evans, A., France, R., Lano, K. and Rumpe, B., 2014. Developing the UML as a formal modelling notation. arXiv preprint arXiv:1409.6928.

Formetta, G., Antonello, A., Franceschi, S., David, O. and Rigon, R., 2014. Hydrological modelling with components: A GIS-based open-source framework. Environmental Modelling & Software, 55, pp.190-200.

Geng, Y. and Cassandras, C.G., 2013. New “Smart Parking” system based on resource allocation and reservations. IEEE Transactions on Intelligent Transportation Systems, 14(3), pp.1129-1139.

Hanumantharaju, M.C., Ravishankar, M. and 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.

Khomtchouk, B.B., Van Booven, D.J. and 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), p.1.

Larman, C., 2012. Applying UML and Patterns: An Introduction to Object Oriented Analysis and Design and Interative Development. Pearson Education India.

Levy, N., Martens, K. and Benenson, I., 2013. Exploring cruising using agent-based and analytical models of parking. Transportmetrica A: Transport Science, 9(9), pp.773-797.

Rosen, M., Lublinsky, B., Smith, K.T. and Balcer, M.J., 2012. Applied SOA: service-oriented architecture and design strategies. John Wiley & Sons.