Concept Model for Application

Added on - 16 Sep 2019

  • 16

    pages

  • 1769

    words

  • 90

    views

  • 0

    downloads

Showing pages 1 to 4 of 16 pages
PrototypeStudent Name:Student ID:Course Name:Course ID:Faculty Name:University Name:
Table of ContentsSection I.....................................................................................................................................2Concept Model for Application.............................................................................................2Usability Concepts.................................................................................................................2Operationalizing Usability Concepts.....................................................................................2Task Allocation......................................................................................................................3Section II....................................................................................................................................4Initial Interface Specification.................................................................................................4Low Fidelity Prototypes.........................................................................................................4Mobile................................................................................................................................5Desktop..............................................................................................................................6Quick and Dirty Initial Empirical Evaluation........................................................................7Interface Specification Modification......................................................................................8High Fidelity Prototype..........................................................................................................8Mobile................................................................................................................................9Desktop............................................................................................................................12Quick and Dirty Empirical Re-evaluation............................................................................13Interface Specification Modification....................................................................................14Section 3...................................................................................................................................14Critical Evaluation, Reflection and Prototyping Role..........................................................14
Section IConcept Model for ApplicationThe web and mobile app that will be developed is a utility app. It will help the users identifythe nearest ATM in a particular area. The ATM locater will show any ATM in the nearestarea. Also, it will show whether there is cash in the ATM.Usability ConceptsThe application will be used by the people who are travelling or are looking for ATMs atlocations where they never travelled before. One of the issues that will be resolved by this isthat the user will know whether an ATM has cash or not and only then they will go to it. Itwill save their time. The application will be easy to use with minimal features. The key ideawill be to locate the ATMs and show whether it has cash. Users have to register into thesystem for once using their email address or mobile number.Operationalizing Usability ConceptsThree things will be in consideration, first is mobile application, web application accessiblethrough browsers, and use of geocaching service. The system will work in the followingmanner:1.User 1 need to withdraw cash.2.User identifies an ATM3.User reaches and finds cash in it, he updates app showing available cash4.Another user reaches same ATM, see cash empty, updates status as no cash5.The cash update will be updated on the map visible to all the other users.
6.User will get points for updating, and cash withdrawal which can be redeemed laterfor online items.Task AllocationThe mobile application and web application will have similar functionalities. Both will usethe users’ device location to locate the users’ current location. Both the system will haveminimal design with just one key purpose and that is to show ATM location and cashavailability. The mobile and the web applications that will be developed will work in sync.Any information update by the user on one platform will be shared to another platformthrough the common server. This will ensure that once a user reaches an ATM and withdrawsmoney, then the point earned can be found at the same level even on the web application. Theuser can also locate any ATM using web based application and then update the informationusing their mobile application. This integration will ensure seamless experience to the user.The table below shows the tasks that will be performed by each of the system. As visiblefrom the table below, the tasks that are performed by both the applications are almost similar.The only difference is that the mobile application will assist in getting phone notification bythe users in case of any updates in points or ATM status. If the user is only active on the web-based application, then an email will be sent to the user for any update.Mobile ApplicationWeb-based ApplicationAllow log in and logoutAllow log in and logoutForgot PasswordForgot PasswordShow ATM locationShow ATM LocationGain PointsGain PointsSend to ServerSend to ServerUser ProfileUser ProfilePhone NotificationEmail
desklib-logo
You’re reading a preview
card-image

To View Complete Document

Become a Desklib Library Member.
Subscribe to our plans

Unlock This Document