Challenge Summary
Welcome to Seto - Group Synchronization Wireframe Contest.
We are building an application that will have task to synchronize user groups between different directories.
At the end of this contest, we are looking for an HTML wireframes which showing a new workflow for the application and can be use as input for the next storyboard contest. This application must be user friendly, intuitive, and easy to use.
Round 1
Your submitted solution for client review.
- All user functionality.
Any comments about your wireframe, make sure all pages have correct flow!
Round 2
Your submitted solution for client review.
- All user functionality with the client feedback implemented.
Any comments about your wireframe, make sure all pages have correct flow!
Contest Details:
The purpose of this project is to build a wireframe for new Group Synchronization application. This application will have task to synchronize user groups between different directories. Initially, the directories to be integrated with the new application for synchronization are Domino, Google and client’s own corporate directory running on Sun ONE. The new application will be flexible enough to support adding new directories for synchronization if required in future
We expected the wirefame will capture the best layout and show great user experience that will convey the application functionality.
General:
- Your wirefame solutions must be useful. So, it can save a web designer so much time and energy!. All pages/elements must linked each others. Show us the correct flow.
- The application must be very easy to use and intuitive.
- The application will be built as website application.
- Your wireframe must represents all pages and flows from Conceptualization document. You should use that as a guide, but if there is better way to display any information, feel free to reflected that on your wireframe.
- You MUST use wireframes note pane in every single page you design, to explain what all items are addressed in that page, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
- We also attach the ARS document about the scope and requirements for you to fully understand the propose application functionality.
Group Synchronization Wireframe Requirements:
A. User Functionality
1. Login
- Please provide another screen to show the login error if the username and/or password are wrong.
2. Logout
3. View Homepage
- This will be the screen the user see upon successfully login
- This page should have navigation links to the user role-related functionality of the application
4. View Synchronization Status
- This application proposes the following synchronization statuses for a group: (can be synchronized, ready for synchronization, undergoing synchronization, synchronized, and synchronization error)
5. View Errors
- The error details would contain the directory synchronization errors and communication errors.
6. View Directory User Lists
- The directory user lists will contain the list of users of a specific directory of interest.
- This information can be retrieved via the connectors that integrate with directories.
7. View Groups
- All the logged in users will be able to view information of all groups in read-only mode irrespective of whether they are a member of that group or not.
8. Create Group
- Refers to section 4.4.8 in the Conceptualization doc about the details and required fields.
9. Update Group
- A logged in user will be able update an owned group through the new application.
- Refers to section 4.4.9 in the Conceptualization doc about the details.
10. Delete Group
- A logged in user will be able delete an owned group through the new application.
B. Group Owner Functionality
A Group Owner will be able to perform all actions that a "User" can perform.
1. Modify Mappings
- In the context of this application mapping means making one attribute equal to another attribute.
- Refers to section 4.4.11 in the Conceptualization doc about the details and example.
2. Modify Directories
- The group owners will be able to provide and modify directories information for the groups that they own, the directories information would contain the two directories between whom the Synchronization is intended to take place
3. Force Synchronization
- The group owners will be able to initiate an immediate Synchronization when required on demand.
4. Initiate Simulation Mode
- The group owners will be able to use a simulation mode that helps them to see what the application would do before it actually does it.
5. View Simulation Results
- The group owners will be able to view the simulation results displayed by the application.
6. Acknowledge Simulation Results
- The group owners will be able to acknowledge the simulation results.
C. Help Desk Member Functionality
Help Desk Member will be able perform all actions that a Group Owner can perform. Additionally, the administrator will be able access and modify all groups except the custom LDAP groups.
1. Administer All Groups
- A help desk member will be performing most of the actions that will be similar to that of a Group Owner. The only difference will be that a group owner will be able to access and perform operations specific to only the groups that they own. But, a help desk member will be able to access all groups with the exception of the custom LDAP groups that are accessible only to the administrator.
D. System Administrator Functionality
A System Administrator will be able perform all actions that a Help Desk Member and a Group Owner can perform. Additionally, the administrator will be able manage system level configurations such as configuring the synchronization engine, connectors, Groups and Logging. The administrator can setup synchronization rules and mappings, Manage Custom LDAP(Lightweight Directory Access Protocol) Groups and can view logs.
1. Configure Synchronization Engine
2. Configure Connectors
3. Configure Groups
4. Configure Logging
5. Set Synchronization Rules
6. Manage Custom LDAP(Lightweight Directory Access Protocol) Groups
Target Audience:
- Current customer
- Potential customer
Judging Criteria:
- User Experience
- Completeness and accuracy of the wireframe as defined in the attached 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 & 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
Wireframes should be built in HTML or Axure. The resulting files are not critical in this contest. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
Final Fixes:
As part of the final fixes phase you may be asked to modify content or user click paths.
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.