Instructions
What this Document is For
The purpose of this questionnaire is to help TopCoder learn how your new application should operate to best address your need, problem or opportunity. We'll ask you to describe your current process, and identify your main needs or opportunities. We'll also ask questions about the sort of technical environment the new application should expect, and what features the new application should include.
Your responses to this document will be fed into the Pipeline to start the process of creating a prototype and writing a formal Requirements Specification for your application.

What this Document is Not
This Questionnaire is just a starting place – it is not a formal requirements specification. After you or your team complete this document, your Manager or Co-Pilot will compile responses and post them to competition. The competition includes a lengthy question-and-answer period with you that will flush out details and exceptions. So, don't worry if you miss a few details – there will be many opportunities to fill in the gaps later!

What You Need To Do
Please answer the questions below to the best of your knowledge. If you would like to include drawings or diagrams to make your point better or easier, please feel free. Screenshots of the current application are always helpful too. You can answer questions directly in this document, or include attachments with your responses if you need more space.

• Some questions are more important than others. Please do your best to answer questions marked with the red asterisk. If you cannot provide an answer, please include a few remarks about the reason.

When you're done, please email the Questionnaire to your Co-Pilot or Manager.
NOTE: Do not include "real" data. Be sure to edit or mask screen shots or other attached documents!
Concept Questionnaire
OBJECTIVE

• Please describe the chief goal(s) you wish to achieve by developing this application.

OPPORTUNITY or CURRENT APPLICATION/PROCESS

• If you are planning to replace an existing application or business process, please describe the process below. Or, if you are creating an application to take advantage of an opportunity, please describe it here as well. If you wish, include a diagram that illustrates the steps and systems that are involved in the process. In this section, you are "telling the story."

• Broadly speaking, who is involved with the data or application?  (Please briefly describe the roles of people who will be involved or affected and the information that they will provide or receive.)

  Visitors or information seekers ask a question…or even sometimes … local people want to ask something of other locals or new people to the city who have moved here might want to ask a question too. This question goes on my website and on facebook and twitter and everywhere people can see the question and those that have KNOWLEDGE about the question can answer… but we want people from that city to get the question and answer first.. to get the question on their phone, email, mobile etc.. everywhere.. and people NEED A REASON TO ANSWER and share their LOCAL KNOWLEDGE..

  
  
  What information do you need to feed into the system to complete the process (system input)? For example, do you need to key in customer account numbers or names? Is there a list of shopping cart items?

  You ask a question about a (CITY) choose city Choose (TOPIC) You have a photo or cartoon saying who are (male or female) and maybe (age group) Your question goes everywhere Your answers are listed, emailed to you maybe,, and retained online under the particular topic you are referring.. e.g. accommodation..

  
  
  What are the outputs of the system? For example, does the application charge the customer and print a receipt? Does it update another system?
  

  Answers are listed based on how quick there is a response and based on location if question is about New York answers should be from New York users.. Answers are rated in some unique way that can identify the quality of both question and answer

  
  
  
  
  

• Does the application or process depend on other systems, documents or people? If so, name and briefly describe them here.

  People must want to use our system to ask questions about the area/city/region/country Answers need to be "location based", "fun", Interactive and in and environment that makes a person feel special about the attention they receive back from their question they asked.

  
  
  

• Are there shortcomings to the current system? If so please list and describe them here.

  
  
  If your system or process is comprised of different modules, please briefly describe them here. For example, are there modules or screens that are used only for maintenance?
  

  
  
  
  Please list any mission-critical reports that are produced by the system.
  

  
  
  Is there anything else about the application that you'd like people to know? This is the place to address any functionality, problems, opportunities, risks, etc. that didn't "fit" in earlier questions.
  

  
  
  PROPOSED APPLICATION
  Business Requirements
  

• Why are you taking the time to build this application? What are the expected benefits? What features will indicate success?

  Success will be when someone asks a question about a city to a resident of that city and lots of people around the world answer questions about their city and answer the questions they see are being asked… that people love doing it and keep doing it..

  
  
  

• What will the inputs to the system be? For example, what data or resources do the users or the system need in order to start the process?

  
  
  

• What are the expected outputs from the system? (Outputs can include printed reports, receipts, modified displays, electronic data feeds to external systems, etc)

  
  
  

• Please describe the ideal task flow of the new application; how should it work? Begin with the inputs and end with the outputs. In this section, you should exclude the exceptions that might occur.

  
  
  If possible, please describe the reasons why the path above can fail (or fails today). This could include time or resource limitations, problems with data relationships, other glitches, etc.
  

  
  
  
  
  
  Background and Basic Functionality
  

• Is this a new system, or an upgrade to an older one?

  I don't have this so its new it hasn't been created yet

  
  
  

• Approximately how many users will be using the application?

  Global

  
  
  

• How many users will be on the application concurrently?

  Global so you work it out.. billions and trillions..

  
  
  Will any users be using the system from different timezones?

  Yes.. depending … we want questions about a city to be answered from people in that city but that doesn't stop people from other countries with information answering too but that information should not be as visible as the more appropriate responses from people from that city

  
  
  

• Will the system need to receive feeds from external systems? If so, please name them, if possible. Include a description of the data that must be transferred, and the form it must be transferred in (e.g. email, paper, electronic feed, etc).

  
  
  

• Will the system need to send feeds to external systems? If so, please name them, if possible. Include a description of the data that must be transferred, and the form it must be transferred in (e.g. email, paper, electronic feed, etc).

  
  
  
  Is the system expected to send or receive email? Under which conditions?

  Maybe don't know.. depends on what you think.. maybe..

  
  
  
  

• Is the system expected to operate with any peripheral devices besides a printer? For example, will the application be required to support fingerprint scanners, barcode guns, touchscreens, tablets, RFID, etc.

  
  
  
  Usability

• Please describe the computer resources the designers should expect of the users. For example, will every user have a PC, or should the application be a "green-screen" app? Do users have keyboards and mice? Will users have internet access?

  Users will have internet access

  
  
  Do users have specific GUI needs of the application? For example, should the application support "heads-down" or "cash register" style usage?

  
  
  Wish List
  Please describe some new features that you would like to see the system include.

  Interactivity and making asking an answering a question, fun, rewarding, global and mass opportunities where it can be distributed easily based on "location" you have a question on New York you get New York residents seeing and answering the question FIRST before anyone else. It would be incredible to have some great reward system that makes people want to answer questions about the town or city they live in.. and to make them want to do it again and again.. so everyone can talk to "local people" all around the world..

  
  
  Security
  

• Should the system require the user to log in?

  Probably not maybe a very easy login that pops up so we can get a database but it cannot be difficult as people might not then help answering the questions people have

  
  
  

• Is there a "central authority" that manages user's accounts that this system should "talk" to? If so, please name or describe it if possible.

  
  
  Are there special auditing needs for user's activity on this application?

  We want to give the user points and record information of both and have both question and answer recorded if it is GOOD but to be removed or deleted if it isn't.. How can ensure the quality of the question and answer..

  
  
  

• Will the user be working directly with financial or other protected information, like health records and classified data?

  No

  
  
  Technology
  Should the application be networked or stand-alone? Browser-based or thick-client?

  Don't understand at all

  
  
  Is there a particular language or platform on which the system must be built?

  ENGLISH BUT NEEDS TO BE ABLE TO HAVE GLOBAL LANGUAGE ABILITIES

  
  
  
  THANK YOU!