Challenge Summary
Welcome to the Squids 2 Wireframe Contest. The goal of this wireframe contest is to design an easy-to-use, efficient browser-based application that will be used to create storyboard design and explains the page/elements flow of Squids2 application. Basically we need brand new layout based on the old application but also add some improvements on User Experience and using some our recommended UI Elements.
In the end of this contest we are looking for a process flow and layout design of the pages mentioned below that are part of the whole application. This application must be user friendly, intuitive, and easy to use.
Read contest details and provided attachment to help you create our expected wireframe.
Round 1
Round One
Squids initial wireframe pages for:
1. Homepage
2. Self Service Extracts
3. Test Case Search
4. Defect Search
5. Defect Details
6. Team Administration
7. User Preferences
Notes : Any comments about your wireframe, make sure all pages have correct flow!
Round 2
Final Squids wireframe pages:
1. Homepage
2. Self Service Extracts
3. Test Case Search
4. Defect Search
5. Test Case Planning
6. Test Creation
7. Test Case Details
8. Defect Details
9. Team Administration
10. User Preferences
Notes : Any comments about your wireframe, make sure all pages have correct flow!
Contest Details
The client's company developed a custom tool (SQuIDS) for performing those tasks within company environment. Custom development was performed due to special needs (like different views, tracking data by release, project, phase, application, and/or team) – most commercial test management products didn't support that.
Squids Wireframe Requirements
Note: We attached design ideas.docx, and SQuIDS Student Guide - SQuIDS 101.pdf as references and design idea when build the wireframe.
1. Homepage
- Old page reference: http://ec2-72-44-58-56.compute-1.amazonaws.com/General/Home.aspx
- Desired to be very customizable, widget based
Potential widgets might be:
- Quick Search - single text box to look up a specific test case or defect
- Buzz - Widget to display our internal social networking threads. How the area gonna looks like?
- My Work Summary - Like what is there today on the left with counts associated to the person by status/workflow
- My Test Cases - List of active test cases associated with the user. Check the sidebar of the old Squids homepage.
- My Defects - List of active defects associated with the user. Check the sidebar of the old Squids homepage.
- Quick Import - (assuming the Excel file is already built and ready) Provide an upload option to import new test cases. Need some table of imported files?
- Need create Gauges UI elements for any Squids Summary?
2. Self Service Extracts
Might include things like:
- Search section
- List of fields to select to create custom extract
-- How can this list of fields be more user friendly?
-- Could people be able to drag and drop from a list of available fields to their desired layout? Or some similar movement?
-- People should be able to change the order of the fields
Other considerations:
- Defect and Test Case search criteria are very similar - can these be combined into one search/extract area?
- Some folks may want defects and test cases on the same extract. This can be tricky because it's a many-to-many relationship, but is it doable?
3. Test Case Search
Reference: http://ec2-72-44-58-56.compute-1.amazonaws.com/TestCases/TestCaseLibrary.aspx
This page might include things like:
- Search section
- Results section
-- Inline editing on results
-- Customize what's in the results view
- Quick Actions
- Preview/edit pane for the more common activities
- Follow data in table and filter like existing page
4. Defect Search
Reference : http://ec2-72-44-58-56.compute-1.amazonaws.com/Defects/DefectSearch.aspx
This page might include things like:
- Search section
- Results section
-- Inline editing on results
-- Customize what's in the results view
- Quick Actions
- Preview/edit pane for the more common activities
Other considerations:
- Defect and Test Case search criteria and results are very similar. Can we gain anything from this? They are separate entities, but are there ways to combine views (maybe not have 2 searches, maybe 1?) that help users? Don't have the answer… just worth pondering
- Could it do something cool like show me test cases in one area and defects in another on the same screen, and for example, let me 'drag' a defect to a test case to build an instant association? This is just brainstorming out loud to see what sticks
- Follow data in table and filter like existing page
5. Test Case Planning
This page might include things like:
- Something that contains the planning rules for that team
- Something that allows the users to move test cases (one or many) to a planning window
- Chart(s) to display real-time what the plan is looking like as it is being built
6. Test Creation
Might include things like:
- Easy way to enter multiple tests at a time
- Ability to quickly copy information from one test case to another
- Ability to apply 'template' to fill in 'overhead' fields
- Ability to quickly transition into Test Case Planning activity
- Desire is to make it equal to or better than an Excel import today so that people work directly in the tool itself
a. BONUS!! From tool, should be able to upload attachments to test case easily, which is not available in import
b. BONUS!! From tool, should be able to map to VersionOne for backlog traceability which is not available in import
- Ability to customize what information is collected on add to match team/user needs
7. Test Case Details
Might include things like:
- Everything that's there now, but displayed more user friendly
- Ability to collapse/hide/configure 'sections' (currently tabs) that aren't frequently used
- More natural way to read through comments and attachments to follow the updates and course of events
- Ability to focus on the core test case and de-emphasize the required 'overhead' fields
8. Defect Details
Might include things like:
- Everything that's there now, but displayed more user friendly
- Ability to collapse/hide/configure 'sections' (currently tabs) that aren't frequently used
- More natural way to read through comments and attachments to follow the updates and course of events
- Ability to focus on the core test case and de-emphasize the required 'overhead' fields
Other considerations:
- Defect and Test Case details and results are very similar. Can we gain anything from this? They are separate entities, but are there ways to combine views that help users?
- Could a screen exist with defect and test case information side by side, so for instance, if you are retesting a failed test with an open defect, you can see it all at once and update at once?
9. Team Administration
Might include things like:
- Area to configure team leads and members
- Area to configure subteams
- Area to configure custom fields
a. With the ability to set them as required, as well as define them
- Area to configure test planning rules - Area to view test plans pending approval, see graphically, approve and deny them - Non-required fields they may want to turn 'off'
10. User Preferences
Might include things like:
- Managing saved searches.
- Widget preferences.
- Default 'home' page preference (allow them to skip home page and go straight to Defect Search for example)
- Quick lists - projects, teams, apps - for quicker drop down lists
- Email configuration
- Non-required fields they may want to turn 'off'
Target Audience
- Internal Resources
- Potential Customer
Judging Criteria
- Our main concern is to get great user Experience of Aegle MarketPoint application for Administrator pages!
- Completeness and accuracy of the wireframe as defined in the attached requirements and conceptualization.
- 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 & 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
Generated HTML files with all the requested contest requirements stated above. Keep your source files out from this submission folder.
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.
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.