text:
User:Cwoo4792/enes100/poppit

Link to project ZNC team page.

Assign Task1
Attempt to chunk poppit by playing it multiple times and finding the best wining strategies.

Compare actual work done to Task1
My Goal was to find wining strategies and I started by trying to pop the ones at the top to set up the lower ones to be popped. I found that when I took time to focus on setting up the balloons rather than just popping all the groups I saw, I would have more success in the outcome of balloons.

Week1 Narrative
I set out to find the wining strategies in poppit and I started this week by trying focus my popping at the top of the screen. I found that you really need to take a look at the big picture in order pop the right ones in the right order to end up with the least amount of balloons possible. However, even when I did this I was unable to pop all the balloons in any of the given games.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Try a pop from the bottom half and move up strategy in Poppit.

Compare actual work done to Task2
My goal was to try some games with my focus on popping the bottom half balloons first. I was able to get some tests of that stratgey as well as a strategy of popping all the coupled balloons first.

Week2 Narrative
I set off to find out if a focus on popping the balloons from the bottom half of the screen would prove to be more successful than popping from the top. I was able to find out that my average scores were mildly better and that there would be less strands of un-popped balloons at the bottom. I also decided to see if popping all the coupled balloons first would help in my outcome. I found out that it only made things bad when you only pop the coupled balloons because it just messed up the big group pops giving me an average of about 33.5 balloons. However, when I did not limit myself to only popping them, but popping them to set up large pops, I was able to get an average of about 12.5 ballons.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Finish up project and complete project page.

Start Next Project Week0 activities
Research mechanisms for the R.I.O.T robot.

title: User:Cwoo4792/enes100/poppit


text:
User:Bmart14/enes100/poppit

Link to project DBBM team page.

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: User:Bmart14/enes100/poppit


text:
Engineering Projects/Poppit/Howard Community College/Fall2011/502 AZM

Problem Statement
Use math of various types to analyze poppit, and then try to use this new knowledge to devise strategies or algorithms to play the game better.

Team Members
ZThompso7635

mkhan4793: http://en.wikiversity.org/wiki/User:Mkhan4793

Tophat: http://en.wikiversity.org/wiki/User:Tophat

Summary
People can approach math in different ways in the game. It depends on how you look at it. You can look at the game as a matrix board and try to eliminate the rows and columns by matching the color of the balloons and eliminating them periodically.

team weekly reports.

Story
Our project was to analyze poppit mathematically. The first step was to decide how to look at the game board itself. Determining the irrelevant information was the first obstacle. The shape of the balloons and the little prizes inside some them make the game more interesting visually, but they do not add to the math of trying to eliminated all the balloons.

Since none of us are mathematicians we went to see a math instructor at the college, Roger Hartman. He helped us come up with many ideas and paths of thought that may be of use in the project. We even discussed making each value of a matrix set to a sinusoidal wave-function which would interfere with the spaces around it, which would be out of phase with it due to their position. If the interference produced a zero due to destructive interference then the balloons were of the same color and could be popped. While interesting, this proved more complex than necessary.

Another interesting thing we came across was a theorem that proved that any map could be colored with only four colors, and none of the boundaries of the same color would touch. If applied to poppit, it means one could conceive of a board in which no moves were possible at all, because none of the balloons would be adjacent to each other (Poppit has five colors, but that just means this is even easier to accomplish). Since the board is randomly generated, unless there is an internal regulator against such things, this proves that statistically there will be an impossible poppit board eventually, i.e. not every board is winnable.

One way we decided to approach the game was as either a large matrix or as a series of interconnected sets. With the approach of the matrix, one can view balloons simply as numbers, one through five representing the different colors of balloons, and zero being the value of an empty space. This way you start off with a 10x15 matrix, where every space is a number between one and five. The goal was then to find mathematical operations one can perform to first search the matrix for numbers of equal value which were adjacent to each other, and then could "pop" those spaces by making them both zero. In addition to making just two of them zero, it would then also attempt to match any other spaces adjacent to the first adjacent one.

Another step in the algorithm would be to always check for zero spaces between spaces with nonzero values. This is how one would make sure the balloons rise up when ones above them are popped, or shift towards the center when whole columns are eliminated.

Strategy guides we found online here and here alluded to the fact that each poppit board that is generated is almost entirely random, so it is likely that some boards are winnable and others simply are impossible regardless of your strategy.

