Project Design Proposal Grocery Store Essay

Question:

Discuss about the Project Design Proposal Grocery Store system.

Answer:

Overview

Business success is determined by many factors, however, none is as important as adaptability. This outcome necessitates the current system design that was outlined in the previous proposal where, the interface aimed to capitalise on the combination of business with information technology, particularly, e-commerce. Now, this subsequent short report aims to give a realistic approach to the system design.

This report will outline all the necessary parameters needed to achieve an efficient system with an elaborate user interface. For one, the use cases will be provided including the usability of the design. Moreover, the evaluation tactics will be provided to ensure the set targets are accomplished (Usability, 2017).

Scope

An overall approach is proposed, where this report will cover the entire design of the user’s interfaces, from the system itself to the underlying database systems and the security measures. However, the delivery procedures of the products will solely be left for the supermarkets to develop.

Objectives, Outputs and Targets

Capitalising on the benefits of e-commerce is the overall objective where the customers will have an enhanced user experience while making their purchases. Furthermore, through this objective, other functionalities and advantages will be developed such as rewarding, enhanced, simple and helpful user system. However, in spite of the many benefits, the system’s usability will depend on the principles of the designs (Usability, 2017).

User Requirements

Several assessments and evaluation were done to develop the following requirements. These requirements reflect the interests proposed by the envisioned users i.e. customers.

Functional requirements:

  1. A system that develops personalised accounts i.e. create, renew and login to portals.
  2. Enhances user experience through orders made.
  3. A system that distinguished between placed and accepted orders.
  4. An interface with verifiable accounts i.e. purchase made by customers
  5. Geo-location to track users and available stores.

Objectives determined from requirements

Design requirements:

  1. Real-time system with adjustable user libraries to reflect available products.
  2. An interactive system that provide users with a one on one experience.
  3. Geo-location for tracking purposes (Usability partners, 2017).

Outputs and Targets

Outputs:

  1. A collaborative system that enhances business practises through information technology.
  2. An intuitive system with efficient interfaces to meet the customer’s needs (Carleton, 2013).

Targets:

  1. Initial assessment
  2. Interface design
  3. Development through coding
  4. Testing
  5. Final system
  6. Maintenance and troubleshooting

(Liu, 2013)

Use Cases

Actors

Shoppers: New and active customers

Online Shopping:

shopping cart

Delete items, Edit items and Add items

View orders

Authentication and Identity

Purchase

Identity,

Checkout

Identity, payment services

Register new user

Authentication

Success Criteria

Simple techniques will be used to weigh the project’s progress, this will include the development of milestone and their accomplishment. For instance, achieving the interface design on time will serve as a first phase success of the system design (Usability, 2017). Moreover, the objectives identified i.e. helpful, easy, and engaging etc. will also serve as another measure of success.

Key Assumptions

  1. Users are literate and understand the basics of mobile devices as well as the internet.
  2. Users have the necessary technological requirements; internet and devices.
  3. Stores have the necessary support infrastructure.

Design Aims

As stated before adaptability is the key to business success, this business mantra calls for an adaptive system that can satisfy any requirements including the design process itself. Agile approaches can meet this objective easily, where the system design is split into eloquent subsections based on requirements and expertise. Now, the overall design will collaborate the user requirements (from the initial evaluation) with that of the system developers.

Moreover, these user requirements will enhance the templates developed so as to reflect the need of the user. Following the set templates, users’ functionalities through user stories will outline the final interface that again will reflect the users and the design functionalities (Pichler, 2012).


Fig: Design Principle

In the past, agile design has led to systems that meet varying user requirements, for instance, online retail stores such as Amazon and E-bay vary their system outlook based on the current market environment which is met through agile designs. In essence, the business can adjust user variables and implement them based on designer’s expertise.

Design Outline

Based on the established design, i.e. the proposed wireframes having 4 major interfaces

  1. System design
  2. Development of the initial interfaces
  3. The Login screen – Access to personalised accounts.
  4. Home/ selecting a grocery store – an interface to choose the desired grocery store.
  5. Grocery store – An elaborate map with all active stores.
  6. Shopping – interface where the purchases are made.
  7. Database – supporting the interface with the underlying data.
  8. Testing – assessment to evaluate the functionalities.
  9. Deployment and maintenance.

Proposed Evaluation Methods

In general, usability data from the proposed tests will be captured and analysed to develop conclusive results. These results will then establish the rate of success, however, a simple evaluation plan is proposed.

  1. The first click test – to determine what draws to the users to the system.
  2. The usability test – to test the practicality of the interfaces.
  3. System usability scale (SUS) – A test that outlines the system’s efficiency, usability and objective accomplishment.
  4. Final, expert reviews – presenting the designs to renowned experts to test for different functionalities (Usability, 2017).

References

Carleton. B. (2013). Real-time User Interface Design. Retrieved 08 March, 2017, from:

Liu. S. (2013). Building Online Shopping Website Based On ASP.NET and SQL Server. Retrieved 28 February, 2017, from:

Pichler. R. (2012). Agile user interface design. Retrieved 08 March, 2017, from:

Usability partners. (2017). User requirements analysis. Retrieved 28 February, 2017, from:

Usability. (2017). User Interface Design Basics. Retrieved 28 February, 2017, from:

How to cite this essay: