content 01 System Introduction 02 System Demo 03

  • Slides: 12
Download presentation

content 01 System Introduction 02 System Demo 03 System Security & Scale 04 Summary

content 01 System Introduction 02 System Demo 03 System Security & Scale 04 Summary

Part One System Introduction

Part One System Introduction

Part 1 System Introduction ● This system is aimed to enable passengers, drivers and

Part 1 System Introduction ● This system is aimed to enable passengers, drivers and scheduling managers to use a common application to view bus schedules, routes and book tickets. ● The interface for this system will be a webpage for three different users- passengers, drivers and managers to interact with this system.

Part Two System Demo

Part Two System Demo

Part 2 System Demo http: //g 1. psjconsulting. com/Home/

Part 2 System Demo http: //g 1. psjconsulting. com/Home/

Part Three System Security & Scale

Part Three System Security & Scale

Part 3 System Security & Scale 1. Security issue ● ● ● Access control

Part 3 System Security & Scale 1. Security issue ● ● ● Access control Unsanitized input Encrypted Passwords 2. System scale ● ● For scaling purposes, the limitations rest on the organization and their ability to upkeep and maintain a system of the scale. As users grow, so will the need for higher amounts of memory needed to store the database.

Part Four Summary

Part Four Summary

Part 4 Lessons Learned ● ● A good product plan ○ We understood that

Part 4 Lessons Learned ● ● A good product plan ○ We understood that with a limited timeframe and the restraint of our technical skills, it was for the best interest of ours to keep the application scopes and functionalities to a manageable level. A practical division of work among team members ○ We split our work based on each member's strengths and weaknesses. A good database before implementing functions ○ It is best to have a database that makes sense before starting to implementing functions. Synchronization of teamwork progress ○ When implementing this system, we divided work based on different users. It worked well at the beginning, however, there were some problems when doing pages consolidations.

Part 4 Future Work 1. Managers can delete incidents that has been resolved, Any

Part 4 Future Work 1. Managers can delete incidents that has been resolved, Any incidents that are older than a month and have been resolved will be archived 2. Managers and drivers can set and change their own password; Passengers can login after identity validation and new passengers need to sign up 3. Managers can track the performance of drivers 4. Live track of buses will be shown on the webpage which allow passengers to get precise data about where the buses are located at any given time

demo demo demo demo demo FT 08 Codedemo demo demo demo demo FT 08 Code
OCEAN Demo Nachiket Acharya OCEAN Demo Demo ImplementationOCEAN Demo Nachiket Acharya OCEAN Demo Demo Implementation
BTree Insert and Delete Demo Demo Demo slideBTree Insert and Delete Demo Demo Demo slide
http blogs msdn comcmayo demo demo demo httphttp blogs msdn comcmayo demo demo demo http
OW stelsel Metrokaart DEMO 1 DEMO 2 DEMOOW stelsel Metrokaart DEMO 1 DEMO 2 DEMO
Demo Project reactnative init Demo Project cd DemoDemo Project reactnative init Demo Project cd Demo
Content Strategy Content Strategy Content Strategy Content StrategyContent Strategy Content Strategy Content Strategy Content Strategy
ASUS Demo App Introduction ASUS Demo App PurposeASUS Demo App Introduction ASUS Demo App Purpose
County Website Content Management System Content Strategy CONTENTCounty Website Content Management System Content Strategy CONTENT
APLAWS Content Management System What is content ContentAPLAWS Content Management System What is content Content
T76 4115 Iteration demo T76 4115 Iteration DemoT76 4115 Iteration demo T76 4115 Iteration Demo