Engineering Projects/Poppit/Howard Community College/Fall2011/501 trees

From Wikiversity
Jump to navigation Jump to search

Problem Statement[edit | edit source]


"Anything you can do, I (a developed computer program) can do better" is the underlying theme in the purpose of this project.

As a collective class, we were tasked with the goal to design a program that would play the game "Poppit" and produce better results than that of a human being. The resulting factor being that the program would leave the least amount of un-popped balloons at the end of each game.

As a team, we were task with "Chunking", figuring out how the Poppit game actually works and possible strategies for leaving the least amount of un-popped balloons at the end of each game.

Team Members[edit | edit source]


5/10 non of the links to user space work, can not grade user pages 1sfoerster 18:17, 7 September 2011 (UTC)

Hey Guys, you both need to link your User Pages. We received partial points (see prof. notes above) we can get this squared away in the next class DivaEngineer****

Summary[edit | edit source]

Put an overall, one paragraph summary here with links to the team weekly reports.

Team Weekly Reports

Week 1 (Aug. 29 - Sept. 2, 2011)
Week 2 (Sept. 5 - Sept. 9, 2011)
Week 3 (Sept. 12 - Sept. 16, 2011)

Poster[edit | edit source]

Put a graphic in wikimedia, include the graphic here or link to it here. The graphic should be suitable for creating a traditional project poster.

Note: Include collage of games played

Story[edit | edit source]

Tell a story of the project. Describe how tasks were split up, what the obstacles were, what testing was done, what informal decisions were made, what assumptions were made, what the results were. This is a longer version of the summary with links to all the details collected associated with the project. These links could be to software, links to videos, links to project pages with pictures, etc. Think of the story as a summary of the team weekly reports on one long page rather than a short paragraph like the summary.

Decision List[edit | edit source]

List all formal decisions made with links to their documentation such as a decision tree or decision matrix.

Material List[edit | edit source]

Figuring out what to purchase, what to build, what everything costs is a huge part of engineering. Typically there is a list of materials in stock, materials that are ordered, materials that should be ordered next time there is money, materials that have not been fully justified. These issues are part of healthy management of the engineering lab but are associated with a particular college. The detail needs to be published in this "Done" form. However in the project root, just a list of materials is necessary.

Software List[edit | edit source]

Installing and learning different software packages is part of most engineering project just like the materials list.

Time[edit | edit source]

Time estimates and actual time consumed measurements helps justify salaries (grades). The only way to gain respect for estimated project time and costs is to practice.

Tutorials[edit | edit source]

Most projects consist of making instructions to jump start the next team, shrink the learning of tools and software to the minimum, advice on where to purchase materials, how to assemble, etc. Tutorials modified or created are described here with links.

Next Steps[edit | edit source]

If this is not filled out, the next team may have to repeat each of your steps just to figure out what the next step is. It is best to write this immediately at the end of the project while creating the summary, poster, presentation, and story.