What we have done successfully is establish a way to view poppit mathematically, and potentially write some sort of program that could play poppit for you. We have also proved that unless there is something about the game we have not been told (i.e. something inside the program that keeps it from making an impossible game), it is in fact sometimes unwinnable.

Decision List
Our first decision was how to get in contact with someone from the math department to talk about what kind of math this project would involve. Next we just discussed ideas about moving forward with the math we had found.

Material List
Our work was more an intellectual exercise rather than a construction project. Our materials were essentially our engineering notebooks and the computer.

Software List
The only software we used was Google chrome to play Poppit in, and experiment with its parameters.

Time
It is difficult to say how long it would take to program a computer to beat poppit, because it is less a programming exercise and more a mathematical proof. With access to a program like Mathematica it should be possible to replicate playing poppit in a program using the types of maneuvers we thought of. This would probably take a few weeks to nail down the exact mathematical operations to go with our theories, and then to write a looping program to scan the randomly generated "poppit board" matrices.

Tutorials
Textbooks I consulted were about linear algebra and game theory. The primary ones I explored are below: "Decision Making Through Operations Research" by Robert J. Thierauf and Richard A. Grosse. "Discrete Mathematics with Game Theory" by Edgar G. Goodaire and Michael M. Parmenter. "Numerical Methods Using Mathcad" by Laurene Fausett.

Next Steps
The next thing yo do in this project would be to figure out how to perform these matrix operations that would clear rows, and move values around within the matrix. I do not believe it is possible to make a robot that always wins at poppit, due to the four color theorem, but through testing of the replicator one could fine tune its move order to potentially make one that wins some of the time.


text:
User:Inmookchung27/enes100/poppit

Link to project DBBM team page.

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Inmookchung27/enes100/poppit


text:
Engineering Projects/Poppit/Howard Community College/Fall2011/502 HDM/muzzlbock/poppit

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.


text:
User:Wesley Rodriguez/ENES100/poppit

Poppit Project Fall 2011

title: User:Wesley Rodriguez/ENES100/poppit


text:
User:Dpatel5391/enes100/poppit

Link to project DBBM team page.

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Dpatel5391/enes100/poppit


text:
User:ZThompso7635/enes100

This is my portfolio, introduction to engineering 100, fall 2011.

Poppit User Page

Continuing Poppit Team

Poppit Team: http://en.wikiversity.org/wiki/Poppit/Howard_Community_College/Fall2011/502_AZM

Model Boat: http://en.wikiversity.org/wiki/User:ZThompso7635/enes100/Model_Boat

Model Boat Team: http://en.wikiversity.org/wiki/Model_boat/Howard_Community_College/fall2011/502_bottle

title: User:ZThompso7635/enes100


text:
User:ZThompso7635/enes100/poppit

Team page: http://en.wikiversity.org/wiki/Poppit/Howard_Community_College/Fall2011/502_AZM

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:ZThompso7635/enes100/poppit


text:
User:Dammy125

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Dammy125


text:
User talk:Spatel5040/enes100

ENES 100 webpage for chunk poppit project

title: User talk:Spatel5040/enes100


text:
User:Dpatel5391/enes100

ENES-100 webpage for projects

title: User:Dpatel5391/enes100


text:
Engineering Projects/Poppit/Howard Community College/Fall2011/502 TDM/502 Dkirby7518/Poppit/Howard Community College/Fall2011

Problem Statement
Put the last negotiated problem statement with the instructor or client of the project here.

Team Members
Put each team members name here with links to their personal page here. Real names do not have to be used.

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

Poster
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.

Story
Tell a story of the project. Describe how 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
List all formal decisions made with links to their documentation such as a decision tree or decision matrix.

Material List
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
Installing and learning different software packages is part of most engineering project just like the materials list.

Time
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
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
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.


text:
User:Dmoreno1899/ENES100/poppit

ENES Fall 2011 Poppit project

title: User:Dmoreno1899/ENES100/poppit


text:
User:Mkhan4793

This link back to project page :Poppit/Howard Community College/Fall2011/502 AZM

This is the link to Airplane float  :User:Mkhan4793/enes100/AirPlane Float

http://en.wikiversity.org/wiki/User:Mkhan4793/enes100/poppit

Link to project TSAY team page.

Problem Statement1
To show how math is involved in the game.

Solution
You can look at the game as a function in which you use the elimination method to solve the question. You have to eliminate balloons as much as you can in order to win. Each balloon is given a color. In that case, r = red balloon, g=green b=blue.

