At this project milestone the team
presents an informal presentation on block diagram of the system they plan to build
along with a project Gantt chart. Your
team's block diagram should be in poster format in PowerPoint or other supported
software and 36" x 36" in size. Please submit the file electronically to the Desire2Learn dropbox.
The project manager should contact the instructor to get the poster printed
several days before your presentation.
The instructor and TA's will meet with
individually with each team during class hours to discuss the block diagram and
Until your team receives a grade of > 70% you may not proceed to the next stage
of the project.
The general format of the poster is detailed below:
Block Diagram: Include a block diagram of your system. The
should conform to the following guidelines:
|Each block must be a complete functional unit that can built and tested
independently of other blocks of your system. |
|A block can be hardware and/or software.|
|Connections between blocks must be identified with some technical
details such as the type of signals carried, voltage and current levels,
|Blocks need to have a descriptive title.|
|Each block needs to have a rating of the technical difficulty.
|You have (N-1)*100 "difficulty points" to distribute across the
entire block diagram where N is number of people on your team.
The project manager should not be assigned a block.|
|The number of points available to each person on the research and
prototyping stages will be scaled by the fraction of total difficulty
points their blocks are worth. There needs to be discussion among
your team to either balance the workload or to decide how to distribute
points depending on the time and effort individuals can devote to the
|Estimate the difficulty points for each block from factors such as
design complexity, interfacing, need for research to design the block,
difficulty of fabricating or testing. |
|Blocks may be split between two people if needed. In this case
one person has lead responsibility and will get 75% of the difficulty
points while the second support person will get 25% of the difficulty
|Difficulty points for blocks may be increased or decreased by adding
or deleting features to each block.|
|Do not assign difficulty points for fabrication steps such as
milling boards or soldering. Points are assigned only for design
|Clearly identify the person who has full responsibility for each block
on the diagram.
Although we expect that many people will contribute to the design of each
block it is critically important that one person be responsible for the
|Here are examples of one
several bad block diagrams.|
Please ask the instructor if you have any questions on the format of the
Late Deduction: Failure to complete this assignment on time will
result in a point reduction as outlined on the
syllabus. Note that these deductions
are cumulative with late deductions for earlier portions of the project.
The team's poster will be graded using the rubric below. Team's
that score less than 70% will need to correct errors in their block diagram
before they are allowed to move to the next phase of the project. Note
that delays at this stage of the project, while not fatal, can lead to
additional work later in the project design cycle.
Connections between blocks
Distribution of Effort
Presentation & Understanding
System is complete with well
defined modules and little functional overlap.
|Connections between blocks clearly defined with
sufficient technical detail to debug system.
||Block difficulty level is assessed accurately.
||Psuedocode is accurate, descriptive, and technically accurate and feasible.
||Efforts of team are clearly defined and equitably distributed.
Schedule is complete and realistic/
||Team correctly answers questions and has fully researched the design
System is complete, but modules
are not well defined or have overlap.
|Connections are defined but not enough information to measure what signals
||Minor inconsistencies in assessment of block difficulty
||Psuedocode is generally correct, but some minor errors or technical issues.
||Efforts of team are defined, but not equitably distributed. Schedule
may create difficulties.
||Team can answer most question and researched most of the design project.
System incomplete, poorly defined
or overlapping function of modules.
|Blocks are connected but connections are not defined or measurable.
||Major inconsistencies in estimates of block difficulty
||Major technical issues with psuedocode.
||Design process not well defined or gross variation of efforts of
||Team has clear gaps in knowledge; insufficient research to answer questions
about their project.
Block diagram not a valid or
complete representation of system.
|Blocks not connected or connections are incorrect or inconsistent.
||Team lacks basic understanding of how to assess difficulty.
||Psueodcode does not accurately reflect the needs of the project.
||Team lacks basic understanding of the design process or work required.
||Clear lack of understanding. Basic questions unanswered.