Challenge Summary
Welcome back to SQuIDs! We are reposting the "Single Page Assignment to Library Design Concept Contest" to help clarify the requirements and goals of this design concept task.
SQuIDS is an existing web application that is used to support test case creation/planning and defect management. The goal of this contest is to re-design the user experience for the "search results" of the "Library and Assignments" sections and help create a professional user experience around how a user interacts with the SQuIDs application.
Note: We have started a "Bonus Prize" for the Studio Member who wins the most SQuIDs2 Studio Contests! The SQuIDs2 Series is going to be running up to 7 user interface/user experience contests over the next two months! We are looking for the Studio Community to help us innovate the user interface/experience of the SQuIDs Application.
For this contest we already have the user interface/graphic design done! (download the provided PSD source files). We are looking for you to focus on the this single screen and improve the user experience.
Round 1
We would like to see your intitial design concepts for these items for feedback on design and direction
Focus on the two result grids and show us designs that accomodate the use cases
- Sharing & Reuse
- Work Queue
- Any other Use Cases you can show
We really need to be able to provide you feedback at this stage - so submit as much as you can!
Round 2
Final Design:
- All Use Cases/Screens plus design updates from the Milestone round
Contest Details
Humana and TopCoder (HTC) have teamed up to build cutting-edge applications and design modern user interfaces/user experiences. This is one of several contests looking to solve a user experience/user interface design problem through the Studio Community.
Design Problem
Download the provided screens/graphic files (SQuIDS-PSD.zip)
Test Case/Defect Search Page (see Test Labs & Defects tab in the wireframe)
- There are 2 sections that display the search results (one for Test Cases and one for Defects)
- Redesign the user experience for the "Test Case" and "Defect" result grids using the provided design as your base design source
- Users need the ability to see these results in a variety of ways based on what actions they take/items they click. (see Use Cases below)
- DO NOT redesign the page! focus on the search result grids!
- While you are only redesigning specific secions of the page we will need to see multiple screens/click-path of the your updated user experience
Note: The wireframe is provided for reference only
- Design NEW concepts/user interactions for this page
Additional SQuIDs Background Details
SQuIDS Test Cases and Defects are broken apart in two sections: (see the Test Lab & Defects tab in the wireframe)
Library
- The first level is the Library
- A Library is the "what" part of a Test Case/Defect
- The Library is the Name, Descriptions, Steps, Application, etc. > these items do not change
Assignment
- The next level is the Assignment.
- The assignment can be thought of as the "when" part of a Test Case/Defect
- Example: This test case is being tested by X tester, who is on X team, for X project, in X suite, for X phase, and so on.
(see the Asignmts column in the wireframe)
The biggest advantage of this set up is the ability to reuse. Since the Library doesn't change, an Assignment can be used over and over again for different Projects, Releases, Suites, Phases, Teams, etc.
~
Use Cases (Common uses of the Search Results)
We would like you to analyze the use case descriptions and provide design concepts that solve them!
"There are different “stages of testing” where a Tester will need to see the data in different ways. There is a writing stage, planning stage, execution stage and more. Testers would need different views depending on where they are in this process.
Use Case: Reuse
- The ability to reuse existing set of test cases/defects.
- This means creating a new assignment to the Library.
- People focus in on what is being tested (such as the application, steps, and postcondition), but may also use the Assignment information to help narrow their search.
- Example: someone may want to reuse all the new tests from the last release as regression in the next release.
- Alternatively, someone may want the exact same scenario repeated in their plan with the same assignment information, but a different test window, such as cycles of testing or a final pass.
Use Case: Sharing
- The ability to have another team include your tests/defects as part of their work.
- This means the Library remains the same. Portions of the Assignment may be copied to the new Assignment.
Use Case: Status/Updating
- People will get together and review the status of testing and they would like to see a summarized version of tests/defects at once.
- During the review session, they would like to make real time edits without navigating to other screens.
- Especially applicable to Agile teams doing stand-up meetings
- Also includes the approval workflow process for team leads and release managers to review, approve or reject
Use Case: Work Queue
- The ability to see the work that needs to be done by the individual, their team, their project etc.
- Helps to prioritize the next item to work on and move from one item to the next quickly.
Use Case: Mass Changes
- Changes are often required in bulk, such as moving an entire test plan from one release to another.
- People need ability to see the related work, select it, and apply changes in bulk.
- Changes could require prompts for additional information.
- This could also be just data correction such as updating the application or test team for a large quantity.
Use Case: Research
- The ability to find out what is going on at any time, without having to build custom reports
- The ability to drill down into the levels of detail to answer questions, either at the high level or a fine detail
Quick Actions
Include how the quick actions will work. You can review the existing demo application (use IE browser, go to "Test Lab" page and search for "TopCoder Demo App" in the Application field) and see that today they are just a drop down.
- Quick Actions are used in all of the Use Cases
- Quick Actions are needed for users to "quickly" do actions in bulk.
- Basically, a user should not have to open all of their test cases/defects and edit them one at a time.
~
Branding Guidelines
- Follow the provided storyboard design!!
Target Audience
- Internal Resources
Judging Criteria
- How did you think about the Search Results and the interactions?
- Where you able to improve the user experience?
- Sharp graphics that work with the current (provided) design
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Please upload PNG/JPEG images in a zip file with all requested contest requirements stated above.
Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop or Illustrator and saved as layered PSD/AI files.
Final Fixes
As part of the final fixes phase you may be asked to modify your graphics, images (sizes or colors) or modify overall colors.
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.