Strategies of Chunking
There is not really a math technique of chunking the balloons faster. We can think the game as a matrix in which we chunk and pop the balloons from the corner and slowly popping the balloons gradually moving into the center.

Results from the game
The results of the game vary on how you approach the game. It basically depends on the way each individual plays. Hence math is less involved in the results. The only place where math takes a part in the result is when there are a number of balloons left. 1 balloon meaning that you are good therefore increasing the number of balloons and the end means that you are not that good at popping the balloons.

title: User:Mkhan4793


text:
User:Tophat

Link to Poppit Project Poppit/Howard_Community_College/Fall2011/502_AZM team page.

Link to Music Project Music_projects/Howard_Community_College/fall2011/502_MusicTeam team page.

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Tophat


text:
User:Dmoreno1899/ENES100

Projects for Dominick Moreno's Fall 2011 ENES100 class.

Projects

 * Chunking Poppit

title: User:Dmoreno1899/ENES100


text:
User:Spatel5040/enes100/poppit

Link to project TSAY team page.

Give instructor top 3 project choice list
My top three project choices are: Chunk Poppit, music project and Apps. I really like the chunk Poppit project because it is really easy. Our group just have to play the game and come up with the strategy to pop the most balloons.

Write problem statement
Try to pop all the balloons in the game poppit

Assign Task1
We were assigned to play multiple games of poppit with different strategies. We were supposed to find out which strategy works best to pop most of the balloons. We think that the best strategy was to pop all the balloons that are chunked in big group and the work with balloons chunked in small group.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Our task was to find the best strategy that would pop most or all of the balloons in game called Poppit and have an accuracy or more than 80% success.

Compare actual work done to Task2
We tried multiple strategies but than at last we found out that the best strategy was to pop the larger groups first and then work our way down to the smaller groups.

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Spatel5040/enes100/poppit


text:
User talk:Spatel5040

 Hello Spatel5040, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:43, 8 September 2011 (UTC)

What is the copyright of File:Helicopter42.jpg?
The same comments apply to:
 * File:Helicopter2.jpg
 * File:Helicopter2.jpg
 * File:Helicopter30.JPG
 * File:Helicopter31.JPG
 * File:Helicopter32.JPG
 * File:Helicopter33.JPG
 * File:Helicopter34.JPG
 * File:Helicopter35.JPG
 * File:Helicopter36.JPG
 * File:Helicopter37.JPG
 * File:Helicopter38.JPG
 * File:Helicopter39.JPG
 * File:Helicopter40.JPG
 * File:Helicopter41.JPG

--Thenub314 18:44, 29 October 2011 (UTC)

Files Missing License Information
Thank you for uploading files to Wikiversity. See Media for copyright and license requirements for Wikiversity files. All files must have copyright and/or license information added to the file.

Instructions for adding copyright and/or license information are available at License tags. Files must be updated within seven days or they may be removed without further notice. See Requests For Deletion for more information.

The following files are missing copyright and/or license information:
 * File:Helicopter64.jpg
 * File:Helicopter65.jpg
 * File:Helicopter66.jpg
 * File:Helicopter67.jpg
 * File:Helicopter68.jpg
 * File:Helicopter69.jpg
 * File:Helicopter70.jpg
 * File:Helicopter71.jpg
 * File:Helicopter72.jpg
 * File:Helicopter73.jpg
 * File:Helicopter74.jpg
 * File:Helicopter76.jpg
 * File:Helicopter77.jpg
 * File:Helicopter78.jpg
 * File:Helicopter79.jpg
 * File:Helicopter80.jpg

MaintenanceBot (discuss • contribs) 03:53, 11 November 2013 (UTC)

title: User talk:Spatel5040


text:
User:Afayyaz6843/enes100/poppit

Link to project TSAY team page.

Problem Statement1
To use a most efficient way of popping balloons. To have a least number of balloons left at the end of the game.

Strategies of Chunking
Their were few strategies adapted by all the team members in order to achieve our goal of having a least number of balloons left at the end of the game. The most working strategies were popping the big chunks first and then smaller, popping smaller chunks first and then bigger, left to right, and top to bottom.

Results from the game
The game was played more than 50 times using all the strategies listed. Out of all the strategies the most efficient was popping bigger chunks of balloons first and then smaller. By using this strategy not only we had had gotten the least number of ballons at the end of the game, but also we had an average of 11%.

Analysis
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

title: User:Afayyaz6843/enes100/poppit


