Overview: Rapid prototyping is a critical skill in the game industry. Whether developing a proof of concept or in the early stages of game development, programmers must be able to quickly analyze task documents, learn any new technology, and then accurately implement their tasks for a given prototype within a given time frame.
For Part I of the project, you are assigned a rapid prototype project by a hypothetical company that has a hard deadline. The company has given you project documents that provide the specifications required for the rapid prototype. When working on your prototype, you will need to be conscious of scope creep and may have to rebalance your workload or refactor what you are doing to meet your deadline.
Prompt: Project Scenario—Rapid Prototype Request from Acme Game Design. As an employee of Acme Game Design, you will often have to juggle multiple projects. Companies sometimes hire Acme Game Design to create games to help market their products. Your supervisor has requested that you choose one of the following three scenarios to design an additional prototype as a marketing promotion: Metallic Detective Treasure Hunt, Fuzzy Farmer, or Clean Your Room.
For Milestone One, you will choose one of the three scenarios listed below and design a prototype based on the specifications in the design document for your scenario. This milestone addresses the project specifications for your rapid prototype design in addition to details on logging source control check-ins.
Scenarios/Design Documents: Review the requirements for each rapid prototype as outlined in the design documents.
Your rapid prototype must conform to the expectations of the company as detailed in the provided project specifications,
Specifically, you must demonstrate the following critical elements:
I. Source Code Control
a. Test the source code control system for prototype and submit a log of your check-ins in order to indicate active project management. Ensure that you check in your source code after each instance of modifications made.
b. Define
II. Traceability: The prototype delivered must contain all of the required functionality specified in the provided project documents.
Guidelines for Submission: To complete this assignment:
- Submit a screenshot of the log of check-ins (change list) in the Bitbucket source control to reflect updates to the prototype.
- Given the game design document for the chosen scenario, identify the requirements to be built in the prototype and submit a 1- to 2-page proposal for implementation. Be sure to use appropriate citations and APA-style formatting for your paper along with 12-point Times New Roman font. See the game design document for an example.
- Use the Traceability Matrix Template to complete the traceability criteria for this milestone.
Goal: Level 1 – Map
Objectives: Create Landscape
- Task: Create a new level/map.
- Task: Create a new landscape.
- Task: Sculpt the landscape.
- Task: Apply a variety of materials.
- Task: Test and Verify.
Objectives: Create border fence.
- Task: Create a ranch style fence section using simple shapes.
- Task: Add materials and texture to the the fence section.
- Task: Convert the fence section to a static mesh.
- Task: Copy/Duplicate the fence section placing it around the border of the map.
- Task: Test and Verify.
Objectives: Create simple shape objects
- Task: Create a rock.
- Task: Create a bush.
- Task: Create a tree.
- Task: Create a cluster of flowers.
- Task: Test and Verify.
Objectives: Add obstacles to the map.
- Task: Place randomly on the map rocks.
- Task: Place randomly on the map bushes.
- Task: Place randomly on the map tree.
- Task: Place randomly on the map flowers.
- Task: Test and Verify.