Challenge Summary

Welcome to HP Data Quality Landing Zone Web Application Wireframe Challenge

The objective of this challenge is to create the HP Data Quality Landing Zone Web Application based on requirements and guidelines stated on challenge details.

You need focus on delivering top notch features, ease to use application also present the best practice for responsive web application.

Round 1

Submit Initial HP Data Quality Landing Zone Web Application Wireframe submission for these following screens:
1). Login
2). User Profile
3). Dashboard
4). Job List

Round 2

Final HP Data Quality Landing Zone Web Application Wireframe submission for these following screens:
1). Login
2). User Profile
3). Dashboard
4). Job List
5). Job Detail/Edit
6). Job Setup/Creation
7). Recently Completed File Transfer Jobs
8). Currently Running File Transfer Jobs

Design Problem
The HP Data Quality team receives large amounts of data on a regular basis from various sources - manufacturing processes, customer surveys, internal customer service statistics, etc. They would like to develop a file transfer and monitoring tool that alerts internal resources when files arrive and then transfers those files to alternative locations within their infrastructure. The Landing Zone app will designate a folder for incoming data for each data source or data type and then a destination where it will be transferred. Often HP Data Quality personnel are moving files between regular and HDFS file systems.

General Requirements
- This is going to be a responsive web application. Keep this in mind in your approach.
- Need able to drill down all the pages flow.
- Submit Desktop Screen Size for this challenge (1024px x 768px)

Submission Requirements
1). Login

- Users will authenticate with basic authentication.

2). User Profile
- Users will provide email address for notification purposes.  
- There will be two types of users: Admin Users and Normal Users.
- Admin Users will be able to see all jobs in the system.

3). Dashboard
- Displays summary statistics about currently running file transfer jobs
- Displays summary statistics about recently completed file transfer jobs

4). Job List
- Display Job Name (Clicking on Job Name should navigate users to Job Detail)
- Job Tags
- Source IP/DNS
- Source Path
- Destination IP/DNS
- Destination Path
- Last Completed Delivery
- Next Scheduled Pickup (if applicable)

5). Job Detail/Edit
- Display Job Name (Clicking on Job Name should navigate users to Job Detail)
- Job Tags
- Source IP/DNS
- Source Path
- Destination IP/DNS
- Destination Path
- Last Completed Delivery
- Next Scheduled Pickup (if applicable)
- Allow users to change monitoring settings
- Allow users to add notifications
- Allow users to tag a job
- Allow users to designate transformation jobs to be executed.

6). Job Setup/Creation
- Designate a user-friendly name for the job
- Configure landing zone for a particular file type or data source (designate a folder on the current server.)
- Allow users to create new folders on the system.  
- Designate a target IP address and a destination directory for the files.
- Allow for configuration to write to Hadoop-based file systems.  The destination folder output process should include the following parameters
-- Is HDFS Destination? (checkbox)
-- Hadoop Distribution (dropdown) (display if Is HDFS Destination? = true)
-- Hadoop Version (dropdown)  (display if Is HDFS Destination? = true)
-- URL (text field:  e.g. “hdfs://localhost:9000)  (display if Is HDFS Destination? = true)
-- Use Datanode Hostname (checkbox)  (display if Is HDFS Destination? = true)
-- User Name (text)  (display if Is HDFS Destination? = true)
-- Compress Data? (checkbox)  (display if Is HDFS Destination? = true)
-- Compression Type (dropdown - GZIP | BZIP2)  (display if Is HDFS Destination? = true and Compress Data? = true)
- User should be able to configure whether the landing zone should be continuously monitored -- a check once per minute (configurable) to see whether a file has arrived -- or whether files are expected at a regular interval -- once per day/week/month.
- Designate resources to be notified when data arrives and when transfers to destination folder is complete.
- If files are scheduled on a regular basis allow users to designate whether they would like a notification when a file doesn’t arrive by a certain time of day.
- There should be a mechanism to group or tag jobs beside the folder structure of the source directories.
- There should be the ability to send a notification (webhook or JSON request) to another system that a further transformation job should be run on the data file after the data arrives in its target destination directory.

7). Recently Completed File Transfer Jobs
Please report the following information for recently completed jobs:
- Time delivered in landing zone
- IP Address/DNS Name of Landing Zone
- Full Path to file
- Size of File
- Time transferred to destination
- IP Address/DNS Name of Destination Zone
- Full Path to destination file
- Size of File at Destination folder
- Status:  for error reporting - Initial Delivery Error, Transfer Error, Network Connectivity issues, Files - Not Found (File Naming issues) Errors, Permission/Authorization issues etc.

8). Currently Running File Transfer Jobs
Please report the following information for recently completed jobs:
- Progress of delivery to Landing Zone - Both time remaining and size in KB, MB, or GB depending on size of file.
- IP Address/DNS Name of Landing Zone
- Full Path to file
- Current Size of File
- Progress of delivery to Landing Zone - Both time remaining and size in KB, MB, or GB depending on size of file.
- IP Address/DNS Name of Destination Zone
- Full Path to destination file
- Current Size of File at Destination folder

Target User
- HP Internal Employee

Judging Criteria
- How well you build wireframe solution for HP Data Quality Landing Zone Web Application based on requirements below
- Follow best practice of Responsive Design Patterns.
- User Experience of this application is our concern

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 Plain HTML/CSS/JS or you can generate from Axure application. The resulting files are not critical in this Challenge.The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.

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.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure
  • Sketch

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30055641