[Authentic] OKPlate! is an online service that confirms the validity of a Victorian vehicle registration plate.The service enables the user to provide an image of a number plate and receive a spoken response that the plate is valid or in-valid by checking the plate versus registration details.

Assignment 1 – Project Diary
Team Members
Project Goal
OKPlate! is an online service that confirms the validity of a Victorian vehicle registration plate.
The service enables the user to provide an image of a number plate and receive a spoken response that the plate is valid or in-valid by checking the plate versus registration details.
The application is targetedpredominately towards service stations, but can be utilised by toll agencies, parking stations, councils and other companies that require validity of plate identification for their business model.
(example: petrol stations may refuse fuel purchase if plates are invalid).
The core function can be extended by also capturing the vehicle image, to confirm that the make and model of the vehicle the plate is attached to is the same make / model as registered.
A further extension is the indication that the vehicle is recorded as stolen.
Project Value
Value Hypothesis
Enable a real-time service to check for plate validity based on open sourced products and services. Subscribe consumers to the service and introduce a charging model.
Our vision is to provide integration services between consumers and providers.
Our business model is based on transaction volume, extending functionality provided through the service will foster new markets.
The application is similar to the BlueNetsystem utilised by the Victorian police to detect fraudulent drivers which cost $86 million, and also similar to commercial petrol station products to detect fuel theft.
Growth Hypothesis
Providing extensions to the data captured will enable growth into other sectors, and requires planning for horizontal scaling to handle future growth.
Partnering with data providers to act as a sole data broker will solidify market presence and reduce competition. This will require investment in authentication portals and development of charging models.
Lobbying for the right to be the provider of sensitive information will solidify future growth. This will require appropriate security and data classification.
Future extensions involve providing the app as a service, exposing the endpoint instead of the website, thus can be integrated with fixed cameras, point of sales devices etc.
Metrics
We will monitor traffic to the website and application usage. This usage will feed our subscription model. Since this application is targeted towards companies that require valid plate identification, it is not expected that there will be a high volume of individual users utilising the application.
Future functionality may shift the application usage, thus needs to be planned such as public and authenticated access. (e.g.in addition toselect organisations using the service, individuals purchasing a used vehicle on a car site may use the service for validity).
Project Plan
Communication Strategy
Communication between team members will be mainly through Slack and Email.  (show use of of this)
Task Management Strategy
Task management will be performed utilising Trello, this is so that we can keep track of what tasks and stages each of the team members are working on.
(show use of this)
Iteration Plans
The development cycle will follow a rapid application development cycle, where the application will be built in a series of iterations, a function introduced and tested in each integration.
The first 3 iterations below are detailed in the attached spreadsheet.
Iteration 1
Create Mockup Screens (refer attached spreadsheet)
Start Date
02/04/2018
End Date
20/04/2018
Description
The goal here is to determine what functionalities will people need in order to meet their business requirements. Use balsamiq tool to create low fidelity mock-up screens to trial screen flow.
Result
Following mock-up screens prototyped. http://bit.ly/2E4LXnE
Follow Up
Work through screen flow to determine satisfactory path and or need for additional screens / extensions.  Build skeleton application.
Iteration x
Attempt to consume registration plate details (refer attached spreadsheet)
Start Date
9/04/2018
End Date
11/04/2018
Description
Result
As per the architectural decisions we will web scrape the REVS website
Next Step
Include in functionality in the application
Design Thinking Process
Attached is the “Design Thinking Questionnaire”.
Note: Ansley assumed the role of Petrol Station owner and Richard assumed role of Architect / Web developer.
Architecture
Overview
Architectural Decisions
The following technical design principles will be adhered to when developing the OKPlate! system.
Service Oriented: The application will be organised as self contained services in line with the Service Oriented Architecture design p…

Posted in Uncategorized