Challenge Summary
We are excited to see your wireframes for this challenge!
Round 1
Submit your initial wireframe solution for checkpoint feedback
A. Client User Requirements:
01 Client Dashboard
02 My Orders/ Service Requests
03 My Deliverables
B. Drone Operator:
01 Drone Operator Dashboard
02 My Tasks
03 Mission Situation Board
Notes.jpg: Any comments about your design for the Client.
Round 2
Submit final wireframe solution plus checkpoint feedback.
A. Client User Requirements:
01 Client Dashboard
02 My Orders/ Service Requests
03 My Deliverables
04 My Order Templates
05 My Profile
B. Drone Operator:
01 Drone Operator Dashboard
02 My Tasks
03 Mission Situation Board
04 My Tools
05 My Drones
06 My Qualification(s)
07 My Profile
Notes.jpg: Any comments about your design for the Client.
In this challenge, we are looking for your help in coming up with wireframes for remaining users of the drone application.
Wireframe Considerations:
- Please have the provided wireframes as base for this challenge, you need to build upon that
- Follow the resolution from existing wireframes!
- Your Wireframes should follow the same layout and structure as the previous wireframes, just tailer for the experience and interactions for each unique user type below.
- Make sure you organize each user type wireframes correctly so that it's clear what wireframes belong to each user type. This is VERY important. If we are confused about your organization you will not score well in this challenge.
User Persona:
Think on who is interacting with whom and put yourself in the respective actor’s role and you should get the right ideas on the needed web views for the business use cases.
- Client interacting with Service Provider
- Service Provider interacting with Client
- Servicer Provider interacting with Drone Operator
- Drone Operator interacting with Service Provider
Suggested Screens:
Below are the list of functionalities each of the users will be performing.
NOTE: You are not limited to the screens listed below, feel free to add any screens that are required to show the flow of your concepts.
A. Client User Requirements:
01 Client Dashboard:
We don't have the complete requirements of what the Client Dashboard will include in total. However, we can get a rough start on what this will look like.
- My Orders
- My Deliverables
- My Profile (Global Item)
02 My Orders/ Service Requests:
Need to see a list of orders with status/ tabs for different Order progress:
- New/ Pending
- Accepted
- Rejected
- In Progress
- Completed
- Archived
The Client needs to be able to do/ see:
- Create Order (option to select an Order Template)
-- Service Request Id (DSP)
-- Client Id (DSP)
-- Service Provider Id (Select available)
-- Service Request Date (date/time) (input)
-- Service Type (select based on selected SP) (input)
-- Service Sequence (single, repetitive, ...) (input)
-- Service Request Status / History (DSP)
-- Area of Interest (location, area) (input)
-- Deliverables (type, format, quality, content) (input)
-- Deliverables Date (date/time)
-- Deliverables Consumer (electronic) Address (input)
-- Payment Type
-- Additional info (free text or upload of info "pdf")
- View Order Detail/ Edit Order
- View Order Progress
- View Deliverable(s) (Takes user to 03 My Deliverables)
- Delete Order
- Archive Orders (Completed Orders)
03 My Deliverables:
(View Final images, video, etc. from Completed Order)
- View Deliverables
04 My Order Templates:
Order templates consist of frequently used/ recurring data. Using the same Drone Service Provider ID, Same Service Type, Same Area of Interest, etc.
- Manage Order Templates
- View/ Edit Order Templates
05 My Profile:
- View/Edit Profile Information
B. Drone Operator:
01 Drone Operator Dashboard:
- My Tasks
- My Tools (placeholder content is fine)
- My Drones
- My Profile
- My Qualifications
02 My Tasks:
- Tasks
- Task Details
-- Task Name
-- Task Id
-- Service Request Id
-- Service Provider Id
-- Drone Operator Id
-- Drone Type/Id
-- Sensor Type
-- Mission StartDate
-- Mission EndDate (date/time)
-- Mission Type
-- Mission Sequence (single, repetitive, …)
-- Mission Status / History
-- Area of Interest (location, area)
-- Deliverables (type, format, content, quality)
-- Deliverables Date (date/time)
-- Approved Flight Plan Id
-- Drone Checklist Log (Id/file)
-- Executed Flight Plan Id
-- Drone Data (recorded mission data) (Id/files)
-- Flight Log (Id/file)
-- Additional info (free text or upload doc (pdf))
- Accept/ Reject Task
- Submit Delivery of Task
-- Upload Service Report/Deliverables
03 Mission Situation Board:
Client Wireframes User this as a starting point. (The Mission Situation Board is the monitor/ screen of In-Progress Tasks)
- Receive Command & Control Drone Operator Activities/Mission for a Task (will receive the following Mission C2 from the Service Provider)
-- Confirm mission / Take-off release
-- Mission abort - go to next emergency landing
-- Mission abort - return to Home
-- Mission alert
-- Mission warning
- Submit drone mission execution/flight status (The Drone Operator will submit the following drone mission execution/flight status information to the Platform)
-- Confirm pre-flight checks / ready for take-off
-- Confirm airborne
-- Confirm ready to land
-- Confirm landed
-- Cancel, emergency alerts, flight diversions, connectivity lost
- Provide and perform (record) Pre-Flight/Run-up checks
- Provide and perform (record) Post-Flight checks
- Upload/receive and store Flight Plans
-- The platform shall enable the Drone Operator to upload and store the flight plan(s) generated -- The platform will store the flight plan(s), linked to the corresponding Drone Operator Task.
-- The platform will support the upload of two flight plans per task/mission: (1) the flight plan to be approved and (2) the flight plan executed for the mission
- Upload/receive/store drone data (flight log, flight telemetry)
-- The DO shall be able to upload and store the drone data (flight log, flight telemetry)
-- The platform will link the uploaded data to the corresponding drone operator task.
- Upload/receive/store drone data (recorded mission data)
-- The DO shall be able to upload and store the drone data (flight log, flight telemetry)
-- The platform will link the uploaded data to the corresponding drone operator task.
04 My Tools:
- Just include this screen/ navigation item as a placeholder for now
05 My Drones:
- Drone information and details
- Can reuse a lot of the same data and layouts for Drones found in the Service Provider Wireframes
06 My Qualification(s)
- Create and maintain the qualification/certification records
- Based on the Drone Operator's qualification requirements and the qualification records, the platform will provide a notification for qualification/certification renewal.
07 My Profile:
- View/Edit Profile Information
Challenge Resources:
Service Provider Wireframes (Attached)
- User these wireframes as your base for layout, general user flows, and organization of content
- Include a new set of wireframes for each user (Client and Drone Operator) based on these
Mission Situation Board:
https://drive.google.com/file/d/0B6kvOdxpqnKMcldoUWltMU5uakk/view?usp=sharing
- These are a set of quick wireframes from the client to explain their thinking for the Mission Situation Board for the Drone Operator user.
- use these wireframes a base
Target Audience
- Client, Drone Operator B2B
Learn Axure
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/support
Judging Criteria
- User Experience of the application/portal
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Wireframes should be built in HTML or Axure
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.