Muserium Application Prototype: Design, Evaluation, and Implementation

This document details the development and evaluation of a Muserium application prototype. The project focuses on designing a mobile application for museum navigation, ticket booking, and information access. The prototype, created using Justinmind, includes key screens such as login, registration, ticket booking, a collection view, and a map. The design is based on an iPhone-X screen, and the evaluation methodology involves testing with a group of users, including designers and novices, to assess usability and gather feedback. The limitations include the incomplete design with missing pages and the lack of a fully functional application. The evaluation plan outlines the test scenarios, process, and data collection methods to assess user interaction and satisfaction. The project highlights the design process, implementation details, and evaluation strategies for a museum application.

System UI
Development
Name of the Student
Name of the University

Design Statement
• The design of the application is done based on the
museum
• The design is done on a mobile phone screen (iPhone-X)
• The project will scope will be developing a responsive web
application
• This responsive web app can be access from any modern
web browser

Implementation - Tool
• The tool selected for developing the prototype is
Justinmind
• This tool allows developing from wireframes to highly
interactive prototypes
• Fully-interactive prototypes can be done very easily in
Justinmind
• The designs can be done from scratch
• This tool supports visual design, web interactions and
mobile gestures

Implementation - Process
• The iPhone-x was chosen as the screen base
• A background is added and locked in position
• Text input forms are added with messages inside those
• Various form elements has been added and size adjusted
• Common elements for every screen is added in master
page

Implementation – Prototype
Details
• The prototype has five screens
• Login screen is for showing login form
• Registration page is for showing registration form
• Ticket booking is for booking form
• The user can see the contents of the museum in view
collection screen
• The exhibit map can be seen in map screen

Implementation – Screens

Evaluation - Condition
• Ten people will be hired to test the application
• Three of these people are application designer
• Three of them have good understanding of applications
• Four of them are novice in terms of application utilization
• The test will be conducted in the mobile devices
• The users will be informed about what the application is
about

Evaluation – Test Scenarios
• Login to the website
• Registering to the system
• Going back and forward to login and registration page
• Accessing the map
• Booking a ticket
• View the collection

Evaluation – Process
• All the users will be invited at the same time
• One responsible person will be interacting with one group
of users
• The analyst will collect data by observing how easily the
user is accessing the system
• The user will fill a feedback form and submit to the
analyst

Limitations
• The design does not include all the pages of the
application
• Implementing a efficient navigation was not possible due
to lack of screens
• The user cannot actually use the application as real one
• The interfaces will differ from what the actual system will
be