1 / 14

Phase 4

Phase 4. Team member contributions. Teams may send me an email, directing what percentage of the team grade is to be attributed to each team member Those who did not contribute, should be granted zero credits Seriously. The Peer Review. Your rating is 10% of your grade.

niles
Download Presentation

Phase 4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Phase 4

  2. Team member contributions Teams may send me an email, directing what percentage of the team grade is to be attributed to each team member Those who did not contribute, should be granted zero credits Seriously.

  3. The Peer Review • Your rating is 10% of your grade. • Do one for each team member and for yourself • Your score: #you do - #bad • Hand them in by the last day of class • Forms will be on the web site • Hardcopy please

  4. 1. This team member was regularly available. 2. This team member regularly read and used email in relation to the team project. 3. This team member was supportive of the activities of other members. 4. This team member started work with sufficient time to finish on time. 5. This team member tried hard regardless of the value of their contribution. 6. This team member was essential to our team's success. 7. This team member actively participated in Phase I. 8. This team member actively participated in Phase II. 9. This team member actively participated in Phase III. 10. This team member actively participated in Phase IV. 11. This team member HAD the background to significantly contribute to the team effort.

  5. Part 1 - The WBS • Create a list of tasks needed to implement your system (the Work Breakdown Structure) • Imagine your team to be part of a company with unlimited resources. Imagine your target to be the successful completion of the entire system (not just your team demo). Imagine that you are about to plan the labor for the entire job to the finest detail.   • List all the tasks to be completed. EVERY TRACKABLE TASK MUST BE INCLUDED. • Do NOT include hardware costs. However, the labor to select and purchase hardware should be included. • See lecture #11

  6. Part 2: The Demo • Your team is required to portray the user experience, and/or PROVE THAT YOUR PROJECT IS FEASIBLE. How and what you do is up to you. • It can be a PowerPoint presentation of 10-12 slides • It can be a working demonstration of your integration thread • Unless you've already demonstrated for Open House or the Nov 12/15 Demos, you must do a formal 20 minute presentation

  7. The Demo - 20 min presentation • Present a “picture” of the final product • System Architecture • Feasibility • Look-and-Feel • Main User Screens • Identify problem areas

  8. Part 3: The Brochure Each team is required to produce a professional, commercial-quality brochure to be used as marketing material, in soliciting clients for funding. The brochure is similar to materials customers expect in real-world demonstrations. • Tri-fold, color if possible (see me if this is an obstacle) • Include Team # and names • One side commercial / one side technical • This should include some critical screen snapshots.

  9. Grading • We fill out a form, and use subjective assessment of 9 categories (more later) Thoroughness of the WBS Full participation by all team members    Professionalism of the presentation    Creativity and professionalism of the brochure    Usefulness of the system in solving the problem    Sensitivity to the customer and users    Sound SW Engineering applied    Creativity and usefulness of the user interface    General attention to detail    Fun & karma component

  10. Your software – usefulness in solving the problem • State the problem explicitly • State how you solve that problem in one sentence • Why you discarded other solutions

  11. Your software - Creativity and usefulness of the user interface • Natural mapping • Remember the good and bad examples • Semantic use of color • User - not CS - jargon

  12. Your software – sensitivity to the customer and user • It better not look like it was designed and meant to be run by CSE and CEN students. • The language should be problem-space

  13. Your software architecture - General attention to detail • Consistency • Misspellings are bad • Seamless boundaries • Context-sensitive help

  14. Your software - Fun & karma component • Please don’t stress out • Attitude can overcome a meager baseline

More Related