text:
User talk:Mkhan4793

5/10/0 ... this is not the proper place for a user page on a project, did not push the project forward 1sfoerster 12:45, 20 September 2011 (UTC) how do we push the project forward? I did write on my userpage. Mkhan4793 13:59, 21 September 2011 (UTC)

 Hello Mkhan4793, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:43, 8 September 2011 (UTC)

title: User talk:Mkhan4793


text:
User:Mkhan4793/enes100

this is my portfolio http://en.wikiversity.org/wiki/User:Mkhan4793/enes100/poppit

title: User:Mkhan4793/enes100


text:
User talk:Wesley Rodriguez

0/0/0 ... this user page is in the wrong space .. is not filled out 1sfoerster 13:03, 20 September 2011 (UTC)

 Hello Wesley Rodriguez, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:43, 8 September 2011 (UTC)

title: User talk:Wesley Rodriguez


text:
User talk:Dkirby7518

 Hello Dkirby7518, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:43, 8 September 2011 (UTC)

title: User talk:Dkirby7518


text:
User:Syoon9484/enes100/poppit

Link to project TSAY team page.

Give instructor top 3 project choice list
Typically the instructor picks teams. Students send the instructor their top 3 choices. The project choices are typically those found at Category:General_Engineering_Projects. The instructor tries to put students in the project of their choice. Put your top three choices here after they are used to assign you to this project. Create a link to the project root and to where your team will be working.

Write problem statement
Look through the existing problem statements. Find something not yet done on the project. Create a problem statement for it. Think of a new subsystem that needs to be built for the project. The goal is something simple, possible, for zero dollars.

Assign Task1
Tasks are typically done over the weekend. They are documented during the week, presented during the week and the next weekends work is negotiated during the week. Week 0 is the week that task 1 is negotiated. Record your individual task here. Plan on working on it during the weekend between week0 and week1.

Compare actual work done to Task1
Rationalize differences

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Record what you are planning on doing for the team during the weekend between week1 and week2 of the project here.

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Syoon9484/enes100/poppit


text:
User talk:Dpatel5391

 Hello Dpatel5391, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:44, 8 September 2011 (UTC)

title: User talk:Dpatel5391


text:
User talk:ZThompso7635

 Hello ZThompso7635, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:44, 8 September 2011 (UTC)

title: User talk:ZThompso7635


text:
User talk:Dammy125

 Hello Dammy125, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:44, 8 September 2011 (UTC)

 Hello Dammy125, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:44, 8 September 2011 (UTC)

Files Missing License Information
Thank you for uploading files to Wikiversity. See Media for copyright and license requirements for Wikiversity files. All files must have copyright and/or license information added to the file.

Instructions for adding copyright and/or license information are available at License tags. Files must be updated within seven days or they may be removed without further notice. See Requests For Deletion for more information.

The following files are missing copyright and/or license information:
 * File:IMG 20111025 123118.jpg

MaintenanceBot (discuss • contribs) 03:40, 11 November 2013 (UTC)

title: User talk:Dammy125


text:
User:Tophat/enes100

This is my portfolio for Introduction to Engineering Design ENES-100 http://en.wikiversity.org/wiki/User:Tophat/enes100/poppit

title: User:Tophat/enes100


text:
User:Mkhan4793/enes100/poppit

here is the page for the poppit

title: User:Mkhan4793/enes100/poppit


text:
User:Tophat/enes100/poppit

My Poppit page

title: User:Tophat/enes100/poppit


text:
User talk:Tophat

0/0/0 delete the stuff you are not going to fill out, no record of what you intended to do, did not push the project forward 1sfoerster 12:48, 20 September 2011 (UTC)

user pages for music projects are in the wrong spot ... please move ... will not grade in the future 1sfoerster 20:25, 26 September 2011 (UTC)

0/0/0 ... thing has changed or is filled out for the project 1sfoerster 20:26, 26 September 2011 (UTC)

0/0/ ... nothing has changed 1sfoerster 18:23, 3 October 2011 (UTC)

Haven't seen you in class at all. If you check on this, leave a comment on my discuss page and I'll give you my number to catch you up to speed. Dmoreno1899 17:19, 9 October 2011 (UTC)

0/0/0 ... nothing to grade 1sfoerster 14:00, 11 October 2011 (UTC)

Again, nothing new to say. Dmoreno1899 18:53, 16 October 2011 (UTC)

