Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Outline the features to program by priority--core features, enhanced features, and wish list features. You will find an example of a basic requirements document in the examples tab, as well as the feature map example that can serve the same purpose. Begin coding and maintain well organized code as you progress towards your first full demonstration. It is important to code in "chunks" that you can test frequently to minimize the chance of some bugs getting very hard to diagnose.
Optionally, you could use pseudocode to outline your plan for development as well. This Kahn Academy tutorial is a good introduction to the technique.
❏ Deliverable A document or slide that outlines your progressive development plan.
After careful review of your team's sketches and ideas (from 1.5), agree on the main game features and the visual theme of your team's design. Then create digital interface mockups that represent your different screen states that can demonstrate the game flow. These mockups will be used in the next step to create an interactive prototype.
If your team is has having difficulty agreeing on a design direction, determine a plan to come to a decision. Maybe, instead of one mockup, you make two or three unique mockups to compare before deciding.
❏ Deliverables Five digital screen mockups (or more) that represent:
the welcome screen
the question screen
the question screen on correct answer feedback
the question screen on incorrect answer feedback
the closing (thank you) screen once the player is done.
Provide enough visual and interactive detail in your interactive prototype to allow thorough testing of each potential user scenario in your game. We recommend you use Marvel App to create your prototype.
❏ Deliverable A link to your working Marvel App prototype that uses your interface mockups.
Conduct some basic code testing to verify that the app is acting as expected under different conditions. Ensure that everything works as expected on different size screens and with touch or mouse interactions. Consider all the things a user might do, like double click, click and drag, swipe, change browser dimensions mid-game, etc.
❏ Deliverable A document outlining the results of your code testing.
✓- Below Standard
✓ At Standard
✓+ Above Standard
A prototype is provided but lacks detail to make the evaluation fruitful, not demonstrating a unique visual or interactive perspective on the basic trivia template design.
A prototype that demonstrates thoughtful concept design and provides a good representation of idea for feedback from participants.
A prototype that is exceptional in representing and evaluating some novel concepts in an efficent way for participants, or a couple variations of a prototype are presented to test alternate concepts.
An evaluation is presented but doesn't communicate any added value to the team's development process.
An evaluation that produces valuable insights on improving and developing the team's concept.
An evaluation that is exhaustive and thoughtful in collecting as much useful information from participants while be respectful of their time.
A marketing card is complete but is very basic and lacks cohesion with the overall team's project.
A marketing card conveying a consistent visual and narrative story with the game concept that will clearly generate interest in the game.
A marketing card with an exceptionally engaging and visual message to try the trivia game.
✓- Below Standard
✓ At Standard
✓+ Above Standard
Interface mockups are provided but lack detail, not demonstrating a unique visual perspective on the basic trivia template design.
The interface mockups demonstrate a thoughtful concept design and provides a good representation for ideas and feedback from participants.
The mockups are exceptional in representing and evaluating some novel concepts, or a couple variations of concepts are presented to compare.
✓- Below Standard
✓ At Standard
✓+ Above Standard
A prototype is provided but lacks detail to make the evaluation fruitful, not demonstrating a unique visual or interactive perspective on the basic trivia template design.
A prototype that demonstrates thoughtful concept design and provides a good representation of idea for feedback from participants.
A prototype that is exceptional in representing and evaluating some novel concepts in an efficent way for participants, or a couple variations of a prototype are presented to test alternate concepts.
✓- Below Standard
✓ At Standard
✓+ Above Standard
The code testing documentation has been completed but lacks detail or an accurate evaluation of the code quality.
The code testing is complete, accurately represents the state of the application, and is useful in identifying improvements as needed.
The code testing is very thorough and goes beyond the standard testing items provided in the example.
Take this opportunity to wrap-up your trivia app the best you can in order to begin testing your game in the next phase.
❏ Deliverable A slide set with a link to your prototype, a summary of evaluation results, a copy of your marketing card, and a link to your working trivia app. Prepare to demonstrate and present your background work.
Each team member should evaluate the prototype by having two people individually play the prototype game using the think-aloud protocol. Synthesize your results and define important decisions for your trivia design before coding begins.
Thinking Aloud from Nielsen Norman Group.
❏ Deliverable A document or slide that summarizes the results of your prototype evaluation.
You will find that creating good trivia questions will take careful thought and multiple iterations. So getting a good start on your question bank will be very beneficial. Follow the instructions for managing a question database for your team and make an intentional plan to develop your 20 or more questions.
❏ Deliverable Your completed 20+ question database.
Design a prototype of the solution for a detailed internal review and evaluation by a sample of stakeholders. Based on what you learn from your prototype, organize a development strategy to methodically program and style your solution with efficiency and quality. Also prepare for the promotion and launch of your solution, and conduct unit testing to ensure all is in working order before an in-class demonstration.
Many of the tasks for this stage may occur in parallel with occasional starts and stops appropriate for your development progress.
✓- Below Standard
✓ At Standard
✓+ Above Standard
The live trivia app is functioning, but the style and/or content has been developed very little from the base template provided.
The app demonstrates intentional design and styling consistent with the team's concept and goals. The app code and features demonstrate a customized interaction that largely functions as desired.
The app is clearly a work of diligent and thoughtful work that goes beyond the base requirements for the project.
The demonstration and development review were presented but lack a cohesive explanation.
The demonstration and development review provided a coherent explanation of the background work completed and the functions and features of the demonstrated application.
The demonstration demonstrated an exceptional development process due to the prototyping and evaluation work.
✓- Below Standard
✓ At Standard
✓+ Above Standard
An evaluation is presented but doesn't communicate any added value to the team's development process.
An evaluation that produces valuable insights on improving and developing the team's concept.
An evaluation that is exhaustive and thoughtful in collecting as much useful information from participants while be respectful of their time.
✓- Below Standard
✓ At Standard
✓+ Above Standard
The question bank is mostly complete but lacks quality of work, revealing a hurried approach or little reflection.
The question bank is complete and presents a consistent method and attention to detail.
The question bank provides exceptionally formed questions and answers that reveal a thoughtful approach to generating and evaluating the quality of the work.
Task
Estimated Time
Question Bank Development
3 hours
Interface Mockups
2 hours
Interactive Prototype
1 hour
Prototype Evaluation
1 hour
Code Development Outline & Begin Coding
6 hours
Marketing Card
1 hour
Code Testing
2 hours
Prepare Development Review and Demonstration
2 hours
Create a 3" x 5" marketing card. The marketing card will be a valuable lead-in to your game that could be distributed physically or as a digital image. Think about what your elevator pitch would be for the game and make it visual.
❏ Deliverable A PNG image file of your marketing card.
✓- Below Standard
✓ At Standard
✓+ Above Standard
A marketing card is complete but is very basic and lacks cohesion with the overall team's project.
A marketing card conveying a consistent visual and narrative story with the game concept that will clearly generate interest in the game.
A marketing card with an exceptionally engaging and visual message to try the trivia game.