Code Monkey home page Code Monkey logo

fyp-smartkart's Introduction

FYP-SmartKart

Report(s) and Artefact for my Dissertation Project.
Prior to my graduation, this repository was private.
After Graduation, I publicised this repository.

Under Documents you will find the .tex and associated files for the PID and Report, as required for the submission.
These are initially licensed under CC-BY-SA-4.0; however the University may require me to change this License or otherwise "unpublish" that section.

Under Artefacts you will find the source tree for the app that I am making as part of this Dissertation.
This is licensed under the Apache-2.0 license.

Further details are given in READMEs in these folders.

fyp-smartkart's People

Contributors

fisherthewol avatar

Watchers

 avatar

fyp-smartkart's Issues

Testing of UI and UX.

During the development of the UI and UX, they should be tested as much as is possible without the backend; this task can continue during development of the backend.

Creation of any Glue Code necessary.

Glue Code may be needed for a myriad of reasons, including but not limited to:

  • Changes to build tools
  • Needed code for publication to android app stores (e.g. Google Play Store or F-Droid).

Delivery.

The artefact (application) and final report should be delivered under this milestone.

Mis-use of units.

Output is in m/s but displayed as MPH; need to convert on display.

Plan the UX (User Experience).

Similar to the UI, the UX should be planned before implementation, taking pointers from relevant sources on how best to do so.

Plan the UI Design.

The User Interface design should be designed and revised, with reference(s) to relevant sources on the subject, before implementing the design in code.

Evaluation of potential Datasets.

There may or may not be datasets of average speed check zones, or it may be necessary to create one. This must be evaluated, and a dataset decided.

Implement UX.

Alongside implementing the UI, the UX must also be implemented.

Design of Data Model.

Any dataset used will need some form of wrapping for use within the application. This wrapping will need to be implemented in code, but before that it should be designed.

Testing of the Algorithm

The algorithm should be tested throught it's development. There is scope to do integration testing with the UI and/or conitinuation of #7.

Final Bug Fixes

Bugs may "appear" at the end of the project, that require fixing.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.