0/0/0 ... nothing to grade 1sfoerster 13:44, 18 October 2011 (UTC)

 Hello Tophat, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:45, 8 September 2011 (UTC)

title: User talk:Tophat


text:
User talk:Inmookchung27

 Hello Inmookchung27, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:45, 8 September 2011 (UTC)

Files Missing License Information
Thank you for uploading files to Wikiversity. See Media for copyright and license requirements for Wikiversity files. All files must have copyright and/or license information added to the file.

Instructions for adding copyright and/or license information are available at License tags. Files must be updated within seven days or they may be removed without further notice. See Requests For Deletion for more information.

The following files are missing copyright and/or license information:
 * File:Ball 2.jpg
 * File:Ball1.jpg
 * File:Ballone.jpg
 * File:Waterfall10.jpg
 * File:Waterfall11.jpg
 * File:Waterfall5.jpg
 * File:Waterfall7.jpg
 * File:Waterfall8.jpg
 * File:Waterfall9.jpg

MaintenanceBot (discuss • contribs) 03:47, 11 November 2013 (UTC)

title: User talk:Inmookchung27


text:
User:Dmoreno1899

Enes 100 Projects

 * [Poppit]
 * [Music Project]
 * [The Tin Can Band] (Music Project part II)

title: User:Dmoreno1899


text:
User talk:Bmart14

 Hello Bmart14, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:45, 8 September 2011 (UTC)

Files Missing License Information
Thank you for uploading files to Wikiversity. See Media for copyright and license requirements for Wikiversity files. All files must have copyright and/or license information added to the file.

Instructions for adding copyright and/or license information are available at License tags. Files must be updated within seven days or they may be removed without further notice. See Requests For Deletion for more information.

The following files are missing copyright and/or license information:
 * File:BIg and small bowls.jpg
 * File:Different tubes .JPG
 * File:Escher Poster.JPG
 * File:Escher triangle veiw 1.JPG
 * File:Escher triangle veiw 2.JPG
 * File:Escher uphill roll 1.JPG
 * File:Escher uphill roll 2.JPG
 * File:Escher uphill roll 3.JPG
 * File:Escher uphill roll 4.JPG
 * File:Escher uphill roll 6.JPG
 * File:Escher uphill roll 7.JPG
 * File:Finger holding tube.jpg
 * File:Fish Tubes.jpg
 * File:Illusion 1234.JPG
 * File:Illusion different angle 1234.JPG
 * File:Illusion different angle.JPG
 * File:Measuring Cup.jpg
 * File:Tub with tube sticking in it.jpg

MaintenanceBot (discuss • contribs) 03:40, 11 November 2013 (UTC)

title: User talk:Bmart14


text:
User:Dmoreno1899/ENES100/Poppit

Poppit Project

Objective
To find a way to "cheat" at the flash game "Poppit". The ENES100-502 class has been broken up into sub-groups to accomplish this task. Objectives for some of these groups include strategizing how to play the game, collecting data, using discrete mathematics/statistics to find out if its mathematically possible to win every game, or if there is some kind of RNG factor that makes it impossible to win 100% of the games.

The group I have been designated to is dedicated to programming. Our objective is to write a program that, when given a screenshot of the starting screen, can identify the balloons, and reproduce them in a matrix with a similar structure to the one in the game. This is to be done with Processing, an open-sourced Java based programming language.

title: User:Dmoreno1899/ENES100/Poppit


text:
User:Tleopold2485/enes100/poppit

Link to project TSAY team page.

Give instructor top 3 project choice list
1.)Internal combustion engine

2.)Turbocharger/supercharger

3.)Model airplane

Write problem statement
Find a strategy to pop the most balloons possible by either color or by number of balloons in a group

Assign Task1
Play as many games as possible and using as many strategies as possible to develop the most effective strategy

Compare actual work done to Task1
Found that the best strategy was to pop the larger groups first and then work our way down to the smaller groups.

Week1 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week1 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task2
Perfect the strategy and try to ensure the probability of success is above 80%

Compare actual work done to Task2
Rationalize differences

Week2 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week2 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:32, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task3
Record what you are planning on doing for the team during the weekend between week2 and week3 of the project here.

Compare actual work done to Task3
Rationalize differences

Week3 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week3 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Assign Task4
Record what you are planning on doing for the team during the weekend between week3 and week4 of the project here.

Compare actual work done to Task4
Rationalize differences

