Difference between revisions of "Talk:BetaDelta"
Jump to navigation
Jump to search
Natalie.ng (talk | contribs) |
|||
Line 1: | Line 1: | ||
− | + | == Proposal Review == | |
− | |||
− | |||
− | ' | + | The fundamental idea behind this project is sound, and the project is formulated in a collaborative way with clearly defined tasks. |
− | * | + | That being said, the proposal itself is poorly formatted and shallow. |
− | * Entire project hinges on $2.00 light sensor. | + | |
+ | ===Strengths=== | ||
+ | * Team has a clear objective of what they're hoping to accomplish as far as the website is concerned. | ||
+ | * The overview is well-written. | ||
+ | * There is a clear division between the tasks required to complete the project. | ||
+ | |||
+ | ===Weaknesses=== | ||
+ | This project considers at least the following tasks: | ||
+ | # Design a physical box for the Raspberry Pi board and the sensor suite. | ||
+ | # Design a small electronic circuit to send all the sensor information to the Raspberry Pi. | ||
+ | # Design a power distribution method (battery, power supply, a mix of both?) | ||
+ | # Develop an algorithm capable of transforming sensor data into useful information. | ||
+ | # Develop a two-way website, likely hosted in the cloud, where groups already studying can declare their intention to collaborate, and students looking for groups can find a match. | ||
+ | # Model a database to store past information regarding usage, schedules, and topics. | ||
+ | |||
+ | The current proposal only addresses, superficially, a few of the items mentioned above. | ||
+ | Hence, either this project must be downscaled to a point where the objectives are narrower, or the proposal must be completely rewritten to reflect the actual tasks that need to be solved. | ||
+ | |||
+ | Other comments: | ||
+ | * Overall format of the proposal is deficient. Please use the [https://www.mediawiki.org/wiki/Help:Formatting MediaWiki Help] to improve the presentation. You can also take a look at the source code of other project pages to learn how to use the wiki. | ||
+ | * Team members should be listed above the objectives, and include the TA. | ||
+ | * Entire project hinges on $2.00 light sensor. Is a light sensor a robust source of data for this project? | ||
* Gantt chart does not illustrate how responsibilities will be divided between the team members. | * Gantt chart does not illustrate how responsibilities will be divided between the team members. | ||
− | |||
* Budget should have links and *is* required for the proposal. It should also contain a total. | * Budget should have links and *is* required for the proposal. It should also contain a total. | ||
* Is it reasonable to believe that all 3D printing (including design) will begin and end in a single week? | * Is it reasonable to believe that all 3D printing (including design) will begin and end in a single week? |
Revision as of 06:31, 7 February 2017
Proposal Review
The fundamental idea behind this project is sound, and the project is formulated in a collaborative way with clearly defined tasks. That being said, the proposal itself is poorly formatted and shallow.
Strengths
- Team has a clear objective of what they're hoping to accomplish as far as the website is concerned.
- The overview is well-written.
- There is a clear division between the tasks required to complete the project.
Weaknesses
This project considers at least the following tasks:
- Design a physical box for the Raspberry Pi board and the sensor suite.
- Design a small electronic circuit to send all the sensor information to the Raspberry Pi.
- Design a power distribution method (battery, power supply, a mix of both?)
- Develop an algorithm capable of transforming sensor data into useful information.
- Develop a two-way website, likely hosted in the cloud, where groups already studying can declare their intention to collaborate, and students looking for groups can find a match.
- Model a database to store past information regarding usage, schedules, and topics.
The current proposal only addresses, superficially, a few of the items mentioned above. Hence, either this project must be downscaled to a point where the objectives are narrower, or the proposal must be completely rewritten to reflect the actual tasks that need to be solved.
Other comments:
- Overall format of the proposal is deficient. Please use the MediaWiki Help to improve the presentation. You can also take a look at the source code of other project pages to learn how to use the wiki.
- Team members should be listed above the objectives, and include the TA.
- Entire project hinges on $2.00 light sensor. Is a light sensor a robust source of data for this project?
- Gantt chart does not illustrate how responsibilities will be divided between the team members.
- Budget should have links and *is* required for the proposal. It should also contain a total.
- Is it reasonable to believe that all 3D printing (including design) will begin and end in a single week?