Notes

CERTIFICATE

This is to certify that the Minor Project entitled "EZ Safe Parking" is the bonafied work done by Rishav Srivastva (1806504),Sharanya Sharma (1806420),Urja Sahay(1806534), Vipul Shukla(1806448) during 2021-2022 in partial fulfillment of the requirement of the 3rd Semester Minor Project of Bachelor's of Degree(B.tech), in KIIT University,Bhubaneshwar, under our supervision and guidance of our teacher Sarita Tripathy.



ACKNOWLEDGEMENT

I would like to whole heartedly thank and express my sincere gratitude to Mrs Sarita Tripathy for her constant encouragement in the development of this Minor project.I extend my sincere thanks to all the faculty members of the department, for their continuous encouragement, guidance and support throughout the development of this Minor Project.


ABSTRACT

Now–a– days in all the cities in India face severe parking problems. Off street parking is common in all Organizations, big shopping malls and theatres and huge offices which are used by employees & customers, on the other hand on-street parking is traffic problem causing as the parking is directly controlled by market forces, with individual parking and hence has high demand. With this facility the end user will be provided with a wide range of user-friendly parking facilities in all major organizations of various cities. The user can book the parking slot through online. This service is continually provide the highest levels of customer service at every location, ensuring every experience. Achieving this has been one of the key factors in making Secure Parking. With this everyone will have no parking worries.



DATA FLOW DIAGRAM

A data flow diagram is a graphical tool used to describe and analyze movement of data through a system. They are the central tool and forms the basis from which the other components are developed. The transformation of data from input to output may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movements of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams.The development of DFD’s is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The top level diagram is often called context diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD. The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail is described for analyst to understand the process. Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical form, this lead to the modular design. A DFD is also known as a “bubble Chart” has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system.
DFD SYMBOLS
In the DFD, there are four symbols
1. A square defines a source (originator) or destination of system data.
2. An arrow defines data flow. It is the pipeline through which the information flows.
3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data.


CONSTRUCTING A DFD
There are several rules of thumb that are used in drawing DFD’s. They are:
1. Process should be named and numbered for an easy reference. Each name should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD, it is marked with a short diagonal.
3. When a process is exploded into lower level details, they are numbered

RULES GOVERNING THE DFD’s
PROCESS
1. No process can have only outputs.
2. No process can have only inputs. If an object has only inputs then it must be a sink.
3. A process has a verb phrase label.
DATA STORE
1. Data cannot move directly from one data store to another data store, a process must move data.
2. Data cannot move directly from an outside source to a data store. Data must be moved by a process that receives data from the source and places the data into the data store.
3. Data cannot move directly to an outside sink from a data store. Data must be moved by a process.
4. A data store has a noun phrase label.
SOURCE OR SINK
1. Data cannot move directly from a source to a sink. It must be moved by a process.
2. A source or sink has a noun phrase label.
DATA FLOW
1. A data flow has only one direction of flow between symbols. It may flow in both directions between a process and a data store to show a read before an update.
2. A fork in a data flow means that exactly the same data goes from a common location to two or more different processes, data stores, or source/sinks.
3. A join in a data flow means that exactly the same data come from any of two or more different processes, data stores, or source/sinks to a common location
4. A data flow cannot go directly back to the same process it leaves.
5. A data flow to a data store means update.
6. A data flow from a data store means retrieve or use.
7. A data flow has a noun phase label.