Week4 Narrative
Upload photos to wikimedia. Upload video to youtube. Convert all spreadsheets, documents, and presentations to wiki format and create wiki subpage of your page for each of them. Link to them here in a narrative that tells a story. High light the problems (engineering problems) you had and how you solved them.

Week4 Peer Review
Go to each team mates weekly summary wiki page. Read their activities and narrative. Then go the associated discussion page. Say something positive on this page. Try some constructive criticism. Add your name and 1sfoerster 13:33, 28 August 2011 (UTC) to create a time and date stamp. Create a new category if another team mate has already commented here.

Complete Project Page
Follow the "project done" format.

Start Next Project Week0 activities
During this week you will perform the week0 activities of the next project.

title: User:Tleopold2485/enes100/poppit


text:
User talk:Dna bitz

 Hello Dna bitz, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:46, 8 September 2011 (UTC)

title: User talk:Dna bitz


text:
User talk:Muzzlbock

 Hello Muzzlbock, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:46, 8 September 2011 (UTC)

title: User talk:Muzzlbock


text:
User:Tleopold2485

Original post

title: User:Tleopold2485


text:
Engineering Projects/Poppit/Howard Community College/Fall2011/502 TDM/502 Mscobell1809/Poppit/Howard Community College/Fall2011/502 TDM

Problem Statement
Put the last negotiated problem statement with the instructor or client of the project here.

Team Members
Put each team members name here with links to their personal page here. Real names do not have to be used.

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

Poster
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.

Story
Tell a story of the project. Describe how 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
List all formal decisions made with links to their documentation such as a decision tree or decision matrix.

Material List
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
Installing and learning different software packages is part of most engineering project just like the materials list.

Time
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
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
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.


text:
User talk:Cwoo4792

 Hello Cwoo4792, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:47, 8 September 2011 (UTC)

title: User talk:Cwoo4792


text:
User talk:Npsweet

 Hello Npsweet, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:48, 8 September 2011 (UTC)

What is the copyright of File:IMG 20111013 124937.jpg?
The same comments apply to:
 * File:IMG 20111013 124944.jpg
 * File:IMG 20111013 124954.jpg
 * File:IMG 20111004 131255.jpg
 * File:IMG 20111004 131305.jpg
 * File:Rubber band gun2.jpg.jpg
 * File:Rubber band gun.jpg

Files Missing License Information
Thank you for uploading files to Wikiversity. See Media for copyright and license requirements for Wikiversity files. All files must have copyright and/or license information added to the file.

Instructions for adding copyright and/or license information are available at License tags. Files must be updated within seven days or they may be removed without further notice. See Requests For Deletion for more information.

The following files are missing copyright and/or license information:
 * File:IMG 20111004 131255.jpg
 * File:IMG 20111004 131305.jpg
 * File:IMG 20111013 124937.jpg
 * File:IMG 20111013 124944.jpg
 * File:IMG 20111013 124954.jpg
 * File:IMG 20111101 115059.jpg
 * File:Rubber band gun.jpg
 * File:Rubber band gun2.jpg.jpg

MaintenanceBot (discuss • contribs) 03:50, 11 November 2013 (UTC)

title: User talk:Npsweet


text:
User talk:Nridings2

 Hello Nridings2, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:48, 8 September 2011 (UTC)

title: User talk:Nridings2


text:
User:ZThompso7635

Engineering100 page: http://en.wikiversity.org/wiki/User:ZThompso7635/enes100

title: User:ZThompso7635


text:
Engineering Projects/Poppit/Howard Community College/Fall2011/502 1+2=11

Problem Statement
Put the last negotiated problem statement with the instructor or client of the project here.

Team Members
Dominick Moreno

Wesley Rodriguez

Dominick Moreno

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

Poster
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.

Story
Tell a story of the project. Describe how 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
List all formal decisions made with links to their documentation such as a decision tree or decision matrix.

Material List
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
Installing and learning different software packages is part of most engineering project just like the materials list.

Time
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
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
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.


text:
User talk:LindseyDN

 Hello LindseyDN, and welcome to Wikiversity! If you need help, feel free to visit my talk page, or contact us and ask questions. After you leave a comment on a talk page, remember to sign and date; it helps everyone follow the threads of the discussion. The signature icon in the edit window makes it simple. All users are expected to abide by our Privacy policy, Civility policy, and the Terms of Use while at Wikiversity.

To get started, you may

 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.

 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You don't need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --Abd 16:51, 8 September 2011 (UTC)

title: User talk:LindseyDN