Challenge Summary
The Global Service Activity System (SAS) is a web based application used to track project related service activities. Users can create and edit service activity data, perform on-line inquiry, filtering/sorting of that data, and generate either a service activity summary or detailed reports.
For this challenge, we need you to create the Storyboard Design for the new SAS web application (based on the wireframes created in our previous challenge).
We look forward to seeing your creative designs!
Round 1
Round 1 will focus on the following user functionality for the SAS web application:
1) Dashboard
2) Service Activity
3) Reporting
a) Only the Reports Wizard screen is required for Round 1 (the rest of Reporting will be included in Round 2).
NOTE: See the requirements in "SAS Web App Wireframes FFv2.zip" (wireframes for the new SAS web app) to understand the screens / functionality for these areas. The wireframes show how the screens / functionality should work in the new web application.
Round 2
In Round 2, you will need to include all Round 1 screens (updated based on milestone feedback). For Round 2, you must also include all the remaining functionality descibed in the prior wireframes and project documentation, including:
4) Reporting
a) All Reporting functionality, including Reports Wizard from Round 1.
5) Admin
6) Help
Primary Goals
The goal of this project is to design and develop a new Global Service Activity System (SAS) web based application. This project is a re-write of an existing FLASH based system to a JAVA based system with an improved architecture.
For this challenge, we are asking you to create the Storyboard Design for the new SAS web application (based on the wireframes created in our previous challenge). The wireframes for the new SAS web application are attached for you to use while creating the Storyboard design.
Project Description
The Global Service Activity System (SAS) is a hosted web based application used to track project related service activities. Users can create and edit service activity data, perform on-line inquiry, filtering/sorting of that data, and generate either a service activity summary or detailed reports. The reports can either be on demand or the user can setup a schedule for the report and it is then emailed based on that schedule. The user can setup and maintain N number of reporting schedules. The tool provides a dashboard area that the user can add canned graphs that show services activities by date for a specific division. The user can add a graph for each division present in the data set and then reorder them. There is also an administrative function to create and maintain the Areas that are used in the tool.
This project will design and develop a new Service Activity System (SAS) web based application by re-writing the existing FLASH based system to a JAVA based system with an improved architecture.
General Requirements:
- Produce a front-end design (Storyboard) that can be used to demonstrate all screens / mentioned functionality as required in each round.
- Required designs are for a web application (the new SAS web application).
- The design must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in contest round details (and described in the wireframes).
- Your design must represents all pages and flows from Wireframes. You should use that as a guide, but if there is better way to display any information, feel free to reflect that on your design.
- Screens should be numbered correctly to explain the storyboard flow to us.
- Please check wireframe notes on each page to see the various interactions in those pages. You need to include those in your submission.
Branding and Guidelines:
- Your design must fit 1024 pixels wide screen resolution. It should also be able to scale up to larger displays.
- Colors are open to designers. Consider the target audience of this application and "the ATLAS look and feel" (see attached files for examples of this). It must be pleasant and easy to use.
- Use web-safe fonts for the pages content. Beware of declaring your fonts according to the Studio font policies.
- Show all the hover states for all UI elements you create (buttons, hyperlinks, dropdowns, etc).
Storyboard Requirements:
Overall:
- Follow the workflow and layout guidance from "SAS Web App Wireframes FFv2.zip" (wireframes for the new SAS web app). You need to create storyboards to cover all the pages in these wireframes.
- Make sure to provide screens for popups, collapase/expandable features, error forms, and so on.
- As a suggestion, click all the buttons in the forms to understand the interaction features of the application.
- Pay attention to some notes over the wireframes with UI descriptions.
Project Documentation:
1) "SAS Web App Wireframes FFv2.zip" - Wireframes for the new SAS web app. Your Storyboard Design should be based on these wireframes.
2) "Example from Previous Project - Service Request Tool - finalFix-8-prototype.rar" - Storyboards from a previous project (the service request tool). Provided to show an example of the "ATLAS" look and feel. NOTE: These Storyboards are from a DIFFERENT project and are only provided as an example of the "ATLAS" look and feel the client would like for the SAS web application for this project.
3) "ECUE Standards and Icons.zip" - The ECUE standards and icons that are the basis of our ATLAS look and feel
About CCA Contests
- CCA (Competition Confidentiality Agreement) is required for this contest. If you don’t have a signed CCA on file you need to follow these instructions and then request for the access: http://apps.topcoder.com/wiki/display/tc/Competition+Confidentiality+Agreement+%28CCA%29
- If you have a signed CCA on file, send the access request for this project to: support@topcoder.com.
Target Audience
Users of the existing SAS application.
Judging Criteria
- Overall look and feel of the design
- Simplicity and Consistency in the design
- Completeness and accuracy of how the design matches the screens / flow of the wireframe.
- How well you follow the client's branding / design guidelines.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client)
What to Submit
Preview JPG/PNG Image File
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 ZIP File
All requested contest requirements/screens as JPG or PNG files.
Source ZIP File
All fully editable original source files of the submitted design as required by the contest under "Source Files" in the side bar.
Final Fixes
As part of the final fixes phase you may be asked to complete one round of minor changes to ensure your submission meets the stated requirements of this contest. See more information about Final Fixes.
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.