DMV System

Prototyping Technique

Evolutionary Prototyping

The DMV will require a system that will continuously adapt to an ever changing environment and one that will contain sufficient redundancies to mitigate failure and give consistent results.

The prototyping technique we will use is Evolutionary prototyping.

Under this technique, a robust system that will form the main structure of the new system will be designed and constantly refined, rebuilt and new features added to it. The aim of this is to improve on the system and to accommodate redundancies. This prototyping technique will allow the software to continuously mature as the usage environment changes (Carter, Antón, Dagnino & Williams, 2001)

Evolutionary prototyping will also allow the addition of new technologies over time, creating a system that is immediately responsive to the environment. 

This will be advantageous in two ways:

  1. The software is made up of two main components – the customer self-check-in and the receptionist check-in. This technique will allow the software to evolve continuously over time to accommodate new changes in the technological field thereby giving a seamless experience to the customer (Hilton, Hughes, Little & Marandi, 2013).

This technique will allow new features to be added into the receptionist check-in over time in response to new developments within the laws governing the DMV.

  1. The core of the system will be constantly refined during the design process by taking into account constant inputs from the DMV and all personnel involved in the process. This will result in a robust system that will be implemented immediately after completion.

 

Management Plan

Project Objectives 

To create a system that allows customer self-check-in during rush hour

To create a software system to allow receptionist to check-in the rest of the time

Actions

To implement the program objectives listed above, we will

  1. Create a customer self-check-in system for busy times
  2. Create a receptionist check-in system for use the rest of the time

Personnel

Supervisor – will be charged with ensuring smooth running of the project from start to finish.

Programmers – will create the main system to handle both the customer and receptionist check-in

User interface designer – will design the user interfaces for the customer and receptionist check – in.

Collectively, the personnel will perform testing on the project and will conduct a commissioning session at the time of handover

Stages of implementation

Stage 1 – allocation of personnel to duties and establishing chain of command

Duration – 1 day

This will involve allocating specific duties to the employees based on their qualifications and job description.

 

Stage 2 – timeline design

Duration – 1 day

Deciding and designing the timeline of the software design with specific deliverables after certain durations. At this stage the management team will come up with a log frame containing the actionable timeline for coming up with the software (Chaffey & White, 2010).

Stage 3 – software system model design

Duration – 3 days

All parties involved in the software design will meet and agree on a proper evolutionary prototype design that will suit the project

Stage 4 – data collection and database design

Duration – 2 weeks

The management team will visit the DMV to collect data that will be required. The programmer and the user interface designer will create the database and determine data access and control protocols during this stage (Chaffey & White, 2010).

Stage 5 – Software design

Duration – 2 weeks

During this stage, the programmers will work in constant collaboration with the supervisor and the rest of the software design team to write the required code to handle both the customer and the receptionist check-in systems. At this stage, the bulk of the software will take shape and redundancies will be designed into the system.

 

Stage 6 – user interface design

Duration – 1 week

At the end of software design phase, the user interface designer will design the appropriate interfaces for both checks – in systems then append them to the software and the databases created at stage 2

Stage 7 – design of process handling future software modifications

Duration – 1 day

At this stage, the management and all parties involved in the software design will meet and come up with the procedures that will be used to handle future software modifications.

Stage 8 – Software testing

Duration – 1 week

The final system will be tested to check for robustness, response to external environment and to detect any bugs and debug

Stage 9 – software commissioning

Duration – 1 week

The team will hand over the software to the DMV and train both the staff and customers on how to effectively use the software.

Customer check-in Receptionist check – in
Only activated during busy times Always active
Highly interactive Less interactive
Low lever access protocols High level access protocols

 

Leave a Reply