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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to LIVING PROGRESS - BUILD - WCS - Admin Tool Wireframe Challenge!

The goal of this challenge is to build the user experience of the admin tool for Women Community Savings team. We need the tool to be user friendly web application. No UI prototype is currently available but it’s expected that the UI will adhere to the detailed requirements provided in this challenge specification.

Round 1

- Submit your initial wireframe solution for checkpoint feedback.
- Submit an initial version of your solution.
Notes.jpg: Any comments about your design for the Client.

Round 2

- Submit final wireframe solution plus checkpoint feedback.
- Submit final version of your solution.
Notes.jpg: Any comments about your design for the Client.
Challenge Description:
The goal of this challenge is to build the user experience of the admin tool for Women Community Savings team. We provided detailed requirements under admin tool requirements.
 
We are looking for wireframe (Axure) solutions based on requirements below. We’re also looking to the community to come up with interesting ideas for the workflow - we’re absolutely open to creative solutions!
At the end of this wireframe challenge, we are looking to have a complete solution for the user experience and flow.

Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all screens mentioned in required sections below, if any requirement is missing in final submission the client will not look at it, so make a checklist for the required screens to make sure you designed all of them.
- Please show us your proposal as a movie or series of wireframes that communicate the user’s intended interaction with your proposed solution.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.

Notes:
- This is going to be a web application.
- Your wireframe submissions need to be able to drill down for all page flow.
- Show your wireframe solution for:
-- Desktop view: Design for desktop display 1280px and height as required.
- Please consider responsiveness while designing the solution as the client want the solution to be usable on mobile devices as well.
- Feel free to suggest any tools/functions that can bring good User Experience for this tool.

Admin Tool Requirements:
1 Login & Logout for Admin Users:
- It is assumed that the admin user needs to login to be able to perform any operation with the app. If the user is not logged in, they will be prompted to enter their credentials. The application must log all activity related to user authentication.
Login:
- The application will allow admin users to login by entering their credentials. The application validates user credentials and performs authentication/authorization:
-- Pre-conditions: the non logged-in user taps the application icon on their device
-- Post-conditions: the user was successfully logged in, can access application functionality.
- The user will be entering the username and password on login screen. Both username and password are case sensitive.
- If either username, password or both are invalid, the app will show a message ‘Invalid credentials’ and prompt the user to try again
Logout:
-
The user can logout at any time from the application to ensure high security.  The logout will be performed through the some security system:
-- Pre-conditions: the logged in user pressed “Logout” button or the user session has expired.
-- Post-conditions: the user was logged out from the application and cannot work with the application until login again.
- Once logged in, the admin user can tap the logout button/ link to log out of the app.
- We need “Remember Me” checkbox.

2. Forgot Password:
- The admin user should be able to click the ‘Forgot Password’ button on login screen to retrieve their credentials. Clicking this link should open a modal window prompting the user to provide their email (username).
-- If the user provides a valid username (email), they should get a link to reset their password
-- If the user provides an invalid username (email), the app must show an appropriate error message that the username is not valid.

3. Super Admin User:
- It is assumed that at least one super admin user is pre-populated via a database script/ configuration. The super admin user can then in turn:
-- Add new admin users
-- Mark a user as admin
-- Remove admin privileges for other admin users
-- Add/Delete/Update other admin users
- For Android app users, the super admin and admin users can do the following
-- Deactivate users (bar them from logging into the Android app)
-- Reset password
-- Change/ assign roles such as President, Controller, Treasurer, Secretary.
- The super admin user must also be able to change it’s own password and modify profile attributes such as:
-- Name.
-- Email.

4. Android App User Listing, Search Sorting:
- It is expected that the admin app provides a list view for all users of the Android app, providing searching and sorting capabilities. The list view must show the following user fields
-- Member Id
-- Name
-- Email
-- Saver Group
- The following information must be pulled in from the corresponding Saver Group:
-- Saver Group Manager Name
-- Saver Group Employment Worker
-- Saver Group Township
-- Saver Group District
-- Saver Group Country
- It should also be possible to click on an Android user’s member id (hyperlink) to view additional user details such as:
-- Savings Passbook Details
-- Loan Passbook Details

5. Reset Password for Android App Users:
- It is expected that super admin and admin users have the privileges to reset password for Android app users.  This should trigger an email to the Android app user with a link to reset their password.

6. Role Management for Android App Users:
- It is expected that super admin and admin users should be able to modify the role for Android app users.

7 Manage Other Admin Users:
- It is expected that the admin app provides a list view for all other admin users providing searching and sorting capabilities. The list view should allow the following capabilities:
-- Add new admin users
-- Mark a user as admin
-- Remove admin privileges for other admin users
-- Add/Delete/Update other admin users

8. Sponsor Logo Customization:
- The Android app shows 4 sponsor logos on the login screen. It is expected that the super admin/ admin users can upload/ change these icons in the admin app and these are retrieved in the Android app via an API.

9. Report Requirements:
- The Admin app should allow super admin and admin users to be able to generate reports for loans, transactions, account statements. It should allow:
-- Selecting certain geographies and drill down capabilities based on country, township, district etc.
-- For a certain saver group etc.

Supporting Documents:
Admin Tool requirements document (AdminTool-DetailedRequirements.pdf.zip).

Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn

Target audience:
- Admins from Women Community Savings team.

Judging Criteria:
- User Experience of application.
- Completeness and accuracy of the wireframe as defined in the spec requirements.
- How well your wireframes provide a consistent user flow.

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.

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.

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:

2017 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: 30055240