The Automated PIEAS Transport System Proposal-Implementation and Application in Computer Sciences-Project Report, Study Guides, Projects, Research of Applications of Computer Sciences

Download The Automated PIEAS Transport System Proposal-Implementation and Application in Computer Sciences-Project Report and more Study Guides, Projects, Research Applications of Computer Sciences in PDF only on Docsity! 1 Automation of PIEAS Transport system Perspective The Automated PIEAS Transport System will be an internet based application. It will provide user-friendly interfaces and easy access to information. It could be accessed by a large number of users simultaneously. A DBMS will be working behind the web server on which this product will be installed, to manage the large amount of data. A GUI will also be developed for users, which will help the users to know the details about the desired vehicles and required information will be delivered to the user. The Automated PIEAS Transport system will be a free of cost web based application. It is meant to entertain the users to get information easily with in no time. The aim behind the development is to enhance the recital and to reduce the processing time for retrieving the preferred details. This web based application will quickly facilitate the users with accurate and updated information, the details provided for the vehicles, the timings regarding routes and information about the passengers will be precise and flawless since the system administrator will keep the system up to date. 1.1 Design Goals The purpose of this document is to provide detailed requirements specification for the project titled “Automation of PIEAS Transport system”. This document is aimed to provide an overview of different requirements, constraints, and functionalities of the intended system. The documentation of requirements will be helpful, as it provides all the necessary aspects that the developer needs to keep in mind during the course of development. 1.2 Scope of Automated PIEAS Transport System This proposed Automated Transport system will be a web based interface accessible by the users, in and outside of PIEAS. The business goals of the system are To provide such a service to users to interact with the Transport Department through the web interface. To reduce the processing time. To enhance the recital by providing required details in less time. docsity.com T o enable the organization to have a reliable record of resources and their due utilization. Automated PIEAS Transport System is a free-of-cost, web-based system. It’s meant to allow users to quickly and easily get the information. Automated PIEAS Transport System (PTS) will reduce the processing time. This was the main lingering factor in request processing because of Student-Transport department interaction. This system will enhance the performance by providing required details in time. This will also enable the organization to have a reliable record of resources and their due utilization. docsity.com o Activity diagrams 7th Semester Final Work Following work is completed after the midterm presentation. Normalization Database Implementation Software design and implementation docsity.com 4 Normalization Mapping of Entities Simple attributes are mapped directly onto the relation. Simple attributes are used in order to map component attributes. A separate relation with a foreign key taken from the superior entity for the multi-valued attributes. UserRecord User_ID adminID UpdateDetails Administration SA_ID FirstName LastName JobDetails Password Transportation_ Records TransportationID adminID UpdateDetails Transportation TransportationID TransportationDetails Vehicles VehiclesID MaintenanceDetails MaintenanceDate MaintenanceCost Drivers DriverID FirstName LastName ContactNo. JobDetails Users User_ID UserDetails Password UsageRecord docsity.com User_ID route_ID UsageDetails Charges Mapping Relationships Holds For One-to-Many relationships Primary key on the one side becomes a foreign key on the many side. User_ID UserDetails Password User_ID adminID UpdateDetails User_ID Update SA_ID FirstName LastName JobDetails Password User_ID adminID UpdateDetails User_ID SA_ID Updates SA_ID FirstName LastName JobDetails Password TransportationID adminID UpdateDetails SA_ID docsity.com  No partial functional dependencies All the relations are in the Second normal form. So there is no need to change any relation Third Normal Form  2NF PLUS no transitive dependencies (functional dependencies on non-primary- key attributes)  The primary key is a determinant for another attribute, which in turn is a determinant for a third.  Non-key determinant with transitive dependencies go into a new table. Non-key determinant becomes primary key in the new table and stays as foreign key in the old table All the relations are in the third normal form. So there is no need to change any relation docsity.com 5 Database Design and Implementation: Relational model is used for the design and implementation of PIEAS Transport System Database. The Relational schema and the tables constructed are given below: 5.1 Entity Relationship Diagram Figure 1 ER diagram docsity.com Description of ER diagram An entity-relationship (ER) model is a specialized graphic that illustrates the interrelationships between entities in a database. There are two basic components comprising an entity relationship diagram, entities and relationships. Entities in PTS There are seven major entities in the PTS. The role and description of the Entities is described below. USER A User is any person who accesses the system. He/she cannot change their details at their will if there is any change required on part of users the administrator will modify the records and the report about the up-dation of UserRecords will be stored. ADMINISTRATOR It comprises all people in-charge of running and maintaining the system. It may include either Database Administrator or the system administrator but both will have different job descriptions and access rights. USER RECORD This entity holds the records of the USER starting from the creation of the user. USAGE RECORD This entity holds the record of the usage of transportation by the user. The records for this will be based on requests made by the users for availing the transport facility. DRIVERS This entity encompasses all the drivers for all the vehicles working currently for daily services in the organization. Driver entity counts collectively on all the drivers for route buses and staff duty vehicles. VEHICLES This holds all the vehicles being used in the transport department currently. docsity.com Figure 3 USER_RECORD Table 3. DRIVERS TABLE: CREATE TABLE DRIVERS_T ( DRIVER_ID VARCHAR(255), FIRST_NAME CHAR(20), LAST_NAME CHAR(20), JOB_DETAILS VARCHAR(255), CONTACT_NUMBER INTEGER NOT NULL, CONSTRAINT DRIVERS_PK PRIMARY KEY(DRIVER_ID)); Figure 4 DRIVERS Table docsity.com 4. ADMINISTRATOR TABLE CREATE TABLE ADMINISTRATOR_T ( ADMIN_ID VARCHAR(255)NOT NULL, FIRST_NAME CHAR(20), LAST_NAME CHAR(20), JOB_DETAILS VARCHAR(255), PASSWORD VARCHAR(20) NOT NULL, CONSTRAINT ADMINISTRATOR_PK PRIMARY KEY(ADMIN_ID)); Figure 5 ADMINISTRATOR Table 5. VEHICLES TABLE CREATE TABLE VEHICLES_T ( VEHICLE_ID VARCHAR(255)NOT NULL, VEHICLE_ROUTE VARCHAR(255), docsity.com VEHICLE_TYPE VARCHAR(255), MAINTENANCE_DETAILS VARCHAR(255), FUEL_RECORD VARCHAR(255), MAINTENANCE_COST DECIMAL(6,2), MAINTENANCE_DATE INTEGER, CONSTRAINT VEHICLES_PK PRIMARY KEY(VEHICLE_ID)); Figure 6 VEHICLES Table 6. TRANSPORTATION TABLE CREATE TABLE TRANSPORTATION_T ( TRANSPORTATION_ID VARCHAR(255)NOT NULL, TRANSPORTATION_DETAILS VARCHAR(255), docsity.com CONSTRAINT DRIVES_PK PRIMARY KEY (DRIVER_ID,VEHICLE_ID)); ‘Diagram - D¥N..PTS.Diagram, . Summary — Colmnflae == Condensed Type © Nlatle. «== Data Type» Lerath Identity Destintion DRIVER 0 varchar 258) No vacharess) =e] 9 VENICE varchar 258) No vacharess) «= es] | FUEL DETAILS varchat(5) Yes vata) =O] | oaTE tattine Yes dette a Oo O Figure 10 DRIVES Table docsity.com  5.3 Diagram Following diagram explains the interaction, the syntax is given in the appendix A. Figure 11 Database Diagram docsity.com 6 SOFTWARE DESIGN AND IMPLEMENTATION 6.1 LOGIN FUNCTIONALITY In this section, the LOGIN functionality has been explained. The purpose of login functionality is to allow only the authenticated users to access the PIEAS Transport System. This functioanlity makes the system more secure. Only the concerned and authorized persons will be able to access the PTS. Any user who wants to login the system has the provide its specific User ID and password, the ID and password will be comapred with those records that are already available in the systems database. The psuedocode for the login functioanality I guven below PSUEDOCODE: TRY to Open the Connection Execute the reader Read/loop all the records in DB Compare password with DB records IF The password matches Redirect the User Else Show the message “Invaid User” Close Reader Close Connection. docsity.com