Skip to content
saurabh1965 edited this page Oct 5, 2019 · 1 revision

Welcome to the Titans wiki!

Hackathon 2k19

Problem on parking management system.

Table of content

Introduction
  • Purpose
  • Document conventitions
  • Intended audience and reading suggestions
  • Scope
Overall description
  • Product perspectives
  • Product features
  • Characteristics
  • Operating Environment
External interface requirements
  • User interfaces
  • Hardware interfaces
Non functional requirements
  • Software quality attributes

Introduction

The purpose of this project is to build a parking management system to ease the parking facility.And to retrieve the details of the vehicles.
  • Document conventions
    This document uses the conventions
  • db-Database
  • Intended audience and reading suggestions:
    it is a prototype of parking management system it is applicable within the college premises. This has been implemented under the guidance of college professors. This project is useful for the parking management team and as well as to the faculty and students.
  • Project scope
    The purpose of the parking management system is to ease parking management and to create a convenient and easy-to-use application for users, trying to get the proper arrangements. The system is based on a relational database with its parking management and providing individual spot functions.

Overall description

  • Productive perspectives
Vehicle details
It contains the vehicle number.
Owner descriptions
It contains the vehicles owner name and phone number.
Spot description
It contain which spot is provided to the owner of the vehicle.
  • Product features
    Name,phone no., spot, vehicle no..
  • Characteristics.
    Proper utilization of the time.
    Reduces the workload of the user.
    Environment friendly.
    Increases the security of the vehicle.
  • Operating environment
Operating environment for the Parking Management system is as listed below.
  • Operating system: Windows.
  • Database:sq-lite
  • Platform:Android studio.

External interface requirements

  • User interface
Front-end software: Android studio version 3.2
Back-end software: Android studio (sq-lite)
  • Hardware interface
Windows.
A browser which uses java and sq-lite(Android studio).

Non functional attributes

Software Quality Attributes
  • AVAILABILITY: The vehicle should be available on the specified spot and specified time as many vehicle owners are doing advance reservations.
  • CORRECTNESS: They should reach at start from correct start terminal and should reach the correct spot.
  • MAINTAINABILITY: The security in chargers should maintain correct schedules of vehicles.
  • USABILITY: The spot schedules should satisfy a maximum number of owners needs.

Clone this wiki locally