NASA SMG Tool Wireframes Challenge

Welcome to NASA SMG Tool Wireframes Challenge. We need you to create HTML wireframes to represent a simple web application for NASA.

Round 1

For your R1 deliverables please submit all the requested features for client review.

Round 2

Final wireframes will contain all of the functionalities plus any updates from client feedback.

The primary goal of this contest is to create HTML wireframes that represent the functionality of a web application that acts similar to an airline ticketing system. The goal is to provide content to users through a wide variety of filters and contribute for learning purposes. In other words, three environments, Admin, SMG Tool and Education Portal, 3 screens tops for each scenario, which would make a total of 9 screens approximately for this challenge. It’s up to you to create more or less according to your suggestions of course.

As reference, see any ticket issuing website, Expedia recommended but DON’T COPY ANYTHING, just as reference for inspiration.

General Requirements
- Produce HTML click-through wireframes to represent the functionalities of the application.
- The design should be simple, user-friendly and easy to understand.
- Develop as many pages/elements you need to complete all the requirements.

Wireframes Requirements
Background
Follow the attached SMGApplicationFeatures document with description of the features and background you should know to understand this application. It’s a simple concept document you need to explore to extract requirements from. You are encouraged to improve the features but make them simple.

The Solutions Mechanism Guide (SMG - SMGTool.ppt) is put together by NASA to allow their employees to understand the different solutions available to them based on specific criteria and based on their current stage of their project. The SMG presents the users with different “Solutions” which have unique characteristics like cost, delivery type, duration, etc (SMGSolutions.xls).

While this guide exists, it is not user-friendly, and the linear design makes it hard to maintain. When someone adds a new Solution to the guide, there is no easy way to do it other than manually, and revising the flow that presents the information is cumbersome.

You don’t need to include all the content from these slides since you’re creating something new filter-based, it will all depend on the filter capabilities, just so you know the scope of this challenge is short in that sense.

Deliverables
The client wants three sections to the new version of this guide (see section #3 and #4 in the provided document respectively):

1) SMG Management (Admin)
1.1) Create/Edit/View Solutions
- Edit information about each solution

1.2) Create static pages as part of the Education section
- These are reference pages.

1.3) Create static informational pages for the Education portal

1.4) Add/remove fields from the search form

2) SMG Tool
2.1) View solutions that match the search criteria
-  Include screen for viewing full solution details

2.2) Compare 2 or more solutions (like comparing laptop model/specs, etc)

2.3) View display in printer friendly format

3) SMG Education Portal
3.1) Static pages with information (Knowledge maturity guide, etc)

3.2) Will have a top-level “Topics” page that is like a table of contents

Note: #2 and #3 will have the same top level starting point. Also, at points within #2, there should be quick access to the corresponding definitions all available in the Education portal. For example, as an user is filling out the form, the Knowledge Maturity Level is being asked and he/she doesn’t know what that is - It should be easy to quickly see what that is in the Education portal and then jump back into the Form. Or, can just browse the Education portal for these topics before proceeding with the form.

The Admin panel will have a different entry point.

Target Audience
IT related government employees.

Judging Criteria
- Capability to capture and represent the application features.
- User experience.

Submission File
All requested contest requirements/screens as clickable HTML files unless otherwise stated in the contest details.

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.

Preview Image
Create a 1024x1024 JPG or PNG file in RGB color mode and place a screenshot from your submission within it.