BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Test Data Generator GUI Wireframes. Primary purpose of this contest is to create a wireframe for a desktop application that will help to generate test data which in turn will be used by developers and application testers.

This Desktop Application will allow the users to Manage Data projects (Create/Update/Delete). Within a Data Project they will have the ability to specify the database connectivity details, specify tables, specify regular expressions and generate XML configuration files. This XML Configuration file will be used as the input to generate Test Data, and this generated test data can in turn be uploaded to a target database as per the need of the user. See the below tasks and attached conceptualization for more details.

Round 1

-Complete all the use-cases under “Application Tester and Developer Functionality”
-Notes : Any comments about your wireframe, make sure all pages have correct flow! 

Round 2

-Complete all the use-cases under “Application Tester and Developer Functionality”
-Any suggestions from client given during milestone feedback need to be implemented.
-Notes : Any comments about your wireframe, make sure all pages have correct flow!  


About the Project:
Basically this project revolves around three primary components - Database Metadata Mapper (Maps the columns from table), Regular Expression Generator (generates regular expression from sample data) Test Data Generator (Main component that generates test data) - these are used for the generation of Test Data for databases which have a JDBC driver (e.g. DB2, Oracle, MS SQL Server, MySQL, and PostgreSQL). This Desktop Application will have the following abilities,

1) User can create a New Data Project and they will be able to perform any of the following activities within the Data Project.
2) User can specify the Test database with connectivity info.
3) User can specify the tables from the database – column for tables is retrieved by the system.
4) User can specify the Test Data Configuration options for the table (s) (multiple tables need to be supported)
5) User can either specify the regular expression for each column with a String Values (CHAR, VARCHAR) or generate the regular expression by connecting with sample data.
6) User can generate the XML Configuration File.
7) Finally, user can use the generated XML configuration file to generate Test Data and upload the data to Target Database (if needed)

The above mentioned points were grabbed from the conceptualization document to help you understand the project easily. Please read the conceptualization to get a complete understanding of the project and use-cases.

Contest Requirements
For this contest you will need to complete the entire use-cases under “Application Tester and Developer Functionality”

4.4.2 - Close application
4.4.3 - Create new test data project
4.4.4 - Open existing test data project
4.4.5 - Save test data project
4.4.6 - Edit test data project
4.4.7 - Specify test database with connectivity information
4.4.8 - Specify table names
4.4.9 - Specify test data generation configuration options
4.4.10 - Specify regular expressions
4.4.11 - Generate regular expressions
4.4.12 - Generate xml configuration file for "Test Data Generator" component
4.4.13 - Generate test data files
4.4.14 - Update target database with generated test data

Reference Designs and Best Practices
Some reference design concepts might include:
1) “Wizards” (http://en.wikipedia.org/wiki/Wizard_%28software%29) that guide new users through complex tasks
2) The requirements and conceptualization refer to the managing of test data generation configuration as “Projects”. Design inspiration may be taken from Eclipse: http://www.wikihow.com/Create-a-New-Java-Project-in-Eclipse
3) The GUI designer may take some general inspiration on usability from Neilsen’s Ten Usability Heuristics: http://www.useit.com/papers/heuristic/heuristic_list.html

Target Audience
-Developers
-Application Testers 

Judging Criteria:
Your submission will be judged on the following criteria:
-Usability and intuitiveness of the interface design.
-Completeness and accuracy of the wireframe as defined in the requirements.
-How well your wireframes provide a consistent user flow
-How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)

Submission and Source Files Requirements
Submission File
All requested contest requirements/screens as clickable HTML files unless otherwise stated in the contest details.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Preview Image
Create a 1024x1024 JPG or PNG file in RGB color mode and place a screenshot from your submission within it.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe. 

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.

ELIGIBLE EVENTS:

2013 TopCoder(R) Open

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

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30028884